mysqld got signal 11

[SupuS]

Hi all

I have problem with my mysql server .. I found this in my /var/log/syslog


Jun 30 06:28:17 s2 mysqld[19615]: mysqld got signal 11;
Jun 30 06:28:17 s2 mysqld[19615]: This could be because you hit a bug. It is also possible that this binary
Jun 30 06:28:17 s2 mysqld[19615]: or one of the libraries it was linked against is corrupt, improperly built,
Jun 30 06:28:17 s2 mysqld[19615]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 30 06:28:17 s2 mysqld[19615]: We will try our best to scrape up some info that will hopefully help diagnose
Jun 30 06:28:17 s2 mysqld[19615]: the problem, but since we have already crashed, something is definitely wrong
Jun 30 06:28:17 s2 mysqld[19615]: and this may fail.
Jun 30 06:28:17 s2 mysqld[19615]:
Jun 30 06:28:17 s2 mysqld[19615]: key_buffer_size=16777216
Jun 30 06:28:17 s2 mysqld[19615]: read_buffer_size=131072
Jun 30 06:28:17 s2 mysqld[19615]: max_used_connections=49
Jun 30 06:28:17 s2 mysqld[19615]: max_connections=100
Jun 30 06:28:17 s2 mysqld[19615]: threads_connected=2
Jun 30 06:28:17 s2 mysqld[19615]: It is possible that mysqld could use up to
Jun 30 06:28:17 s2 mysqld[19615]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
Jun 30 06:28:17 s2 mysqld[19615]: bytes of memory
Jun 30 06:28:17 s2 mysqld[19615]: Hope that's ok; if not, decrease some variables in the equation.
Jun 30 06:28:17 s2 mysqld[19615]:
Jun 30 06:28:17 s2 mysqld_safe[28586]: Number of processes running now: 0
Jun 30 06:28:17 s2 mysqld_safe[28588]: restarted
Jun 30 06:28:17 s2 mysqld[28591]: 070630 6:28:17 InnoDB: Database was not shut down normally!
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: Starting crash recovery.
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: Reading tablespace information from the .ibd files...
Jun 30 06:28:17 s2 mysqld[28591]: 070630 6:28:17 InnoDB: Operating system error number 2 in a file operation.
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: The error means the system cannot find the path specified.
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: If you are installing InnoDB, remember that you must create
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: directories yourself, InnoDB does not create them.
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: File name ./mysql.sock
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: File operation call: 'stat'.
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: Error: os_file_readdir_next_file() returned -1 in
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: directory .
Jun 30 06:28:17 s2 mysqld[28591]: InnoDB: Crash recovery may have failed for some .ibd files!
Jun 30 06:28:24 s2 mysqld[28591]: InnoDB: Restoring possible half-written data pages from the doublewrite
Jun 30 06:28:24 s2 mysqld[28591]: InnoDB: buffer...
Jun 30 06:28:25 s2 mysqld[28591]: 070630 6:28:25 InnoDB: Starting log scan based on checkpoint at
Jun 30 06:28:25 s2 mysqld[28591]: InnoDB: log sequence number 0 290004594.
Jun 30 06:28:25 s2 mysqld[28591]: InnoDB: Doing recovery: scanned up to log sequence number 0 290004594
Jun 30 06:28:25 s2 mysqld[28591]: InnoDB: Last MySQL binlog file position 0 28532269, file name /var/log/mysql/mysql-bin.000046
Jun 30 06:28:25 s2 mysqld[28591]: 070630 6:28:25 InnoDB: Started; log sequence number 0 290004594
Jun 30 06:28:25 s2 mysqld[28591]: 070630 6:28:25 [Warning] 'user' entry 'root@s2' ignored in --skip-name-resolve mode.
Jun 30 06:28:25 s2 mysqld[28591]: 070630 6:28:25 [Note] /usr/sbin/mysqld: ready for connections.
Jun 30 06:28:25 s2 mysqld[28591]: Version: '5.0.22-Debian_0ubuntu6.06.3' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution


I searched on net but I cannot find any solution .. It repeats every day at 06:28 am .. missed I something in config file?

Thanks for any idea

SupuS

[till]

Please check if any cronjobs run at this time and that you have enough free space on your harddrive(s).

[SupuS]

Please check if any cronjobs run at this time and that you have enough free space on your harddrive(s).

Hi till

default daily cron runs before ..

Jun 30 06:25:01 s2 /USR/SBIN/CRON[28354]: (root) CMD (test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily)


but I tested this command and without mysql error and root crontab is here:

# crontab -l
30 00 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/logs.php &> /dev/null
59 23 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/ftp_logs.php &> /dev/null
59 23 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/mail_logs.php &> /dev/null
59 23 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/cleanup.php &> /dev/null
0 4 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/webalizer.php &> /dev/null
0,30 * * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/check_services.php &> /dev/null
15 3,15 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/quota_msg.php &> /dev/null
40 00 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/traffic.php &> /dev/null
05 02 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/backup.php &> /dev/null
0 4 * * * /root/ispconfig/php/php /root/ispconfig/scripts/shell/awstats.php &> /dev/null


and about harddrive space:

#
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 9,2G 5,3G 3,5G 61% /
varrun 1007M 112K 1007M 1% /var/run
varlock 1007M 4,0K 1007M 1% /var/lock
udev 1007M 76K 1007M 1% /dev
devshm 1007M 0 1007M 0% /dev/shm
lrm 1007M 22M 986M 3% /lib/modules/2.6.15-23-amd64-generic/volatile
/dev/sda1 89M 18M 67M 21% /boot
/dev/sda5 9,2G 551M 8,2G 7% /tmp
/dev/sda6 47G 19G 27G 41% /var

[falko]

I think 6:28h could be the time when cron.daily runs. What's the output of ls -l /etc/cron.daily?

[SupuS]

I think 6:28h could be the time when cron.daily runs. What's the output of ls -l /etc/cron.daily?

Hi falko

here is output:


# ls -l /etc/cron.daily
total 52
-rwxr-xr-x 1 root root 5566 2006-04-18 21:47 apt
-rwxr-xr-x 1 root root 314 2006-04-03 16:43 aptitude
-rwxr-xr-x 1 root root 502 2005-07-07 13:48 bsdmainutils
-rwxr-xr-x 1 root root 419 2005-07-05 15:16 find
-rwxr-xr-x 1 root root 577 2005-04-24 11:43 chkrootkit
-rwxr-xr-x 1 root root 89 2005-05-26 11:47 logrotate
-rwxr-xr-x 1 root root 946 2005-09-26 17:13 man-db
-rwxr-xr-x 1 root root 345 2005-06-28 09:57 quota
-rwxr-xr-x 1 root root 585 2006-12-01 16:32 rkhunter
-rwxr-xr-x 1 root root 3227 2005-11-15 13:46 standard
-rwxr-xr-x 1 root root 1307 2005-09-23 22:07 sysklogd
-rwxr-xr-x 1 root root 1449 2005-10-25 16:52 webalizer

[falko]

Hm... Can you check all the scripts in /etc/cron.daily if they do something with MySQL?

[SupuS]

Solved .. I switched off backup bin files by commenting out this line:

#log-bin = /var/log/mysql/mysql-bin.log

in my.cnf but I forgot comment these two lines too:


expire-logs-days = 20
max_binlog_size = 104857600


Now I have commented all these lines and error disappears. In my versin of my.cnf unfortunatelly is not this important line:

# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian! :rolleyes:

Thanks for your help