How to fix eror mysql : ld-elf.so.1: /usr/local/libexec/mysqld: Undefined symbol "sched_getcpu@FBSD_1.7"

[marzochi]

This service running on VPS and After I upgraded the CPU on my host server mysql can't running with error log :

mysqld_safe Logging to '/var/log/mysql/error.log'.
mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
0 [System] [MY-010116] [Server] /usr/local/libexec/mysqld (mysqld 8.0.32) starting as process 32102
1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
ld-elf.so.1: /usr/local/libexec/mysqld: Undefined symbol "sched_getcpu@FBSD_1.7"
mysqld_safe mysqld from pid file /var/db/mysql/myserver.pid ended

# pkg --version
1.20.6
# freebsd-version -uk
13.0-STABLE
13.0-STABLE
# mysql --version
mysql  Ver 8.0.32 for FreeBSD13.1 on amd64 (Source distribution)

I tried searching in several articles but couldn't find it.
How can I run my mysql?

Thanks

 

[SirDice]

13.0-STABLE is old. Upgrade your system. I suggest you reinstall the system with 13.2-RELEASE.

 

[marzochi]

13.0-STABLE is old. Upgrade your system. I suggest you reinstall the system with 13.2-RELEASE.

Thank you for your response Mr. SirDice , I will try upgrade to 13.2-RELEASE, but I'm sorry, will the previous database still be there when I try to update it?

 

[SirDice]

I would suggest checking out the releng/13.2 branch and build(7) from source.

 

[cyclaero]

Thank you for your response Mr. SirDice , I will try upgrade to 13.2-RELEASE, but I'm sorry, will the previous database still be there when I try to update it?

As a general rule of thumb, when a question arises like "... will the previous database still be there when I try to update it?", don't ask, but do a backup.

Given the error, perhaps you can't use any of the mysql tools itselves anymore. Anyway, you could give it a try:

ssh root@your.server.com 'mysqldump -u root --all-databases --extended-insert --force' > /local/path/to/the/mysql-dump.sql

If this does not work, then do:

mkdir -p /local/path/to/the/mysql-backup-dir
cd /local/path/to/the/mysql-backup-dir
ssh root@your.server.com 'cd /var/db/mysql; tar -cf - ./' | tar -xvf -

 

[cracauer@]

Thank you for your response Mr. SirDice , I will try upgrade to 13.2-RELEASE, but I'm sorry, will the previous database still be there when I try to update it?

Yes, no problem. The system is currently unable to touch the database anyway, it won't be damaged.

As mentioned if you have some spare space do a backup now just in case.

 

[marzochi]

I would suggest checking out the releng/13.2 branch and build(7) from source.

Dear SirDice after upgrade to 13.2-RELEASE-p now mysql server is running and previous database that has not been backed up currently running normally, Thanks for you help, cheers

#uname -a
FreeBSD 13.2-RELEASE-p3 FreeBSD 13.2-RELEASE-p3 releng/13.2-n254633-a1c915cc75c1 GENERIC amd64

# /usr/local/etc/rc.d/mysql-server status
mysql is running as pid 2036.

 

[marzochi]

Yes, no problem. The system is currently unable to touch the database anyway, it won't be damaged.

As mentioned if you have some spare space do a backup now just in case.

okay now the database is running normally after the upgrade, thx sir..

 

[SirDice]

#uname -a 
FreeBSD 13.2-RELEASE-p3 FreeBSD 13.2-RELEASE-p3 releng/13.2-n254633-a1c915cc75c1 GENERIC amd64

Good. From now on you can use freebsd-update(8) to keep it up to date. You will need to upgrade again in the future, when 13.3 is released (probably some time next year). Sign up for the freebsd-announce mailing list. You will be notified if there are any security issues that might pop up. And you will be notified whenever new versions are released.