[ZBX-10064] Zabbix server does not sync the history caches on shutdown Created: 2015 Nov 10  Updated: 2017 May 30  Resolved: 2015 Dec 21

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 2.0.15, 2.2.10, 2.4.6, 3.0.0alpha3
Fix Version/s: 2.0.17rc1, 2.2.12rc1, 2.4.8rc1, 3.0.0alpha5

Type: Incident report Priority: Blocker
Reporter: MATSUDA Daiki Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: cache, lock, synchronization
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File zabbix-2.0.15-1_parent_process_force_execute_sync.patch     File zabbix-2.2.10-1_parent_process_force_execute_sync.patch    

 Description   

Zabbix server does not sync the history caches concering items with trigger(s) on shutdown.

Situation is following
1. DB Syncer process starts to sync
1.1 It locks triggers on DCconfig_lock_triggers_by_itemids()
2. Parent process receives the SIGTERM and sends SIGTERM to all children
3. DB Syncer terminates without releasing trigger locks

4. Parent process start full-sync
4.1 find the trigger locks and unlist its item
4.2 terminates without sync

So, I attached the fixed patch to escape to find locks on Parent process.
There is no problem because Parent Process syncs only on shutdown.

 Comments   
Comment by MATSUDA Daiki [ 2015 Nov 13 ]

This problem is occured by the influence of ZBX-7484.

Comment by MATSUDA Daiki [ 2015 Nov 26 ]

So, SIG_PARENT_PROCESS macro is not cool because it calles getpid() everytime. Parent process is forever Parent Process and Childrend too.

So, I added the patch for 2.0.15 and please check it.

Comment by Viktors Tjarve [ 2015 Dec 15 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-10064 r57188.

Comment by Andris Zeila [ 2015 Dec 21 ]

Successfully tested.

Comment by Viktors Tjarve [ 2015 Dec 21 ]

Released in:

  • pre-2.0.17rc1 r57294
  • pre-2.2.12rc1 r57295
  • pre-2.4.8rc1 r57296
  • pre-3.0.0alpha5 r57299
Generated at Wed Apr 24 18:43:44 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.