Error establishing a database connection

Hello!

I have a problem:

Does not go into phpmyadmin

http://178.79.132.47/phpmyadmin/

and the error Error establishing a database connection.

http://sgustok.org/

"ps aux"

[email protected]:~# ps aux

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND

root 1 0.0 0.1 2732 1240 ? Ss 20:57 0:01 /sbin/init

root 2 0.0 0.0 0 0 ? S 20:57 0:00 [kthreadd]

root 3 0.0 0.0 0 0 ? S 20:57 0:00 [ksoftirqd/0]

root 4 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/0:0]

root 5 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/u:0]

root 6 0.0 0.0 0 0 ? S 20:57 0:00 [migration/0]

root 7 0.0 0.0 0 0 ? S 20:57 0:00 [migration/1]

root 8 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/1:0]

root 9 0.0 0.0 0 0 ? S 20:57 0:00 [ksoftirqd/1]

root 10 0.0 0.0 0 0 ? S 20:57 0:00 [migration/2]

root 11 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/2:0]

root 12 0.0 0.0 0 0 ? S 20:57 0:00 [ksoftirqd/2]

root 13 0.0 0.0 0 0 ? S 20:57 0:00 [migration/3]

root 14 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/3:0]

root 15 0.0 0.0 0 0 ? S 20:57 0:00 [ksoftirqd/3]

root 16 0.0 0.0 0 0 ? S< 20:57 0:00 [khelper]

root 17 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/u:1]

root 21 0.0 0.0 0 0 ? S 20:57 0:00 [xenwatch]

root 22 0.0 0.0 0 0 ? S 20:57 0:00 [xenbus]

root 142 0.0 0.0 0 0 ? S 20:57 0:00 [sync_supers]

root 144 0.0 0.0 0 0 ? S 20:57 0:00 [bdi-default]

root 146 0.0 0.0 0 0 ? S< 20:57 0:00 [kblockd]

root 156 0.0 0.0 0 0 ? S< 20:57 0:00 [md]

root 240 0.0 0.0 0 0 ? S< 20:57 0:00 [rpciod]

root 242 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/1:1]

root 271 0.0 0.0 0 0 ? S 20:57 0:01 [kswapd0]

root 272 0.0 0.0 0 0 ? SN 20:57 0:00 [ksmd]

root 273 0.0 0.0 0 0 ? S 20:57 0:00 [fsnotify_mark]

root 277 0.0 0.0 0 0 ? S 20:57 0:00 [ecryptfs-kthrea]

root 279 0.0 0.0 0 0 ? S< 20:57 0:00 [nfsiod]

root 282 0.0 0.0 0 0 ? S 20:57 0:00 [jfsIO]

root 283 0.0 0.0 0 0 ? S 20:57 0:00 [jfsCommit]

root 284 0.0 0.0 0 0 ? S 20:57 0:00 [jfsCommit]

root 285 0.0 0.0 0 0 ? S 20:57 0:00 [jfsCommit]

root 286 0.0 0.0 0 0 ? S 20:57 0:00 [jfsCommit]

root 287 0.0 0.0 0 0 ? S 20:57 0:00 [jfsSync]

root 288 0.0 0.0 0 0 ? S< 20:57 0:00 [xfsmrucache]

root 289 0.0 0.0 0 0 ? S< 20:57 0:00 [xfslogd]

root 290 0.0 0.0 0 0 ? S< 20:57 0:00 [xfsdatad]

root 291 0.0 0.0 0 0 ? S< 20:57 0:00 [xfsconvertd]

root 292 0.0 0.0 0 0 ? S< 20:57 0:00 [crypto]

root 854 0.0 0.0 0 0 ? S 20:57 0:00 [khvcd]

root 966 0.0 0.0 0 0 ? S< 20:57 0:00 [kpsmoused]

root 967 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/0:1]

root 996 0.0 0.0 0 0 ? S 20:57 0:00 [kjournald]

root 1000 0.0 0.0 840 4 ? Ss 20:57 0:00 /usr/sbin/sshd

root 1026 0.0 0.0 2368 596 ? S 20:57 0:00 upstart-udev-bridge –daemon

