Dzisiaj logując się do bazy wywala błąd
Kod: Zaznacz cały
root@changeme:/etc/mysql# journalctl -xn
-- Logs begin at pon 2023-10-16 07:28:24 CEST, end at pon 2023-10-16 08:34:01 CEST. --
paź 16 08:33:38 changeme.domain.tld mysql[10364]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
paź 16 08:33:38 changeme.domain.tld systemd[1]: mysql.service: control process exited, code=exited status=1
paź 16 08:33:38 changeme.domain.tld systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
paź 16 08:33:38 changeme.domain.tld systemd[1]: Unit mysql.service entered failed state.
paź 16 08:34:01 changeme.domain.tld CRON[11108]: pam_unix(cron:session): session opened for user root by (uid=0)
paź 16 08:34:01 changeme.domain.tld CRON[11107]: pam_unix(cron:session): session opened for user root by (uid=0)
paź 16 08:34:01 changeme.domain.tld CRON[11109]: (root) CMD (root /etc/skrypty/check_apache >> /root/log_wysylka 2>&1)
paź 16 08:34:01 changeme.domain.tld CRON[11108]: pam_unix(cron:session): session closed for user root
paź 16 08:34:01 changeme.domain.tld CRON[11110]: (root) CMD (php /var/www/lms/bin/lms-monitoring.php --config-file=/etc/lms/lms.ini --autotest --q)
paź 16 08:34:01 changeme.domain.tld CRON[11107]: pam_unix(cron:session): session closed for user root
root@changeme:/etc/mysql# /etc/init.d/mysql restart
[....] Restarting mysql (via systemctl): mysql.serviceJob for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details.
failed!
root@changeme:/etc/mysql# journalctl -xn
-- Logs begin at pon 2023-10-16 07:28:24 CEST, end at pon 2023-10-16 08:35:29 CEST. --
paź 16 08:35:02 changeme.domain.tld CRON[11551]: pam_unix(cron:session): session closed for user www-data
paź 16 08:35:29 changeme.domain.tld /etc/init.d/mysql[11913]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
paź 16 08:35:29 changeme.domain.tld /etc/init.d/mysql[11913]: [61B blob data]
paź 16 08:35:29 changeme.domain.tld /etc/init.d/mysql[11913]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
paź 16 08:35:29 changeme.domain.tld /etc/init.d/mysql[11913]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
paź 16 08:35:29 changeme.domain.tld /etc/init.d/mysql[11913]:
paź 16 08:35:29 changeme.domain.tld mysql[11153]: Starting MySQL database server: mysqld . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . failed!
paź 16 08:35:29 changeme.domain.tld systemd[1]: mysql.service: control process exited, code=exited status=1
paź 16 08:35:29 changeme.domain.tld systemd[1]: Failed to start LSB: Start and stop the mysql database server daemon.
-- Subject: Unit mysql.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysql.service has failed.
--
-- The result is failed.
paź 16 08:35:29 changeme.domain.tld systemd[1]: Unit mysql.service entered failed state.Kod: Zaznacz cały
06:36:55 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.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
key_buffer_size=33554432
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 363085 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0x55c838cab0f3]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x55c838b96b14]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f417a927890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f417931d067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f417931e448]
/usr/sbin/mysqld(+0x5d4c54)[0x55c838d96c54]
/usr/sbin/mysqld(+0x5e0db8)[0x55c838da2db8]
/usr/sbin/mysqld(+0x5e18a6)[0x55c838da38a6]
/usr/sbin/mysqld(+0x5d07de)[0x55c838d927de]
/usr/sbin/mysqld(+0x5a0d31)[0x55c838d62d31]
/usr/sbin/mysqld(+0x5a2cac)[0x55c838d64cac]
/usr/sbin/mysqld(+0x58ec7a)[0x55c838d50c7a]
/usr/sbin/mysqld(+0x55b435)[0x55c838d1d435]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x3f)[0x55c838b98d0f]
/usr/sbin/mysqld(+0x2f7731)[0x55c838ab9731]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x903)[0x55c838abdbd3]
/usr/sbin/mysqld(+0x27d898)[0x55c838a3f898]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x45b)[0x55c838a4485b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4179309b45]
/usr/sbin/mysqld(+0x279258)[0x55c838a3b258]
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.