Solved Fresh install with pinned software (old but supported) version fails

kristian

Verified User
Joined
Nov 4, 2005
Messages
461
Location
Norway
Hi,

A fresh install with a pinned version that is older than what DA/Custombuild expects, fails, because the software package doesn't exist on files.directadmin.com. Example:

Code:
# egrep "^(mariadb|mysql_inst)=" /usr/local/directadmin/custombuild/options.conf
mariadb=10.4
mysql_inst=mariadb
# cat /usr/local/directadmin/custombuild/custom_versions.txt
mariadb10.4:10.4.20:

The install will then end up with this:

Code:
mv: 'mariadb-10.4.20-linux-glibc_214-x86_64.tar.gz' and '/usr/local/mariadb-10.4.20-linux-glibc_214-x86_64.tar.gz' are the same file

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
MYSQLPACK_REALNAME is invalid: . Exiting...

And sure enough, it's not in gzip format:

Code:
# cat /usr/local/mariadb-10.4.20-linux-glibc_214-x86_64.tar.gz
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<p>Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>

I'm running 10.4.20 on an existing server, and I want to use this version on my new server as well, because it's going to be a dev/test server and I want to keep the versions the same. I realize that I can try to figure out what the latest 10.4 version available from files.directadmin.com is (is there a list somewhere?), but that seems to defeat the purpose of being able to pin versions.

Should I never expect custom versions to be available, or is there a policy of how many/old versions will be available for download?
 
What you see should not happen.

Try to do a ./build update first and see versions.txt again.
It should read mariadb10.4:10.4.22. I'm running the 10.4.22 version too on the servers.

Maybe it's a little flaw or update issue on your update server, you might try to choose another mirror.
 
10.4.22 is listed in versions.txt, so I assume that one's available. I'm trying to download 10.4.20 though.
 
Is there a policy around version availability? I see that 10.6 and 10.5 only have a single version available for download.

This limits the usefulness of custom_versions on fresh installs. Its main purpose seems to be on already installed servers, to avoid unexpected upgrades, and could perhaps be simplified (and clarified) with a different syntax, e.g. mariadb10.4:do-not-upgrade, because that's really what it does.
 
Is there a policy around version availability? I see that 10.6 and 10.5 only have a single version available for download.
Last I looked it was the current release and the 1 release before it.

The custom_versions can be used to freeze an installed version or prevent a newer version to be installed. However I never understood it to govern the use of really older versions for install.
 
Yeah that's seems to indeed be the case. The wording of the feature and the fact that you put the actual version number in there, sidetracked me into believing multiple versions would be available for install.
 
Maybe old MariaDB are purged because of the size of each version? It’s possible to install older versions but you need to download the source files yourself. Little bit more work, but possible.

For example Nginx and PHP source files are stored for much longer on the CB mirrors:
 

Attachments

  • 772C5DE8-1BD5-41B5-B839-9B46F1F970EE.png
    772C5DE8-1BD5-41B5-B839-9B46F1F970EE.png
    606.7 KB · Views: 3
  • 51B5BAA9-7025-47B0-B296-1FB89366B16D.png
    51B5BAA9-7025-47B0-B296-1FB89366B16D.png
    457.1 KB · Views: 3
Back
Top