root 1028 0.0 0.0 2368 692 ? S ~~root 1202 0.0 0.0 2364 576 ? S< 20:57 0:00 udevd --daemon

root 1204 0.0 0.0 2364 580 ? S< 20:57 0:00 udevd --daemon

root 1594 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/3:1]

root 1618 0.0 0.0 0 0 ? S 20:57 0:00 [kworker/2:1]

syslog 1936 0.0 0.1 28452 1256 ? Sl 20:57 0:00 rsyslogd -c4

root 1958 0.0 0.0 2284 252 ? Ss 20:57 0:00 dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.l

daemon 1980 0.0 0.0 2300 356 ? Ss 20:57 0:00 atd

root 1984 0.0 0.1 2428 896 ? Ss 20:57 0:00 cron

root 2024 0.0 0.1 5600 932 ? Ss 20:57 0:00 /usr/sbin/sshd

ntp 2112 0.0 0.1 4460 1372 ? Ss 20:57 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 102:104

root 2140 0.0 0.2 5864 1804 ? Ss 20:57 0:00 /usr/lib/postfix/master

postfix 2161 0.0 0.2 5880 1696 ? S 20:57 0:00 pickup -l -t fifo -u -c

root 2207 0.0 0.3 24844 2944 ? Sl 20:57 0:01 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock

root 2221 0.0 0.0 1840 552 hvc0 Ss+ 20:57 0:00 /sbin/getty -8 38400 hvc0

root 2225 0.0 0.0 0 0 ? S 20:57 0:00 [flush-202:0]

root 7808 0.0 0.3 8536 2744 ? Rs 21:34 0:00 sshd: [email protected]/0

root 7901 0.0 0.2 3280 1860 pts/0 Ss 21:35 0:00 -bash

root 12980 0.3 1.1 35780 8772 ? Ss 22:03 0:01 /usr/sbin/apache2 -k start

root 12986 0.0 0.5 35780 4476 ? S 22:03 0:00 /usr/sbin/apache2 -k start

root 12987 0.0 0.5 35780 4476 ? S 22:03 0:00 /usr/sbin/apache2 -k start

root 13039 0.0 0.5 35780 4480 ? S 22:03 0:00 /usr/sbin/apache2 -k start

root 13050 0.0 0.5 35780 4480 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13051 0.0 0.5 35780 4480 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13097 0.0 0.5 35780 4484 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13133 0.0 0.5 35780 4484 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13159 0.0 0.5 35780 4484 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13160 0.0 0.5 35780 4484 ? S 22:04 0:00 /usr/sbin/apache2 -k start

root 13161 0.0 0.5 35780 4484 ? S 22:04 0:00 /usr/sbin/apache2 -k start

postfix 13664 0.0 0.2 8456 2292 ? S 22:07 0:00 qmgr -l -t fifo -u

postfix 13825 0.0 0.2 8464 2252 ? S 22:08 0:00 smtp -n amavis -t unix -u -c -o smtpdatadonetimeout=1200 -o smtpsendxforwardcommand=ye

postfix 13828 0.0 0.2 8464 2260 ? S 22:08 0:00 smtp -n amavis -t unix -u -c -o smtpdatadonetimeout=1200 -o smtpsendxforwardcommand=ye

root 14156 0.0 0.0 0 0 ? Z 22:08 0:00 [sh] root 14158 0.0 0.1 2484 956 pts/0 R+ 22:08 0:00 ps aux

why?~~

15 Replies

@obs:

Except for those upgrading from 5.1 to 5.5 with myisam databases….
Or installing software that forces MyISAM for some reason. (Referential integrity error?! What does it MEAN!!)

In other news, MySQL 5.5 will likely be shipping in Ubuntu 12.04, hopefully putting an end to this MyISAM-by-default nonsense. (Ha.)

Once you have your data restored from backup, consider converting your tables to InnoDB, which is somewhat less prone to these sorts of disasters.

MySQL isn't running. I'm assuming it's supposed to be running on whatever machine that "ps aux" is from.

You didn't really give enough information for anyone to say.

@phyber:

