Zabbix and MySQL, Crashed tables

[michaeltje]

Hi There,

My Zabbix box sometimes stops storing the data in the MySQL database, when i check the zabbix_server.log it shows me the follow:

  6752:20080214:095201 Query::select min(value) from history_uint where clock>1202978881 and itemid=19680
  6752:20080214:095201 Query failed:Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6752:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,21450,24264587)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6752:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,20190,1)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6752:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,19860,2)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6752:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,19410,1)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6753:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,20341,1)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6753:20080214:095201 Query::select max(value) from history_uint where clock>1202978821 and itemid=20341
  6753:20080214:095201 Query failed:Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6753:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,19561,481473)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6753:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,20521,2)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145]
  6753:20080214:095201 Query failed: [insert into history_uint (clock,itemid,value) values (1202979121,20711,3)] Table './zabbix/history_uint' is marked as crashed and should be repaired [145] 

After that i repair the table and the next day it occurs again, is this a bug in zabbix?

Any help is apreciated since this is quite a serious problem, thanks!

[Alexei]

No, it is not bug in ZABBIX!

[michaeltje]

Any idea what this could cause? Its quite annoying

[Alexei]

Just a guess, power offs without a proper shutdown?

[michaeltje]

The machine is running 24/7 and has not be switched off for like 4/5 months, so thats not the problem

[bbrendon]

Disk full?

[michaeltje]

it has used 1 of the 5 GB, i see it happens every morning, it happened today again

[ProTON]

We are experiencing the same problem too. We've consulted with our MySQL support and they told that this usually happens when using delayed queries. Does Zabbix server/agent uses any of this type of queries?

[Alexei]

We are experiencing the same problem too. We've consulted with our MySQL support and they told that this usually happens when using delayed queries. Does Zabbix server/agent uses any of this type of queries?

Zabbix does not use delayed queries at all.

[ProTON]

So why does it happen? Usually during reboots, normal reboots with shutdown -r now. Also I saw this couple of times on normal working system without any reboots. MySQL tables just crashes randomly.

[Alexei]

So why does it happen? Usually during reboots, normal reboots with shutdown -r now. Also I saw this couple of times on normal working system without any reboots. MySQL tables just crashes randomly.

I have no idea. Obviously this question has to be addressed to MySQL team.

[stalker]

try to test your hardware! Check your server memory with memtest86.

If hardware is ok, recheck mysqld options in mysql.cnf and tune it more accurately.

[ProTON]

Memory, CPU and PSU is changed. Also other MySQL DBs on that server works fine without a problem.

[bbrendon]

I'll have to agree with Alexei, this isn't Zabbix. Did you fsck? Do you have a mysql wiz around to look at it?

[ProTON]

I have tried almost everything for the last half a year. Hardware change, fsck, memtest86 and other tests, MySQL version change. Now I tried to swich to InnoDB storage engine instead of MyISAM. If it still crashes then official MySQL support says that this is not a problem with MySQL.