Centos 7: MariaDB versions return 404 on files.directadmin.com

Frank

Verified User
Joined
Sep 25, 2004
Messages
20
One of the servers I manage is a CentOS7 box running DA "stable".

When updating the services using `custombuild`, I see it references MariaDB versions which aren't available on the files.directadmin.com webserver, causing the update to fail.

This is at least the case for MariaDB 10.4 and 10.6 (Haven't checked them all):

mariadb10.4:10.4.31:
mariadb10.6:10.6.15:

There is no 10.4.31 folder at https://files.directadmin.com/services/all/mariadb/10.4/ and no 10.6.15 at https://files.directadmin.com/services/all/mariadb/10.6/

Is this a known issue?
 
Is this a known issue?
Yes, you shouldn't look at the files.directadmin.com directory's anymore. MariaDB is now updated via the Directadmin binarie.
We are using the "current" channel and have MariaDB 10.6.15 running so it must be some place, but not on the files.directadmin.com directory's where it used to be.
 
Am very confused. I am using the recent stable version of DA. I am assuming custombuild auto-updates itself? Or should I update custombuild manually?
 
I don't know if they created an automatic option. I always update manually, you can see in the Custombuild plugin in DA if things can be updated.
Some times some versions are pushed a bit later to the stable channel, because everything must be stable, so I'm not sure if the 10.6.15 version is available on the stable channel.
But you can check by updating manually.

I always do that myself via SSH as root:
Code:
cd /usr/local/directadmin/custombuild
./build update
./build update_versions
 
Which is EXACTLY what I did Richard...


Code:
[root@srv01 custombuild]# ./build versions
Latest version of DirectAdmin: 1.653 build c08a1d88b28d4253a8664310ba7429e884c3f4db
Installed version of DirectAdmin: 1.653 build c08a1d88b28d4253a8664310ba7429e884c3f4db


Latest version of Apache: 2.4.57
Installed version of Apache: 2.4.57

...

Latest version of MariaDB: 10.4.31
Installed version of MariaDB: 10.4.30


MariaDB 10.4.30 to 10.4.31 update is available.

...

[root@srv01 custombuild]# ./build update_versions
Updating MariaDB
    Dumping database XXX
...
    Dumping database YYY
Error: Nothing to do


curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/services/all/mariadb/10.4/10.4.31/centos7-64.txt failed, re-downloading the file...


curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/services/all/mariadb/10.4/10.4.31/centos7-64.txt failed, re-downloading the file...


curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/services/all/mariadb/10.4/10.4.31/centos7-64.txt failed, re-downloading the file...


curl: (22) The requested URL returned error: 404 Not Found
Download of https://files.directadmin.com/services/all/mariadb/10.4/10.4.31/centos7-64.txt failed, re-downloading the file...
Download of https://files.directadmin.com/services/all/mariadb/10.4/10.4.31/centos7-64.txt failed 4 times, exiting...
[root@srv01 custombuild]#
 
Which is EXACTLY what I did Richard...
I'm missing the ./build update command here, I always do that before trying to update things. The ./build versions is only showing versions, not updating the build version.

However I presume you also did that also.

I don't know what's going on with 10.4.31 as I only have 10.6.15 and updated that recently on all servers.
Either 10.4.31 and maybe 10.6.15 is not available for stable or maybe @fln forgot to put them in the correct locations.
 
So referring to your earlier comment about not supposed to use files.directadmin.com: that's invalid then? Or do I need to change that in the build script manually to another url?
 
@Frank CB in DirectAdmin 1.653 does not use centos7-64.txt file at all. It looks like you are running old CB script with new DA.

In the recent DA versions ./build should be a symlink to the main DirectAdmin binary:

Code:
root@server:~# ls -la /usr/local/directadmin/custombuild/build
lrwxrwxrwx 1 root root 14 Sep  8 10:14 /usr/local/directadmin/custombuild/build -> ../directadmin

This ensures you are not using arbitrary CB version but exact CB that was released with this DirectAdmin version. Usually DA takes care of creating the symlink during upgrade.

If symlink is not there - you can execute command da permissions (it is part of what DA does during update) to see if there are any errors in trying to create it.
 
It's not a symlink. So that might be it. Will run `da permissions` later (lost too much time already today)
 
Back
Top