Notifications and proc.num no longer working in 1.6

[asobj]

From the zabbix server log:

5247:20080921:185534 Query failed: [insert into alerts (alertid, actionid,triggerid,userid,clock,mediatypeid,sendto ,subject,message,status,retries) values (1062876,4,14760,3,1222037734,1,'email-removed','ALERT: Process: cdp agent is down on Aaron','Current Value: 0

System Load: 0.41
',0,0)] Unknown column 'triggerid' in 'field list' [1054]

This alert is generated from proc.num which is still working in the 1.4.6 agents. I upgraded two server agents to 1.6 and neither of them will use any proc.num triggers. From the agentd log

29998:20080921:190127 Processing request.
29998:20080921:190127 In check_security()
29998:20080921:190127 Requested [proc.num[buagent]]
29998:20080921:190127 Sending back [0]

buagent is clearly running on the server.

I'm also seeing various mysql query errors in the logs

5259:20080921:190740 Query::select curr.nodeid,curr.tablename,curr.recordid from node_cksum prev, node_cksum curr where curr.tablename=prev.tablename and curr.recordid=prev.recordid and curr.fieldname=prev.fieldname and curr.nodeid=prev.nodeid and curr.cksum<>prev.cksum and curr.cksumtype=1 and prev.cksumtype=0
5259:20080921:190740 Query failed:Unknown column 'curr.fieldname' in 'where clause' [1054]
5259:20080921:190740 Query::select curr.nodeid,curr.tablename,curr.recordid from node_cksum curr left join node_cksum prev on curr.tablename=prev.tablename and curr.recordid=prev.recordid and curr.fieldname=prev.fieldname and curr.nodeid=prev.nodeid and curr.cksumtype<>prev.cksumtype where prev.cksumid is null and curr.cksumtype=1
5259:20080921:190740 Query failed:Unknown column 'prev.cksumid' in 'where clause' [1054]
5259:20080921:190740 Query::select curr.nodeid,curr.tablename,curr.recordid from node_cksum curr left join node_cksum prev on curr.tablename=prev.tablename and curr.recordid=prev.recordid and curr.fieldname=prev.fieldname and curr.nodeid=prev.nodeid and curr.cksumtype<>prev.cksumtype where prev.cksumid is null and curr.cksumtype=0
5259:20080921:190740 Query failed:Unknown column 'prev.cksumid' in 'where clause' [1054]

Any ideas?

[Alexei]

Please, make sure that database was correctly upgraded to 1.6 structure!

[asobj]

I did, twice. There were no errors from the upgrade patch.

[jeenam]

dur

Experiencing the same problem here. Upgraded from v1.4.4 and using the mysql patch included with 1.6.0.

The Mysql patch applied without any errors so there must be something wrong with the patch.

[Alexei]

I did, twice. There were no errors from the upgrade patch.

Then please run ZABBIX server v1.6, not the old 1.4.x.

[asobj]

Yea, I did that.

Tried the upgrade, wouldn't work so I restored everything from our daily 1.4 backup. Waited a few days and tried the upgrade again, same thing so I restored a backup again. Still running 1.4 now.

[Little_rU]

Then please run ZABBIX server v1.6, not the old 1.4.x.

In patch.sql script columns cksumid and fieldname are missing when creating table node_cksum. They need to be added after database upgrade:

alter table node_cksum add cksumid bigint unsigned DEFAULT '0' NOT NULL;
alter table node_cksum add fieldname varchar(64) DEFAULT '' NOT NULL;

Also in patch.sql script column triggerid in table alerts is deleted but never created again. After restoring this column alerts starts to work:

alter table alerts add triggerid bigint unsigned DEFAULT '0' NOT NULL;

[Alexei]

In patch.sql script columns cksumid and fieldname are missing when creating table node_cksum. They need to be added after database upgrade:

alter table node_cksum add cksumid bigint unsigned DEFAULT '0' NOT NULL;
alter table node_cksum add fieldname varchar(64) DEFAULT '' NOT NULL;

Also in patch.sql script column triggerid in table alerts is deleted but never created again. After restoring this column alerts starts to work:

alter table alerts add triggerid bigint unsigned DEFAULT '0' NOT NULL;

This is ABSOLUTELY wrong! Please read my previous post.

[Little_rU]

This is ABSOLUTELY wrong! Please read my previous post.

Sorry, my bad. Forgot to su before doing "make install". Now everithing is working fine.

Sorry again.

[rmoore]

I had the same problem, was upgrading from 1.4.4 to 1.6 and everything related to the upgrade went through without a problem. A custom item I had to monitor a process on a few servers was failing that was previously working just fine. I found this workaround in an old thread:

http://www.zabbix.com/forum/showthread.php?t=8998

Previously my key was just 'proc.num[amavisd]', however I changed the key to check the cmdline instead of the name, so it read 'proc.num[,,,amavisd]' and it started working just fine. Not sure why it would change between 1.4 and 1.6, nothing regarding the amavisd process changed at all, but it works for now.