MySQL isn't running. I'm assuming it's supposed to be running on whatever machine that "ps aux" is from.

You didn't really give enough information for anyone to say.

daemon 1935 0.0 0.0 2300 8 ? Ss 15:22 0:00 atd

root 1936 0.0 0.0 2428 256 ? Ss 15:22 0:00 cron

root 2045 0.0 0.0 2284 4 ? Ss 15:22 0:00 dhclient3 -e IF

root 2056 0.0 0.0 5864 264 ? Ss 15:22 0:00 /usr/lib/postfi

root 2074 0.0 0.0 5600 48 ? Ss 15:22 0:00 /usr/sbin/sshd

ntp 2122 0.0 0.0 4460 204 ? Ss 15:22 0:00 /usr/sbin/ntpd

postfix 2136 0.0 0.0 5880 148 ? S 15:22 0:00 pickup -l -t fi

root 2190 0.0 0.0 0 0 ? S 15:22 0:00 [flush-202:0]

root 2203 0.0 0.2 24844 1788 ? Sl 15:22 0:00 /usr/bin/python

root 2213 0.0 0.0 2764 104 hvc0 Ss 15:22 0:00 /bin/login –

root 2644 0.0 0.0 8532 172 ? Ss 15:25 0:00 sshd: [email protected]

root 2659 0.0 0.0 2052 40 ? Ss 15:25 0:00 /usr/lib/openss

root 3673 0.0 0.1 3344 968 hvc0 S 15:31 0:00 -bash

root 9391 0.6 1.1 35692 8600 ? Ss 16:05 0:00 /usr/sbin/apach

root 9396 0.0 0.5 35692 4360 ? S 16:05 0:00 /usr/sbin/apach

root 9397 0.0 0.5 35692 4360 ? S 16:05 0:00 /usr/sbin/apach

root 9399 0.0 0.5 35692 4360 ? S 16:05 0:00 /usr/sbin/apach

root 9401 0.0 0.5 35692 4360 ? S 16:05 0:00 /usr/sbin/apach

root 9402 0.0 0.5 35692 4360 ? S 16:05 0:00 /usr/sbin/apach

root 9407 0.0 0.5 35692 4364 ? S 16:05 0:00 /usr/sbin/apach

root 9419 0.0 0.5 35692 4368 ? S 16:05 0:00 /usr/sbin/apach

www-data 9544 0.0 0.6 36172 5224 ? S 16:06 0:00 /usr/sbin/apach

root 9551 0.0 0.0 0 0 ? Z 16:06 0:00 [sh] root 9554 0.0 0.1 2484 968 hvc0 R+ 16:06 0:00 ps aux

[email protected]:~# /etc/init.d/mysql start

Rather than invoking init scripts through /etc/init.d, use the service(8)

utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an

Upstart job, you may also use the start(8) utility, e.g. start mysql

start: Job failed to start

Check your mysql log files usually located in /var/log/mysql

/var/log/mysqlerror.log

100616 16:19:00 [Note] /usr/sbin/mysqld: Normal shutdown

100616 16:19:00 [Note] Event Scheduler: Purging the queue. 0 events
100616 16:19:00  InnoDB: Starting shutdown...
100616 16:19:02  InnoDB: Shutdown completed; log sequence number 0 44273
100616 16:19:02 [Note] /usr/sbin/mysqld: Shutdown complete

111122 11:56:05 [Note] Plugin 'FEDERATED' is disabled.
111122 11:56:05  InnoDB: Started; log sequence number 0 44303
111122 11:56:05 [Note] Event Scheduler: Loaded 0 events
111122 11:56:05 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.41-3ubuntu12.3'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
111122 11:56:10 [ERROR] /usr/sbin/mysqld: Table './c1sgustokdesign/wp_comments' is marked as crashed and should be repaired
111122 11:56:10 [Warning] Checking table:   './c1sgustokdesign/wp_comments'
111122 11:56:10 [Warning] Recovering table: './c1sgustokdesign/wp_comments'
111122 11:56:11 [Note] Retrying repair of: './c1sgustokdesign/wp_comments' with keycache
111122 11:56:15 [ERROR] /usr/sbin/mysqld: Table './c1sgustokmag/wp_3_postmeta' is marked as crashed and should be repaired
111122 11:56:15 [Warning] Checking table:   './c1sgustokmag/wp_3_postmeta'
111122 11:56:15 [Warning] Recovering table: './c1sgustokmag/wp_3_postmeta'
111122 11:56:15 [Note] Found 2909 of 2908 rows when repairing './c1sgustokmag/wp_3_postmeta'
111122 11:56:15 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed x9000

