Linode.com Forum

[Alexis2]

Something weird happens on my gentoo linode, i was hoping for a fix with the last patch but it didnt do anything.

this only happens when i have a cron daemon running, happens even if there is no cron job defined, only the cron daemon up is enough to make this happen(i tried fcron, dcron,vixiecron with the same results)

mysql crashes, after a random amount of time,

here's what i get in the logs :

Number of processes running now: 1
mysqld process hanging, pid 6676 - killed
050214 07:44:05 mysqld restarted
/usr/sbin/mysqld: ready for connections.
Version: '4.0.23' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-4.0.23-r1

Number of processes running now: 1
mysqld process hanging, pid 6870 - killed
050214 07:56:05 mysqld restarted
/usr/sbin/mysqld: ready for connections.
Version: '4.0.23' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-4.0.23-r1

Number of processes running now: 1
mysqld process hanging, pid 6961 - killed
mysqld restarted
/usr/sbin/mysqld: ready for connections.
Version: '4.0.23' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-4.0.23-r1
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=131072
read_buffer_size=131072
max_used_connections=3
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 19327 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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...
Cannot determine thread, fp=0x411d7628, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80fc731
0x4015a685
0x8107b31
0x40155041
0x40388b7a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Reso
lved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.



when mysql is crashed there's no other solution (for me) than restarting the linode :

localhost log # /etc/init.d/mysql start
* WARNING: "mysql" has already been started.
localhost log # /etc/init.d/mysql stop
* Stopping mysqld...
[ ok ]op-daemon: warning: failed to kill 7460: No such process



I tried reducing the mem variables, right now i use the my.cnf provided by caker for low mem linodes (linode 64), doesn't seem to make a difference

i have had this problem for months, i stoped using a cron, but now i need it, i searched everywhere and can't find a solution

Any ideas ?


thanks

Alex

[caker]

Have you tried setting this?
Code: set-variable    = thread_cache_size=40

Also, what kernel are you running? Does 2.4/2.6 make a difference?

-Chris

[Alexis2]

I'm running, Latest 2.4 Series (2.4.29-linode39-1um)

trying set-variable = thread_cache_size=40 now

[Alexis2]

hasn't hanged once in 2days and 16 hours, looks good using :
Code: set-variable    = thread_cache_size=40

i'll keep you posted in case it crashes again

Alex

[Ciaran]

Alexis2 wrote: when mysql is crashed there's no other solution (for me) than restarting the linode :

localhost log # /etc/init.d/mysql start
* WARNING: "mysql" has already been started.
localhost log # /etc/init.d/mysql stop
* Stopping mysqld...
[ ok ]op-daemon: warning: failed to kill 7460: No such process

For future reference, you can manually reset a Gentoo initscript to "stopped" status by using "zap" - eg, "/etc/init.d/mysql zap". That'll reset the initscript to "stopped" status manually but it doesn't actually do anything else, so you should only use this if you're certain that the process isn't running.