Zabbix suddenly stops to send emails. Restart helps

[gospodin.horoshiy]

Hello.
I have two problems with my zabbix 1.6.5

1st) All of the sudden, my triggers stop to generate actions( like sending mail etc) despite that all conditions are met. Restarting server fixs this problem.

I think this is not related to my email server, because in zabbixs action audit I can see no attempts to send this alert and Action tab is empty on my Dashboard (see pic).

And these triggers send alerts all the time when zabbix works propely, I'm 100% sure that all conditions are met.


2nd) When I create new Win32 hosts to monitor and then attach any template to it. My server dies. In log I see:
Child process died. Exiting....
After 2 or 3 attemptd to restart my server it actually starts and everything seems to be ok again.

Any thoughts?

Thanks.

[richlv]

which database ?
have you tried reproducing either of the problems with debuglevel 4 and checking out the logfiles ?

[gospodin.horoshiy]

Mysql5

1st problem - no
2nd - it says something about that a table is locked and after that server dies with message that Child process died. Exiting....


I'll try to catch both problems with full debug log...

[richlv]

mysql 5.which ?

[gospodin.horoshiy]

Server version: 5.0.51a-3ubuntu5.4 (Ubuntu)

[gospodin.horoshiy]

Those two problems started to bug me not so long time ago, and i've been running zabbix almost for a year flawlessly before that

[richlv]

well, my best guess right now is to check system load on zabbix server. maybe database is overloaded.

[gospodin.horoshiy]

Ok, I'll check that

[gospodin.horoshiy]

Well, the server itself is almost idle, but mysql... here is mysqltuner.pl output:

Any comments? I'm not good at Mysql and RDBMS optimization and would appreciate any thoughts here. Thanks

-------- Storage Engine Statistics -------------------------------------------
[--] Status: +Archive -BDB -Federated +InnoDB -ISAM -NDBCluster
[--] Data in InnoDB tables: 598M (Tables: 124)
[OK] Total fragmented tables: 0

-------- Performance Metrics -------------------------------------------------
[--] Up for: 2d 20h 27m 13s (6M q [26.716 qps], 37K conn, TX: 452M, RX: 1B)
[--] Reads / Writes: 78% / 22%
[--] Total buffers: 298.0M global + 2.6M per thread (250 max threads)
[OK] Maximum possible memory usage: 954.2M (48% of installed RAM)
[OK] Slow queries: 0% (1/6M)
[OK] Highest usage of available connections: 12% (31/250)
[OK] Key buffer size / total MyISAM indexes: 256.0M/153.9M
[!!] Key buffer hit rate: 70.6% (2M cached / 786K reads)
[!!] Query cache efficiency: 9.2% (393K cached / 4M selects)
[!!] Query cache prunes per day: 17723
[OK] Sorts requiring temporary tables: 5% (20K temp sorts / 346K sorts)
[!!] Joins performed without indexes: 1131
[!!] Temporary tables created on disk: 48% (1M on disk / 2M total)
[OK] Thread cache hit rate: 99% (31 created / 37K connections)
[OK] Table cache hit rate: 97% (288 open / 294 opened)
[OK] Open file limit used: 3% (36/1K)
[OK] Table locks acquired immediately: 99% (6M immediate / 6M locks)
[!!] InnoDB data size / buffer pool: 598.8M/8.0M

-------- Recommendations -----------------------------------------------------
General recommendations:
Enable the slow query log to troubleshoot bad queries
Adjust your join queries to always utilize indexes
When making adjustments, make tmp_table_size/max_heap_table_size equal
Reduce your SELECT DISTINCT queries without LIMIT clauses
Variables to adjust:
query_cache_limit (> 1M, or use smaller result sets)
query_cache_size (> 16M)
join_buffer_size (> 128.0K, or always use indexes with joins)
tmp_table_size (> 32M)
max_heap_table_size (> 16M)
innodb_buffer_pool_size (>= 598M)


UPD:
Ok. I made this changes in my.cnf:
innodb_buffer_pool_size =650M
max_heap_table_size =64M
tmp_table_size = 64M
query_cache_limit = 2M

Will see if this helps...

[gospodin.horoshiy]

I'm pretty sure that it was bad mysql configuration that caused all these problems. Now once I changed them, (innodb_buffer_pool_size =650M, first of all) it looks real sweet and no crashes. Cheers