7.0.12 after update

aaP_felix1230123

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)
[1]+ Exit 125 nohup ${shell} &>/dev/null

aaPanel_Kern

Hello, I suggest you check if mysql is running normally?
Updating aapanel will not operate on mysql

aaP_felix1230123

aaPanel_Kern Because suddenly switch off. Does it also will cause this happen ? Can assist me for this issue ?

aaP_felix1230123

aaP_felix1230123 I would like to purchase the membership for long term.

aaPanel_Kern

aaP_felix1230123
Hello, you can buy directly from the official website or aapanel. Are there any problems with the purchase?

aaP_felix1230123

[root@localhost ~]# sudo systemctl start mysqld
Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
[root@localhost ~]# sudo systemctl status mysqld
● mysqld.service - LSB: start and stop MySQL
Loaded: loaded (/etc/rc.d/init.d/mysqld; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2024-12-10 11:29:49 +08; 26ms ago
Docs: man:systemd-sysv-generator(8)
Process: 17164 ExecStart=/etc/rc.d/init.d/mysqld start (code=exited, status=1/FAILURE)

Dec 10 11:29:48 localhost.localdomain systemd[1]: Starting LSB: start and stop MySQL...
Dec 10 11:29:49 localhost.localdomain mysqld[17164]: Starting MySQL. ERROR! The server quit without updating PID file (/www/server/data/localhost.localdomain.pid).
Dec 10 11:29:49 localhost.localdomain systemd[1]: mysqld.service: control process exited, code=exited status=1
Dec 10 11:29:49 localhost.localdomain systemd[1]: Failed to start LSB: start and stop MySQL.
Dec 10 11:29:49 localhost.localdomain systemd[1]: Unit mysqld.service entered failed state.
Dec 10 11:29:49 localhost.localdomain systemd[1]: mysqld.service failed.

aaPanel_Kern

Hello, please check the mysql error log
cat /www/server/data/*.err|grep -i -C 10 error

aaP_felix1230123

aaPanel_Kern InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
03:14:28 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=0
max_threads=500
thread_count=0

connection_count=0

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2024-12-10T03:30:46.917247Z 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2024-12-10T03:30:46.917327Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-12-10T03:30:46.917331Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2024-12-10T03:30:46.917347Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2024-12-10T03:30:46.917379Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.44-log) starting as process 20261 ...
2024-12-10T03:30:46.977568Z 0 [Note] InnoDB: Started in read only mode
2024-12-10T03:30:46.977611Z 0 [Note] InnoDB: PUNCH HOLE support available
2024-12-10T03:30:46.977616Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2024-12-10T03:30:46.977618Z 0 [Note] InnoDB: Uses event mutexes
2024-12-10T03:30:46.977619Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2024-12-10T03:30:46.977621Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-12-10T03:30:46.977623Z 0 [Note] InnoDB: Using Linux native AIO
2024-12-10T03:30:46.977834Z 0 [Note] InnoDB: Number of pools: 1
2024-12-10T03:30:46.977896Z 0 [Note] InnoDB: Using CPU crc32 instructions
2024-12-10T03:30:46.977941Z 0 [Note] InnoDB: Disabling background log and ibuf IO write threads.
2024-12-10T03:30:46.978099Z 0 [Warning] InnoDB: Unable to open "/www/server/data/ib_logfile0" to check native AIO read support.
2024-12-10T03:30:46.978102Z 0 [Warning] InnoDB: Linux Native AIO disabled.
2024-12-10T03:30:46.978726Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2024-12-10T03:30:47.111106Z 0 [Note] InnoDB: Completed initialization of buffer pool
2024-12-10T03:30:47.196464Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-12-10T03:30:47.206601Z 0 [ERROR] InnoDB: Can't create file '/www/server/data/ibdata1' when --innodb-read-only is set
2024-12-10T03:30:47.206635Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-12-10T03:30:47.508151Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2024-12-10T03:30:47.508191Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-12-10T03:30:47.508195Z 0 [ERROR] Failed to initialize builtin plugins.
2024-12-10T03:30:47.508208Z 0 [ERROR] Aborting

2024-12-10T03:30:47.508217Z 0 [Note] Binlog end
2024-12-10T03:30:47.508305Z 0 [Note] Shutting down plugin 'CSV'
2024-12-10T03:30:47.508926Z 0 [Note] /www/server/mysql/bin/mysqld: Shutdown complete

aaP_felix1230123

aaPanel_Kern no ssl

aaPanel_Kern

aaP_felix1230123
Hi, did you add innodb-read-only configuration?

forcing-innodb-recovery questions, please refer to this post. Make sure to back up or take a system snapshot.

InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

https://www.aapanel.com/forum/d/13216-mysqlmariadb-innodb-storage-engine-damage-solution

aaP_felix1230123

aaPanel_Kern I think was last time i want to do slave master. But not running lastly. And i dint edit and while 7.0.9 is facing some issue already. Because i need membership to manage storage.

aaP_felix1230123

aaP_felix1230123 sudo cp -r /www/server/data /www/server/data_backup

But not working

aaPanel_Kern

It is recommended that you refer to the log information to resolve these issues

aaP_felix1230123

aaPanel_Kern How if still unable to restore it ?

aaP_felix1230123

aaPanel_Kern got payservice for solving problem ?

aaP_felix1230123

aaPanel_Kern I think i did the wrong thing delete backup data.

aaP_felix1230123

aaPanel_Kern how bout Contact your hosting provider letting them know your web server is not completing requests. An Error 522 means that the request was able to connect to your web server, but that the request didn't finish. The most likely cause is that something on your server is hogging resources

aaPanel_Kern

Hello, has the database problem been resolved? If not please check the error log
CF's 522 prompt cannot connect to your server. Please check whether the web program is running normally? What program is web service?

aaP_felix1230123

aaPanel_Kern Done solve and thanks.