MySQL 5.5.58

A better question would be why are you still using 5.5 when 5.7 has been out since 2013? :)
Then again, the general move to MariaDB is well in swing which seem to have some speed advantages over MySQL.
 
BBM said:
A better question would be why are you still using 5.5 when 5.7 has been out since 2013? :)
Then again, the general move to MariaDB is well in swing which seem to have some speed advantages over MySQL.
Click to expand...

We run much newer MariaDB instances on our own servers.

We also manage DirectAdmin for customers and this customer can do a incremental upgrade but can't deal with a major version change right now.

5.5.58 came out 10 days ago.

I just need to know if DirectAdmin supports 5.5 or if not which versions are supported.

Thanks,

Kevin
 
Definitely you will have much more luck to get a response from John by opening a ticket...

Check a list of Members who have read this thread. You won't see him there as of yet.
 
I've submitted a ticket.

zEitEr said:
Definitely you will have much more luck to get a response from John by opening a ticket...

Check a list of Members who have read this thread. You won't see him there as of yet.
Click to expand...
 
It's been added to CustomBuild 2.0, now available on files1.
The changes are quite messy, as they've changed both the naming format from:
  • "MySQL-server" to "mysql-community-server"
  • from "linubx2.6" to "el6" or "el7"
  • frrom 32-bit "i386" to "i686"

and it all varies depending on version.. so 5.5.53 is old, 5.5.58 is the new format.

Same sort of mess for 5.6.

Note, we've added 5.7 support now.

------------
Note! for ALL of the above versions, it will only work with CustomBuild 2.0.
Handling the mess of if-then-else statements in CustomBuild 1.2 or 1.1 was not done.
1.x is essentially end-of-life now anyway.

John
 
The update worked perfectly.

Thanks,

Kevin

DirectAdmin Support said:
It's been added to CustomBuild 2.0, now available on files1.
The changes are quite messy, as they've changed both the naming format from:
  • "MySQL-server" to "mysql-community-server"
  • from "linubx2.6" to "el6" or "el7"
  • frrom 32-bit "i386" to "i686"

and it all varies depending on version.. so 5.5.53 is old, 5.5.58 is the new format.

Same sort of mess for 5.6.

Note, we've added 5.7 support now.

------------
Note! for ALL of the above versions, it will only work with CustomBuild 2.0.
Handling the mess of if-then-else statements in CustomBuild 1.2 or 1.1 was not done.
1.x is essentially end-of-life now anyway.

John
Click to expand...
 
Tried downloading with different servers but keeps giving me this error:

Code: 
Downloaded file /usr/local/directadmin/custombuild/mysql/MySQL-shared-5.5.58-1..i686.rpm does not exist or is empty after download
cwd is: /usr/local/directadmin/custombuild
Fileserver might be down, using the backup file server..
--2017-11-08 10:54:15--  [url]http://69.162.69.58/services/custombuild/all/mysql/5.5/5.5.58/32-bit/MySQL-shared-5.5.58-1..i686.rpm[/url]
Connecting to 69.162.69.58:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-08 10:54:15 ERROR 404: Not Found.
 
"el6" seems to be missing from the path.
What's the output on your server from this command:
Code: 
/usr/local/directadmin/directadmin o | head -n1 | cut -d. -f1 | awk '{print $4}'
as well:
Code: 
/usr/local/directadmin/directadmin o
Note, there are not any el5 rpms.

John
 
Seems like 5.6.38 also showed up on custombuild today too. mysqld doesn't seem to start anymore after the update from 5.6.36 to 5.6.38 though :( (I opened a ticket when someone has time to look).

Also noticed this warning when running build:

Updating MySQL 5.6.38 to 5.6.38
warning: MySQL-client-5.6.38-1.el6.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
Preparing... ########################################### [100%]
1:MySQL-shared ########################################### [ 25%]
2:MySQL-server ########################################### [ 50%]
3:MySQL-devel ########################################### [ 75%]
4:MySQL-client ########################################### [100%]
Ensuring local-infile is disabled for security reasons in MySQL configuration file...
Click to expand...

e: If anyone else ran into this, I downgraded back to 5.6.36 by setting a custom_versions.txt with the following inside:
mysql5.6:5.6.36:

I then ran build mysql again
 
Last edited:
Not sure, but I already replied to one ticket where the issue was:
Code: 
[root@server]# mysqld -V
mysqld: error while loading shared libraries: libnuma.so.1: cannot open shared object file: No such file or directory
and the fix was:
Code: 
yum install numactl
followed by another
Code: 
./buidl set mysql_backup no
./build mysql
./buidl set mysql_backup yes
where we assume the backup was already done the first time around, and we don't want to overwrite them, hence temporarily disabling the backup.

John
 
Unfortunally i ran yesterday into same problem and messed up my whole mysql and now is see that there is an solution, do DA staff check updates before relaeasing ?
 
On an old CentOS 6.9 vps with CB 1.2.41 I'm getting this error when trying to update MySQL:
Code: 
[url]http://files6.directadmin.com/services/all/mysql/64-bit/5.5.58/MySQL-client-5.5.58-1.linux2.6.x86_64.rpm[/url]
Resolving files6.directadmin.com... 2001:16e8:1:c:62:148:174:106, 62.148.174.106
Connecting to files6.directadmin.com|2001:16e8:1:c:62:148:174:106|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-11-10 12:10:30 ERROR 404: Not Found.
Update removed bij DA because of issues? Or is it really time to upgrade this VPS?
 
@amphora,

Please see "Handling the mess of if-then-else statements in CustomBuild 1.2 or 1.1 was not done." said by John in #7

So you might need to migrate to Custombuild 2.x
 
You must log in or register to reply here.
Back
Top