Server Crashes After Client Login

[manfro]

Hello,
I've installed zabbix-server (1.1.2) on a Debian (Plesk VIrtual Server) distribution.
I tried first using mysql 4.0.x, then 4.1.x without net-snmp.
Also zabbix was configured and recompiled withoud net-snmp.
I always get the same error.
Sometine when a win32 agent connects, server looses db connection (socket connection on mysqld.socket) and dies.
I haven't found nothing about that around in forums.
Log file ends like this:

020257:20061025:175325 Nextcheck:1161791624 Time:1161791605
020257:20061025:175325 Sleeping for 5 seconds
020267:20061025:175326 After accept()
020267:20061025:175326 In process_trapper_child
020267:20061025:175326 Before read(65000)
020267:20061025:175326 Read 34 bytes
020267:20061025:175326 After read() 3 [34]
020267:20061025:175326 Got data:ZBX_GET_ACTIVE_CHECKS
iolab-zagor

020267:20061025:175326 Trapper got [ZBX_GET_ACTIVE_CHECKS
iolab-zagor]
020267:20061025:175326 In autoregister(iolab-zagor)
020267:20061025:175326 Executing query:select hostid from hosts where host='iolab-zagor'
020267:20061025:175326 Query::select hostid from hosts where host='iolab-zagor'
020267:20061025:175326 Query failed:Lost connection to MySQL server during query [2013]
020243:20061025:175326 One server process died. Shutting down...
020243:20061025:175326 0. Killing PID=[20245]
020243:20061025:175326 1. Killing PID=[20247]
020243:20061025:175326 2. Killing PID=[20249]
020243:20061025:175326 3. Killing PID=[20251]
020243:20061025:175326 4. Killing PID=[20253]
020243:20061025:175326 5. Killing PID=[20255]
020243:20061025:175326 6. Killing PID=[20257]
020243:20061025:175326 7. Killing PID=[20259]
020243:20061025:175326 8. Killing PID=[20263]
020243:20061025:175326 9. Killing PID=[20264]
020243:20061025:175326 10. Killing PID=[20265]
020243:20061025:175326 11. Killing PID=[20266]
020243:20061025:175326 12. Killing PID=[20267]
020243:20061025:175326 13. Killing PID=[20268]
020243:20061025:175326 14. Killing PID=[20269]
020245:20061025:175326 Server [1]. Got QUIT or INT or TERM or PIPE signal. Exiting...

does anyone have any idea ?

Thanks

[Alexei]

Perhaps your database is corrupted?

[manfro]

I installed mysql 4.0 and then 4.1.
I ran all utilities to recreate tables and to fix corrupted tables, but corrupted tables weren't found.
Always the same problem. Very strange.

[manfro]

It seems to be a problem due to connection to mysql, using mysq.sock.
I disabled DB_SOCKET connection, enabling standard TCP on port 3306 and it doesn't crash any longer.

[Alexei]

Hmm, inetresting. Perhaps some other process deleted the mysql.sock (is it in /tmp?) or changed its permissons?

[manfro]

What should be the right permission on mysql.socket ? I looked around on the web and I found that some mysql distribution start script set "/var/run/mysql" permission to 770. I haven't time to check if it is the same that happens to me.
But it is very strange that it crashes only when that query is executed(select hostid from hosts where host=...), isn't it ?

anyway thank you for your answers and for your great product.