insert or update on table "auditlog" violates foreign key constraint "c_auditlog_1"

[esawyja]

Hi All,
Recently build a new master server running SLES 11 SP3 and Postgres 9.3, but now I'm getting this every time the Child nodes try to send information
2014-01-17 14:57:09 SAST ERROR: insert or update on table "auditlog" violates foreign key constraint "c_auditlog_1"
2014-01-17 14:57:09 SAST DETAIL: Key (userid)=(26626600000000003) is not present in table "users".
2014-01-17 14:57:09 SAST STATEMENT: insert into auditlog (auditid,userid,clock,action,resourcetype,details, ip,resourceid,resourcename) values (26600000000000001,26626600000000003,1383831403,0, 13,'0','127.0.0.1',26626600000013517,'Active Session {HOSTNAME}'),(26600000000000002,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013518, 'Active Session {HOSTNAME}'),(26600000000000003,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013519, 'Alive'),(26600000000000004,26626600000000003,1383 831403,0,13,'0','127.0.0.1',26626600000013520,'Arc hivelog'),(26600000000000005,26626600000000003,138 3831403,0,13,'0','127.0.0.1',26626600000013521,'AS M free space size less than 20 %'),(26600000000000006,26626600000000003,138383140 3,0,13,'0','127.0.0.1',26626600000013522,'Audit on {HOSTNAME}'),(26600000000000007,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013523, 'Excessive log switching'),(26600000000000008,26626600000000003,1 383831403,0,13,'0','127.0.0.1',26626600000013524,' Hit Ratio on {HOSTNAME}'),(26600000000000009,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013525, 'Locks on {HOSTNAME}'),(26600000000000010,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013526, 'PGA Alarm on {HOSTNAME}'),(26600000000000011,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013527, 'Process Alarm on {HOSTNAME}'),(26600000000000012,26626600000000003, 1383831403,0,13,'0','127.0.0.1',26626600000013528, 'Session Alarm on {HOSTNAME}'),(26600000000000013,26626600000000003, 1383831403,0,13,'0','127.0.0.1',266266


Any ideas please
Thanks

[esawyja]

Anyone, please, this is getting serious

[esawyja]

I chatted on the #zabbix channel and they are saying that the child nodes must be on the same level as the master? The child nodes are on V2.0.6 and the master on V2.2.1. Can someone confirm this please

[chojin]

I chatted on the #zabbix channel and they are saying that the child nodes must be on the same level as the master? The child nodes are on V2.0.6 and the master on V2.2.1. Can someone confirm this please

I can't speak out of experience with this, but it seems obvious to me that all nodes in a multi-node setup have to be of at least the same major version. In this case 2.2.0 or 2.2.1. As your database scheme is upgraded to be compatible with v2.2.x, your 2.0.x node(s) won't understand this newer scheme.

A node communicates directly with the database, hence requires a DB scheme compatible with it's own version. so sharing a database between a node 2.2.x and a 2.0.x or even 1.8.x won't be possible as the DB scheme is not backwards compatible with older versions of zabbix.

[esawyja]

That makes sense, thank you, I will create a test box on V2.0.6 and upgrade and see if the error is still there. I will post my results here