I have been working on building out a newer zabbix instance for migration. I took a snapshot of the database and created a new instance from that snapshot.
After getting everything in order, I am presented with the dreaded "Zabbix server is not running : The information displayed may not be current." message. Looking at the log files, I see a-lot of this..
<gibberish>
1595:20130813:162101.071 In DBget_trigger_update_sql() triggerid:13141 value:0(1) new_value:2
1595:20130813:162101.071 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.071 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13142]
1595:20130813:162101.160 In DBget_trigger_update_sql() triggerid:13142 value:0(1) new_value:2
1595:20130813:162101.160 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.160 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13143]
1595:20130813:162101.250 In DBget_trigger_update_sql() triggerid:13143 value:0(1) new_value:2
1595:20130813:162101.250 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.250 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13144]
1595:20130813:162101.340 In DBget_trigger_update_sql() triggerid:13144 value:0(1) new_value:2
1595:20130813:162101.340 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.340 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13145]
1595:20130813:162101.431 In DBget_trigger_update_sql() triggerid:13145 value:0(1) new_value:2
1595:20130813:162101.431 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.431 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13146]
</giberish>
After a few minutes the logs stop filling up with that stuff and start displaying fairly normal information. The sever status changes to normal and everything seems to move along.
Does anyone have any ideas as to what this is?
Thanks,
J
After getting everything in order, I am presented with the dreaded "Zabbix server is not running : The information displayed may not be current." message. Looking at the log files, I see a-lot of this..
<gibberish>
1595:20130813:162101.071 In DBget_trigger_update_sql() triggerid:13141 value:0(1) new_value:2
1595:20130813:162101.071 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.071 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13142]
1595:20130813:162101.160 In DBget_trigger_update_sql() triggerid:13142 value:0(1) new_value:2
1595:20130813:162101.160 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.160 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13143]
1595:20130813:162101.250 In DBget_trigger_update_sql() triggerid:13143 value:0(1) new_value:2
1595:20130813:162101.250 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.250 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13144]
1595:20130813:162101.340 In DBget_trigger_update_sql() triggerid:13144 value:0(1) new_value:2
1595:20130813:162101.340 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.340 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13145]
1595:20130813:162101.431 In DBget_trigger_update_sql() triggerid:13145 value:0(1) new_value:2
1595:20130813:162101.431 End of DBget_trigger_update_sql():FAIL
1595:20130813:162101.431 query [txnlev:1] [select distinct i.itemid,i.type,i.lastclock,i.delay,i.delay_flex,i .interfaceid from items i,functions f,triggers t where i.itemid=f.itemid and f.triggerid=t.triggerid and i.type not in (2,17) and t.triggerid=13146]
</giberish>
After a few minutes the logs stop filling up with that stuff and start displaying fairly normal information. The sever status changes to normal and everything seems to move along.
Does anyone have any ideas as to what this is?
Thanks,
J