MRatWork Forum by Mustafa Ramadhan
Sawo Project - Kloxo-MR Discussions => Kloxo-MR Technical Helps => Topic started by: rAXv2 on 2013-07-10, 10:43:18
-
i am getting this error since last night
On every script i run
Could not connect: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)
Tell me what to do and where are mysql database located i need to take backup
-
my.cnf
[mysqld]
default-storage-engine=innodb
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mysqld according to the
# instructions in http://fedoraproject.org/wiki/Systemd
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
#
# include all files from the config directory
#
!includedir /etc/my.cnf.d
-
Inform here your 'sh /script/sysinfo'.
Try reset password with 'sh /script/reset-mysql-root-password YourNewPassword'.
-
mysql.sock file missing from temp and var/lib/mysql
[root@server script]# sh ./sysinfo
Could not open database connection.
-
kindly check ur gmail...
-
What is output of 'netstat -nltp' and 'df -h' ?
have you tried '/etc/init.d/mysqld restart' ?
-
[root@server /]# netstat -nltp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address Stat e PID/Program name
tcp 0 0 151.236.10.199:53 0.0.0.0:* LIST EN 707/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LIST EN 707/named
tcp 0 0 0.0.0.0:22 0.0.0.0:* LIST EN 838/sshd
tcp 0 0 0.0.0.0:25 0.0.0.0:* LIST EN 760/tcpserver
tcp 0 0 0.0.0.0:7777 0.0.0.0:* LIST EN 1264/kloxo.httpd
tcp 0 0 0.0.0.0:993 0.0.0.0:* LIST EN 756/tcpserver
tcp 0 0 0.0.0.0:7778 0.0.0.0:* LIST EN 1264/kloxo.httpd
tcp 0 0 0.0.0.0:995 0.0.0.0:* LIST EN 779/tcpserver
tcp 0 0 127.0.0.1:57797 0.0.0.0:* LIST EN 1163/php-fpm
tcp 0 0 127.0.0.1:57798 0.0.0.0:* LIST EN 1163/php-fpm
tcp 0 0 0.0.0.0:587 0.0.0.0:* LIST EN 771/tcpserver
tcp 0 0 0.0.0.0:110 0.0.0.0:* LIST EN 770/tcpserver
tcp 0 0 0.0.0.0:143 0.0.0.0:* LIST EN 742/tcpserver
tcp 0 0 127.0.0.1:50000 0.0.0.0:* LIST EN 1163/php-fpm
tcp 0 0 0.0.0.0:465 0.0.0.0:* LIST EN 764/tcpserver
tcp 0 0 :::21 :::* LIST EN 846/xinetd
tcp 0 0 :::22 :::* LIST EN 838/sshd
tcp 0 0 :::443 :::* LIST EN 1183/httpd.event
tcp 0 0 :::80 :::* LIST EN 1183/httpd.event
[root@server /]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/simfs 50G 2.9G 48G 6% /
none 2.0G 4.0K 2.0G 1% /dev
none 2.0G 0 2.0G 0% /dev/shm
/dev/simfs 50G 2.9G 48G 6% /var/named/chroot/etc/named
/dev/simfs 50G 2.9G 48G 6% /var/named/chroot/etc/named.rfc1912.zones
/dev/simfs 50G 2.9G 48G 6% /var/named/chroot/usr/lib64/bind
/dev/simfs 50G 2.9G 48G 6% /var/named/chroot/etc/named.iscdlv.key
[root@server /]# /etc/init.d/mysqld restart
Stopping mysqld: [ OK ]
MySQL Daemon failed to start.
Starting mysqld: [FAILED]
[root@server /]#
-
The problem is that mysqld is not running.
First try a reboot of the server.
if this not solve you must check mysql logs to understand why mysql doesn't start
logs are located in /var/log
-
here is the file
http://txtup.co/CNgDi (http://txtup.co/CNgDi)
mirror
http://txtup.net/CNgDi (http://txtup.net/CNgDi)
-
130710 10:12:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130710 10:12:47 InnoDB: The InnoDB memory heap is disabled
130710 10:12:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130710 10:12:47 InnoDB: Compressed tables use zlib 1.2.3
130710 10:12:47 InnoDB: Using Linux native AIO
130710 10:12:47 InnoDB: Warning: io_setup() failed with EAGAIN. Will make 5 attempts before giving up.
InnoDB: Warning: io_setup() attempt 1 failed.
InnoDB: Warning: io_setup() attempt 2 failed.
InnoDB: Warning: io_setup() attempt 3 failed.
InnoDB: Warning: io_setup() attempt 4 failed.
InnoDB: Warning: io_setup() attempt 5 failed.
130710 10:12:50 InnoDB: Error: io_setup() failed with EAGAIN after 5 attempts.
InnoDB: You can disable Linux Native AIO by setting innodb_use_native_aio = 0 in my.cnf
InnoDB: Warning: Linux Native AIO disabled because os_aio_linux_create_io_ctx() failed. To get rid of this warning you can try increasing system fs.aio-max-nr to 1048576 or larger or setting innodb_use_native_aio = 0 in my.cnf
130710 10:12:50 InnoDB: Initializing buffer pool, size = 128.0M
130710 10:12:50 InnoDB: Completed initialization of buffer pool
130710 10:12:50 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 686643840
130710 10:12:50 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 686645510
130710 10:12:50 InnoDB: Error: page 1166 log sequence number 686664698
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 1051 log sequence number 686659258
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 58 log sequence number 686645929
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 60 log sequence number 686659678
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 63 log sequence number 686646348
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 560 log sequence number 686647460
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 203 log sequence number 686652381
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 205 log sequence number 686657221
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 588 log sequence number 686657221
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 208 log sequence number 686652804
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 211 log sequence number 686660928
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 402 log sequence number 686648288
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 542 log sequence number 686661772
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 225 log sequence number 686654072
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 545 log sequence number 686654072
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 227 log sequence number 686648753
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 230 log sequence number 686654495
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 546 log sequence number 686654495
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 233 log sequence number 686649176
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 235 log sequence number 686654902
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 248 log sequence number 686655748
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 1547 log sequence number 686655748
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 250 log sequence number 686657658
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 252 log sequence number 686656376
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 537 log sequence number 686662195
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 275 log sequence number 686662602
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 279 log sequence number 686651527
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 280 log sequence number 686663025
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 1569 log sequence number 686663448
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 297 log sequence number 686664294
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 591 log sequence number 686664294
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 299 log sequence number 686658418
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 538 log sequence number 686658418
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 38 130710 10:12:50 InnoDB: Error: page 2298 log sequence number 686663772
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
130710 10:12:50 Percona XtraDB (http://www.percona.com) 5.5.31-MariaDB-30.2 started; log sequence number 686645510
130710 10:12:50 [Note] Plugin 'FEEDBACK' is disabled.
130710 10:12:50 InnoDB: Error: page 998 log sequence number 686657235
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 InnoDB: Error: page 1019 log sequence number 686647129
InnoDB: is in the future! Current system log sequence number 686645510.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
130710 10:12:50 [ERROR] mysqld got signal 11 ;
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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 5.5.31-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466711 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
??:0(??)[0x7f9f6b95703e]
??:0(??)[0x7f9f6b5a21dc]
??:0(??)[0x7f9f6acd7500]
??:0(??)[0x7f9f6b8c67e8]
??:0(??)[0x7f9f6b8c68f5]
??:0(??)[0x7f9f6b8c6b3c]
??:0(??)[0x7f9f6b80a4b7]
??:0(??)[0x7f9f6b80a52d]
??:0(??)[0x7f9f6b80eab6]
??:0(??)[0x7f9f6b7f5502]
??:0(??)[0x7f9f6b8f24a5]
??:0(??)[0x7f9f6b8390da]
??:0(??)[0x7f9f6b7e6507]
??:0(??)[0x7f9f6b8f25e6]
??:0(??)[0x7f9f6b8f3a0a]
??:0(??)[0x7f9f6b8e7867]
??:0(??)[0x7f9f6b807947]
??:0(??)[0x7f9f6b7fc32c]
??:0(??)[0x7f9f6accf851]
??:0(??)[0x7f9f6964390d]
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.
130710 10:12:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
-
i think is innodb is corrupted.
If you don't use innodb in your databases try to comment from my.cnf
default-storage-engine=innodb
and add
skip-innodb
maybe you have update mysql and default engine is innodb
-
Have you run 'sh /script/mysql-convert --engine=innodb' before?.
If not, it's maybe something wrong with your innodb storage-engine of mysql.
If you found 'default-storage-engine=innodb' and 'skip-innodb', change it and then run your mysql.
Look like mysql51/mysql55 from IUS have a problem now. Many issues related to Kloxo-MR installing effect by mysql51/mysql55.
I didn't found any issue for mysql from Centos or MariaDB.