Onderwerp: Plesk Database error

Ik kan niet meer op Plesk (8.0.1) komen. Dit is de error die ik krijg:

ERROR: PleskFatalException
Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

0: /usr/local/psa/admin/plib/common_func.php3:175
psaerror(string 'Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)')
1: /usr/local/psa/admin/auto_prepend/auth.php3:88


Alle databases zijn niet meer bereikbaar. Een reboot heeft geen zin gehad.
Zou iemand me raad kunnen geven?

mysql restarten...

Dom vraagje: Hoe doe je dat? Bij 'service mysqld restart' krijg ik 'failed'
*Onze technische man is met vakantie.

Dit komt echt heel vervelend uit. Door die stroomstoring op RedBus was onze server gecrasht en zijn we meer dan een halve week offline geweest. En nu krijgen we weer zoiets...

Ik zou zeggen pak de mysql log en de messages log er eens bij. Die kunnen je waarschijnlijk meer vertellen waarom mysqld niet meer wil starten

Bedoel je dit?

/var/log/mysqld.log {
missingok
create 0640 mysql mysql
prerotate
[ -e /var/lock/subsys/mysqld ] && /bin/kill -HUP `cat /var/run/mysqld/mysqld.pid 2> /dev/null ` || /bin/true
endscript
postrotate
[ -e /var/lock/subsys/mysqld ] && /bin/kill -HUP `cat /var/run/mysqld/mysqld.pid 2> /dev/null ` || /bin/true
endscript
}


Als ik "service mysqld status" uitvoer krijg ik te zien:
mysqld dead but subsys locked

ps aux | grep mysql
root 5840 0.0 0.0 5648 588 pts/0 S 18:51 0:00 grep mysql

Gedeeltelijk.

Geef ook eens het laatste deel van je messages log.

Number of processes running now: 0
061006 17:11:26 mysqld restarted
061006 17:11:26 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 17:11:28 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 20090248
061006 17:11:31 InnoDB: Assertion failure in thread 3209921632 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfe7f81c, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 17:11:31 mysqld ended

061006 18:11:32 mysqld started
061006 18:11:33 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 18:11:44 InnoDB: Assertion failure in thread 3210310752 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbffa7b9c, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 18:11:44 mysqld ended

061006 18:31:55 mysqld started
061006 18:31:55 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 18:31:55 InnoDB: Assertion failure in thread 3209802848 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfef571c, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 18:31:55 mysqld ended

061006 18:40:24 mysqld started
061006 18:40:24 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 18:40:24 InnoDB: Assertion failure in thread 3209708640 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbff95c7c, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 18:40:24 mysqld ended

061006 18:42:20 mysqld started
061006 18:42:20 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 18:42:20 InnoDB: Assertion failure in thread 3210155104 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfefa4fc, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 18:42:20 mysqld ended

061006 19:00:02 mysqld started
061006 19:00:02 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
061006 19:00:02 InnoDB: Assertion failure in thread 3210241120 in file os0file.c line 1062
InnoDB: We intentionally generate a memory trap.
InnoDB: Send a detailed bug report to mysql@lists.mysql.com
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.
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=8388600
record_buffer=131072
sort_buffer=2097144
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (record_buffer + sort_buffer)*max_connections = 225791 K
bytes of memory
Hope that's ok, if not, decrease some variables in the equation

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...
Bogus stack limit or frame pointer, fp=0xbfefaf7c, stack_bottom=0x5ab6f490, thread_stack=65536, aborting backtrace.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x59f52810 is invalid pointer
thd->thread_id=-1

Successfully dumped variables, if you ran with --log, take a look at the
details of what thread -1 did to cause the crash. In some cases of really
bad corruption, the values shown above may be invalid

The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains
information that should help you find out what is causing the crash
061006 19:00:02 mysqld ended

Als je zoekt op google op "mysqld got signal 11" dan krijg je velle mogelijkheden en oplossingen terug van hardware problemen tot corrupte bin bestanden.

Ik durf het bijna niet te vragen, maar zou iemand me het alsjeblieft meer kunnen 'voorkauwen'? Ik zit hier werkelijk waar een potje te janken (*is vrouw) na wat er allemaal gebeurd is afgelopen week. Logisch nadenken is momenteel moeilijk, zeker als je nog een lege maag hebt...

Voeg me maar toe op msn, dan zal ik kijken wat ik voor je kan doen...

mike [at] perfect-id.com

Oorspronkelijk geplaatst door schaapje

Ik durf het bijna niet te vragen, maar zou iemand me het alsjeblieft meer kunnen 'voorkauwen'? Ik zit hier werkelijk waar een potje te janken (*is vrouw) na wat er allemaal gebeurd is afgelopen week. Logisch nadenken is momenteel moeilijk, zeker als je nog een lege maag hebt...

Maak in my.cnf de waarde voor innodb_additional_mem_pool_size eens twee maal zo groot.

Voor zover ik heb kunnen zien, waren er geen InnoDB databases op het systeem aanwezig. Ik heb InnoDB uit de my.cnf verwijderd en draait weer als een zonnetje.

Feit is wel dat je technische man de werkelijke oorzaak moet zoeken van het probleem, dit is slechts een workaround.

Oorspronkelijk geplaatst door gjtje

Maak in my.cnf de waarde voor innodb_additional_mem_pool_size eens twee maal zo groot.

Drie hoeraatjes voor Mike! Alles werkt weer naar behoren!

Nogmaals bedankt, Mike! ;-)

Een ander probleem heeft zich voorgedaan: de onderstaande foutmelding en geen mail meer kunnen ophalen.

Code:

ERROR: PleskMainDBException
MySQL query failed: Can't find file: 'misc.MYD' (errno: 2)

0: /usr/local/psa/admin/plib/common_func.php3:235
	db_query(string 'select param, val from misc')
1: /usr/local/psa/admin/plib/common_func.php3:473
	get_param(string 'login_timeout')
2: /usr/local/psa/admin/plib/class.Session.php:121
	Session->Session()
3: /usr/local/psa/admin/auto_prepend/auth.php3:149