Your database has crashed and corrupted your tables, run the following:

myisamchk --recover /var/lib/mysql/*/*.MYI

it will do it's best to repair your tables however you may still have corrupt data, if you do load a backup if you have one.

@hoopycat:

In other news, MySQL 5.5 will likely be shipping in Ubuntu 12.04, hopefully putting an end to this MyISAM-by-default nonsense. (Ha.)

Once you have your data restored from backup, consider converting your tables to InnoDB, which is somewhat less prone to these sorts of disasters.
Except for those upgrading from 5.1 to 5.5 with myisam databases….

@hoopycat:

Referential integrity error?! What does it MEAN!!
Clearly it's accusing you of having questionable academic practices.

@obs:

Your database has crashed and corrupted your tables, run the following:

myisamchk --recover /var/lib/mysql/*/*.MYI

it will do it's best to repair your tables however you may still have corrupt data, if you do load a backup if you have one.

****Run to Launch Lish Ajax Console »

all the same:****

Does not go into phpmyadmin

http://178.79.132.47/phpmyadmin/

and the error Error establishing a database connection.

http://sgustok.org/

Did you attempt to start mysql afterwards? run start mysql

@obs:

Did you attempt to start mysql afterwards? run start mysql

[email protected]:~# start mysql

start: Job failed to start

&

[email protected]:~# /etc/init.d/mysql start

Rather than invoking init scripts through /etc/init.d, use the service(8)

utility, e.g. service mysql start

Since the script you are attempting to invoke has been converted to an

Upstart job, you may also use the start(8) utility, e.g. start mysql

start: Job failed to start

Check your mysql logs again it should show some new error messages.

@obs:

Check your mysql logs again it should show some new error messages.

/var/log/mysql/error.log

111123 12:54:42 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_78a_0.MYI'; try to repair it
111123 12:54:42 [ERROR] /usr/sbin/mysqld: Incorrect key file for table '/tmp/#sql_78a_0.MYI'; try to repair it
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/monitor_data' is marked as crashed and last (automatic?) repair failed
111123 12:55:01 [ERROR] /usr/sbin/mysqld: Table './dbispconfig/m

/var/log/syslog

