Hello, Sascha

Restarting Zabbix server service should fix this problem. 

Please don't delete any records from events, they can have dependencies.

Is the situation possible that the second instance of the Zabbix server was launched?

Can you attach a Zabbix_server log file? Do you use one instance of database or you configured replication? Are there any third-party services or scripts working with the Zabbix database?

Regards,

Elina

Hi Elina, I restarted many times zabbix-server, but the error remained.

For now I solved by putting the host with item 36183 disabled

Can you

delete from event_recovery where eventid=4797763;

Than enable item.
And what about other questions?

Sorry, just found log attached, give me some time to check it

No problem  thank's for support ! I will wait for your mex

Looks like you have some items collected by userparamers, for example bind.incounter. The script sometimes return an error and item became not supported, because Zabbix gets string instead of numeric. It will be a good idea to change userparameter to interpret errors in a specific number or forward script errors to devnull.

Olso, you can delete records from event_recovery

delete from event_recovery where eventid in ('4797699','4797705','4797754','4797763','4797768');

But the reason for the appearance of duplicates is unclear. So:

Is the situation possible that the second instance of the Zabbix server was launched? Do you use one instance of database or you configured replication? Are there any third-party services or scripts working with the Zabbix database?

I have the same issue in 3.4.11 after upgrading from 3.4.9.

I would like to add to Elinas comment one approach how to configure UserParameter so it will always retrieve some numeric value. This would be the way how to count zabbix processes:

UserParameter=custom.key,pslist=$(ps -caux|grep [z]abbix) && echo ${pslist:-0}

The classic variable is $pslist, but if the value is empty then it will get substituted with 0.

F10, please tell more about you configuration:
Do you have some High Availability setup for DB or back-end?
What is Zabbix server version?

Regards,

I think the Problem was the last update. We have a distributed environment and 2 proxies were not stopped during the server upgrade. We started with a fresh database and imported all setting. After that everything is working fine and performance values of the database are much better. We do not have a HA setup for our DB in the moment.

Hi, I have the same problem. 

And get tons of errors in my server log:

59293:20180816:102804.451 [Z3005] query failed: [1062] Duplicate entry '17257' for key 'PRIMARY' [insert into event_recovery (eventid,r_eventid,correlationid,c_eventid,userid) values (17257,102313,null,null,null);
]
59298:20180816:102804.857 [Z3005] query failed: [1062] Duplicate entry '17274' for key 'PRIMARY' [insert into event_recovery (eventid,r_eventid,correlationid,c_eventid,userid) values (17274,102314,null,null,null);
]
59291:20180816:102804.919 [Z3005] query failed: [1062] Duplicate entry '17270' for key 'PRIMARY' [insert into event_recovery (eventid,r_eventid,correlationid,c_eventid,userid) values (17270,102315,null,null,null);
]
59310:20180816:102805.455 [Z3005] query failed: [1062] Duplicate entry '17282' for key 'PRIMARY' [insert into event_recovery (eventid,r_eventid,correlationid,c_eventid,userid) values (17282,102316,null,null,null);
]
59299:20180816:102805.857 [Z3005] query failed: [1062] Duplicate entry '17263' for key 'PRIMARY' [insert into event_recovery (eventid,r_eventid,correlationid,c_eventid,userid) values (17263,102317,null,null,null);
]

Is there any fix so far? 

Regrads, Chris 

aigars.kadikis

UserParameter=custom.key,pslist=ps -caux|grep -c [z]abbix

ZBX-10876 looks related. It's mentioned there that events table partitioning is not recommended. sascha.papini, do you have db partitioning set up and enabled also for events table?

Hi,

I have had the same issue, and I think it is due to the fact that I restored a backup (not full data, just configuration using zabbix-mysql-dump), and that I did many changes (removed hosts...).

So the symptom is:

• I get the same kind of errors in the log as described in this thread (but multiple records are inserted into event_recovery for the same original event)
• Zabbix can't recover some problems and will create a new one each time the issue happens again.

I am thinking that the restore process has restored values inside the event_recovery and problem tables that don't have any matching record in table events.

So I am wondering if it is safe to delete records from event_recovery and problem tables when they have no matching record in table events?

Is there anything else to do?

Here is a request I have tried to clean up the tables: 

delete from event_recovery  where eventid not in (select eventid from events) or r_eventid not in (select eventid from events);

delete from problem where eventid not in (select eventid from events) or r_eventid not in (select eventid from events);

Thanks in advance,

Eric.

Hi,

@ericn I did exactly the same. Moved to a new server and then the problems starts to begin...

I deleted all entries in the following tables: Problems, Events & Event_recovery. It was not important for me
to see all old problems. 

Now it is solved  Everything is working and I can't see any error so far.

Chris

Thank you Chris for your comment.

So yes, I think the zabbix-mysql-dump script could be improved to avoid these issues when restoring.

After removing the orpheans from the event_recovery and problem tables, I still had left aside events (in table events) showing as problems in the history... I deleted them as well.

Now it's all clean, and Zabbix seems to work fine: It just triggered the same alert that had caused problems and when the cause of the trigger was solved, the problem went into resolved state, as expected.

Eric.

Thanks to community effort!

Armed with this knowledge I will close the issue.