mysql-server newest version 5.7.42 Error

Good morning,

I upgraded mysql version to 5.7.42 and now the server where ispconfig is installed no longer works, can I get help restoring the previous version of mysql? or solve this problem that is blocking my server?
with best regards,
Walter

 

Do you have a disk image backup of the host from before changing mysql version? Restoring that would be easiest.
Otherwise, depending on how you installed the new mysql, there should be a way to uninstall it, then install the original mysql version back.
If you are running ISPConfig, then you should remember ISPConfig supports only the mysql version that comes with the operating system as default. Installing some other mysql usually breaks the system.

 

Thank you for your reply
I am not capable of doing what you suggest. I know the server has a copy system but I don't know how to restore, how can I see it?

The only access is to the ubuntu server with ssh, ispconfig doesn't work

Could you give me some directions or better yet go ahead and solve the problem yourself after paying for the payment you are asking for?

 

See "Business Support" on this page: https://www.ispconfig.org/support/

 

Dear Taleman

Yesterday I made a request for paid support but I don't think it will be satisfied.
I would like to restart the server, could you give me some ideas to fix the problem?

 

Restart? Like in reboot?
If server can be discarded, easy way out is install OS and ISPConfig from scratch. Then you get working system and mysql. I suggest using autoinstaller:
https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/

 

sudo /etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.serviceJob for mysql.service failed because the control process exited with error code.
See booth.choletweb.com does not resolve to address 45.129.14.106: Name or service not known
Oct 24 11:26:09 srv postfix/smtpd[1615]: connect from unknown[45.129.14.106]
Oct 24 11:26:10 srv postfix/smtpd[2653]: connect from unknown[80.94.95.181]
Oct 24 11:26:11 srv CRON[4183]: pam_unix(cron:session): session closed for user root
Oct 24 11:26:11 srv dovecot[935]: auth: Warning: auth client 0 disconnected with 1 pending requests: EOF
Oct 24 11:26:13 srv dovecot[935]: auth-worker(4200): Error: mysql(localhost): Connect failed to database (dbispconfig): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) - waiting for 25 seco
Oct 24 11:26:13 srv dovecot[935]: auth-worker(4200): Error: mysql(localhost): Connect failed to database (dbispconfig): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) - waiting for 25 seco
Oct 24 11:26:13 srv postfix/smtpd[1180]: warning: unknown[45.129.14.106]: SASL LOGIN authentication failed: Connection lost to authentication server
Oct 24 11:26:14 srv dovecot[935]: auth: Warning: auth client 0 disconnected with 1 pending requests: EOF
Oct 24 11:26:14 srv postfix/smtpd[747]: warning: unknown[80.94.95.181]: SASL LOGIN authentication failed: Connection lost to authentication server
Oct 24 11:26:14 srv postfix/smtpd[1180]: disconnect from unknown[45.129.14.106] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
Oct 24 11:26:15 srv dovecot[935]: auth: Warning: auth client 0 disconnected with 1 pending requests: EOF
Oct 24 11:26:15 srv postfix/smtpd[747]: disconnect from unknown[80.94.95.181] ehlo=1 auth=0/1 rset=1 quit=1 commands=3/4
Oct 24 11:26:15 srv postfix/smtps/smtpd[1696]: warning: unknown[xxx.xxx.xx.x.]: SASL LOGIN authentication failed: Connection lost to authentication server
In pratica la cartella mysqld non esiste più in '/var/run/mysqld/ e quindi nemmeno il "mysqld.sock'

 

This log isn't telling you why MySQL won't start.
Only postfix and dovecot services complaining about not being able to connect to MySQL.
Look for relevant errors in MySQL's own log.

 

In practice the mysqld folder no longer exists in '/var/run/mysqld/ and therefore neither does "mysqld.sock'

 

log mysql:


2023-10-23 10:52:05 140661136291584 [Note] /usr/sbin/mysqld: Normal shutdown
2023-10-23 10:52:05 140661136291584 [Note] Event Scheduler: Purging the queue. 0 events
2023-10-23 10:52:05 140660589975296 [Note] InnoDB: FTS optimize thread exiting.
2023-10-23 10:52:05 140661136291584 [Note] InnoDB: Starting shutdown...
2023-10-23 10:52:06 140661136291584 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2023-10-23 10:52:07 140661136291584 [Note] InnoDB: Shutdown completed; log sequence number 1324748960043
2023-10-23 10:52:07 140661136291584 [Note] /usr/sbin/mysqld: Shutdown complete

 

Nothing is logged about starting MySQL??

 

there is nothing

 

sudo service mysql status
● mysql.service - MySQL Community Server
Loaded: loaded (/lib/systemd/system/mysql.service; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2023-10-24 11:20:14 CEST; 47min ago
Process: 3899 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=1/FAILURE)

Oct 24 11:20:14 srv systemd[1]: Failed to start MySQL Community Server.
Oct 24 11:20:14 srv systemd[1]: mysql.service: Service hold-off time over, scheduling restart.
Oct 24 11:20:14 srv systemd[1]: mysql.service: Scheduled restart job, restart counter is at 5.
Oct 24 11:20:14 srv systemd[1]: Stopped MySQL Community Server.
Oct 24 11:20:14 srv systemd[1]: mysql.service: Start request repeated too quickly.
Oct 24 11:20:14 srv systemd[1]: mysql.service: Failed with result 'exit-code'.
Oct 24 11:20:14 srv systemd[1]: Failed to start MySQL Community Server.

 

Service status only gives the last few lines of the log. The real reason is missing.
Look for /var/log/mysql/error.log or something like that.

 

unfortunately that's all there is to it

 

Can't be.
Maybe try in /var/lib/mysql/

If you don't know the location of your MySQL logs, look for the location set in the MySQL config files in /etc/mysql/.
When nothing is set regarding logging then it should be in OS/MySQL's default location.

 

There is not
(dbispconfig): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock'
There is no mysqld folder in the /var/run/ folder
I think that's the problem.

 

Could very well be, but without logging to confirm it's just a shot in the dark.

Recreate the folder, with proper ownership and permissions.
(Usually 775, user mysql and group root)
Then see what happens when you try to start MySQL.

 

nothing new obviously
I will wait for Mr. Thom's response and above all the invoice to make the payment and resolve the problem, before my customers make a legal complaint to me

 

Without logfiles, giving some insight on what's happening in your system (when you start MySQL), it's just a guessing game for everyone.
Including Mr. Thom.