Nov 23 18:02:35 li188-47 postfix/error[10080]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
Nov 23 18:02:35 li188-47 postfix/error[10081]: 89DAEB4076: to=<[email protected]>, relay=none, delay=181583, delays=181582/1.1/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
Nov 23 18:02:35 li188-47 postfix/error[10081]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Nov 23 18:02:35 li188-47 postfix/error[10081]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
Nov 23 18:02:36 li188-47 postfix/qmgr[10069]: warning: private/retry socket: malformed response
Nov 23 18:02:36 li188-47 postfix/qmgr[10069]: warning: transport retry failure -- see a previous warning/fatal/panic logfile record for the problem description
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/error pid 10075 exit status 1
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: /usr/lib/postfix/error: bad command startup -- throttling
Nov 23 18:02:36 li188-47 postfix/qmgr[10069]: D0ED8E27D: to=<[email protected]>, orig_to=<root>, relay=none, delay=301035, delays=301033/2.1/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)
Nov 23 18:02:36 li188-47 postfix/qmgr[10069]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Nov 23 18:02:36 li188-47 postfix/qmgr[10069]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): table lookup problem
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/error pid 10076 exit status 1
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/error pid 10079 exit status 1
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/error pid 10080 exit status 1
Nov 23 18:02:36 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/error pid 10081 exit status 1
Nov 23 18:02:37 li188-47 postfix/master[2131]: warning: process /usr/lib/postfix/qmgr pid 10069 exit status 1
Nov 23 18:03:01 li188-47 CRON[10133]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:04:01 li188-47 CRON[10260]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:05:01 li188-47 CRON[10387]: (getmail) CMD (/usr/local/bin/run-getmail.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:05:01 li188-47 CRON[10388]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:06:01 li188-47 CRON[10515]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:07:01 li188-47 CRON[10641]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: C8130E234: from=<[email protected]>, size=876, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: 9FE5FA8042: from=<[email protected]>, size=715, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: D2047A801A: from=<[email protected]>, size=715, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: CD4A1E27C: from=<[email protected]>, size=876, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: 32D89A8009: from=<[email protected]>, size=2719, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: F1274A801E: from=<[email protected]>, size=1673, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: 89DAEB4076: from=<[email protected]>, size=1514, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: D0ED8E27D: from=<[email protected]>, size=713, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 postfix/qmgr[10711]: CB980E236: from=<[email protected]>, size=877, nrcpt=1 (queue active)
Nov 23 18:07:34 li188-47 rsyslogd: /var/log/mail.log
Nov 23 18:07:34 li188-47 rsyslogd: /var/log/mail.info
Nov 23 18:07:34 li188-47 postfix/smtp[10712]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Nov 23 18:07:34 li188-47 postfix/bounce[10714]: fatal: append file defer C8130E234: No space left on device
Nov 23 18:07:34 li188-47 postfix/smtp[10713]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Nov 23 18:07:34 li188-47 postfix/bounce[10715]: fatal: append file defer 9FE5FA8042: No space left on device
Nov 23 18:07:35 li188-47 postfix/smtp[10712]: warning: C8130E234: defer service failure
Nov 23 18:07:35 li188-47 postfix/smtp[10712]: C8130E234: to=<[email protected]>, orig_to=<root>, relay=none, delay=387751, delays=387751/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Nov 23 18:07:35 li188-47 postfix/smtp[10712]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Nov 23 18:07:35 li188-47 postfix/smtp[10712]: fatal: mysql:/etc/postfix/mysql-virtual_relaydomains.cf(0,lock|fold_fix): tablNov 23 18:56:18 li188-47 kernel: imklog 4.2.0, log source = /proc/kmsg started.
Nov 23 18:56:18 li188-47 rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1922" x-info="http://www.rsyslog.com"] (re)start
Nov 23 18:56:18 li188-47 rsyslogd: rsyslogd's groupid changed to 103
Nov 23 18:56:18 li188-47 rsyslogd: rsyslogd's userid changed to 101
Nov 23 18:56:18 li188-47 rsyslogd-2039: Could no open output file '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Nov 23 18:56:18 li188-47 kernel: Reserving virtual address space above 0xf5800000
Nov 23 18:56:18 li188-47 kernel: Linux version 2.6.39.1-linode34 ([email protected]) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #1 SMP Tue Jun 21 10:29:24 EDT 2011
Nov 23 18:56:18 li188-47 kernel: KERNEL supported cpus:
Nov 23 18:56:18 li188-47 kernel:  Intel GenuineIntel
Nov 23 18:56:18 li188-47 kernel:  AMD AuthenticAMD
Nov 23 18:56:18 li188-47 kernel: released 0 pages of unused memory
Nov 23 18:56:18 li188-47 kernel: Set 0 page(s) to 1-1 mapping.
Nov 23 18:56:18 li188-47 kernel: BIOS-provided physical RAM map:
Nov 23 18:56:18 li188-47 kernel: Xen: 0000000000000000 - 00000000000a0000 (usable)
Nov 23 18:56:18 li188-47 kernel: Xen: 00000000000a0000 - 0000000000100000 (reserved)
Nov 23 18:56:18 li188-47 kernel: Xen: 0000000000100000 - 0000000030800000 (usable)
Nov 23 18:56:18 li188-47 kernel: NX (Execute Disable) protection: active
Nov 23 18:56:18 li188-47 kernel: DMI not present or invalid.
Nov 23 18:56:18 li188-47 kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Nov 23 18:56:18 li188-47 kernel: e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Nov 23 18:56:18 li188-47 kernel: last_pfn = 0x30800 max_arch_pfn = 0x1000000
Nov 23 18:56:18 li188-47 kernel: initial memory mapped : 0 - 00b52000
Nov 23 18:56:18 li188-47 kernel: Base memory trampoline at [c009f000] 9f000 size 4096
Nov 23 18:56:18 li188-47 kernel: init_memory_mapping: 0000000000000000-000000002d3fe000
Nov 23 18:56:18 li188-47 kernel: 0000000000 - 002d3fe000 page 4k
Nov 23 18:56:18 li188-47 kernel: kernel direct mapping tables up to 2d3fe000 @ 9e5000-b52000
Nov 23 18:56:18 li188-47 kernel: xen: setting RW the range b43000 - b52000
Nov 23 18:56:18 li188-47 kernel: 52MB HIGHMEM available.
Nov 23 18:56:18 li188-47 kernel: 723MB LOWMEM available.
Nov 23 18:56:18 li188-47 kernel:  mapped low ram: 0 - 2d3fe000
Nov 23 18:56:18 li188-47 kernel:  low ram: 0 - 2d3fe000
Nov 23 18:56:18 li188-47 kernel: Zone PFN ranges:
Nov 23 18:56:18 li188-47 kernel:  DMA      0x00000010 -> 0x00001000
Nov 23 18:56:18 li188-47 kernel:  Normal   0x00001000 -> 0x0002d3fe
Nov 23 18:56:18 li188-47 kernel:  HighMem  0x0002d3fe -> 0x00030800
Nov 23 18:56:18 li188-47 kernel: Movable zone start PFN for each node
Nov 23 18:56:18 li188-47 kernel: early_node_map[2] active PFN ranges
Nov 23 18:56:18 li188-47 kernel:    0: 0x00000010 -> 0x000000a0
Nov 23 18:56:18 li188-47 kernel:    0: 0x00000100 -> 0x00030800
Nov 23 18:56:18 li188-47 kernel: On node 0 totalpages: 198544
Nov 23 18:56:18 li188-47 kernel: free_area_init_node: node 0, pgdat c0825340, node_mem_map ecded200
Nov 23 18:56:18 li188-47 kernel:  DMA zone: 32 pages used for memmap
Nov 23 18:56:18 li188-47 kernel:  DMA zone: 0 pages reserved
Nov 23 18:56:18 li188-47 kernel:  DMA zone: 3952 pages, LIFO batch:0
Nov 23 18:56:18 li188-47 kernel:  Normal zone: 1416 pages used for memmap
Nov 23 18:56:18 li188-47 kernel:  Normal zone: 179830 pages, LIFO batch:31
Nov 23 18:56:18 li188-47 kernel:  HighMem zone: 105 pages used for memmap
Nov 23 18:56:18 li188-47 kernel:  HighMem zone: 13209 pages, LIFO batch:3
Nov 23 18:56:18 li188-47 kernel: Using APIC driver default
Nov 23 18:56:18 li188-47 kernel: SMP: Allowing 4 CPUs, 0 hotplug CPUs
Nov 23 18:56:18 li188-47 kernel: Local APIC disabled by BIOS -- you can enable it with "lapic"
Nov 23 18:56:18 li188-47 kernel: APIC: disable apic facility
Nov 23 18:56:18 li188-47 kernel: APIC: switched to apic NOOP
Nov 23 18:56:18 li188-47 kernel: nr_irqs_gsi: 16
Nov 23 18:56:18 li188-47 kernel: Allocating PCI resources sta</root></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></root></[email protected]></[email protected]>

/var/log/apache2/error.log

DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.
piped log program ' /usr/local/ispconfig/server/scripts/vlogger -s access.log -t "%Y%m%d-access.log" -d "/etc/vlogger-dbi.conf" /var/log/ispconfig/httpd' failed unexpectedly
DBI connect('database=dbispconfig;host=localhost:3306','ispconfig',...) failed: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/local/ispconfig/server/scripts/vlogger line 255
DBI Error:  at /usr/local/ispconfig/server/scripts/vlogger line 255.

The same errors as before, looks like myisamchk can't fix it, load a backup then convert to innodb which is better at recovering from errors.

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct