[ZBX-10342] {ITEM.VALUE1} was referring to the old data Created: 2016 Feb 03 Updated: 2017 May 30 Resolved: 2016 Mar 03 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 2.2.10 |
Fix Version/s: | 2.2.12rc1, 2.4.8rc1, 3.0.2rc1, 3.2.0alpha1 |
Type: | Incident report | Priority: | Major |
Reporter: | Kazuo Ito | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | alerts, logmonitoring, macro, timestamp | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | analysis.zip | ||||
Issue Links: |
|
Description |
?Default message Date: {EVENT.DATE} {EVENT.TIME} Event: {TRIGGER.NAME} Status: {TRIGGER.STATUS} Severity: {TRIGGER.SEVERITY} Item values: {ITEM.NAME1} ({HOST.NAME1}:{ITEM.KEY1}): {ITEM.VALUE1} Original event ID: {EVENT.ID} ?Get the log Jan 4 01:30:21 host01 message ccc Jan 4 01:30:21 host01 message bbb Dec 29 20:24:24 host01 message aaa Dec 29 20:24:24 host01 message aaa ?event list "2016/01/04 01:26:09","host01","trigger01","PROBLEM","High","0","No","51" "2016/01/04 01:26:09","host01","trigger01","PROBLEM","High","0","No","51" "2015/12/29 20:24:39","host01","trigger01","PROBLEM","High","5d 5h 1m","No","41" "2015/12/29 20:24:39","host01","trigger01","PROBLEM","High","0","No","41" ?alert message Date: 2016/01/04 01:26:09 Event: trigger01 Status: PROBLEM Severity: High Item values: item01 (host01:log[/var/log/messages,Error,UTF-8]): Dec 29 20:24:24 host01 message aaa Original event ID: xxxxxx The event was detected on January 4. |
Comments |
Comment by richlv [ 2016 Feb 03 ] |
is this a duplicate of now private ZBX-10338 ? |
Comment by Aleksandrs Saveljevs [ 2016 Feb 03 ] |
richlv, ZBX-10338 was deleted. |
Comment by Aleksandrs Saveljevs [ 2016 Feb 03 ] |
Which Zabbix version is being used? |
Comment by Kazuo Ito [ 2016 Feb 03 ] |
Using Zabbix2.2.10. |
Comment by Sandis Neilands (Inactive) [ 2016 Feb 03 ] |
While i'm trying to reproduce the problem, kazuo.ito, could you provide:
|
Comment by Andris Zeila [ 2016 Feb 23 ] |
Fixed value cache not caching value if its timestamp seconds matches the timestamp of the oldest cached value and timestamp nanoseconds is less. Development branch svn://svn.zabbix.com/branches/dev/ZBX-10342 wiper After thinking it over I realized that empty items must be removed, the fix is updated in r58687 |
Comment by Sandis Neilands (Inactive) [ 2016 Feb 29 ] |
(1) next is used uninitialized in vch_item_remove_values(). wiper RESOLVED in r58783 sandis.neilands CLOSED. |
Comment by Sandis Neilands (Inactive) [ 2016 Mar 01 ] |
Tested with zabbix_sender and agent.hostname active agent item and trigger. Example: $ ./zabbix_sender -z 127.0.0.1 -i - -T -r localhost agent.hostname 1456831704 hostname_0 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000043" localhost agent.hostname 1456831703 hostname_1 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000042" localhost agent.hostname 1456831705 hostname_2 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000036" localhost agent.hostname 1456831702 hostname_3 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000035" localhost agent.hostname 1456831706 hostname_4 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000042" localhost agent.hostname 1456831710 hostname_5 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000043" localhost agent.hostname 1456831708 hostname_6 info from server: "processed: 1; failed: 0; total: 1; seconds spent: 0.000042" |
Comment by Andris Zeila [ 2016 Mar 02 ] |
Released in:
|