[ZBX-11674] Duplicated clock and ns value for vmware eventlog items (Zabbix 2.2) Created: 2017 Jan 05 Updated: 2017 May 30 Resolved: 2017 Jan 11 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.2.16 |
| Fix Version/s: | 2.2.17rc1 |
| Type: | Incident report | Priority: | Major |
| Reporter: | Kim Jongkwon | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | logmonitoring, vmware | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Seems like this issue is similar to vmware.eventlog has duplicated clock and nanoseconds value. +------------+-----------+------------+--------------------------------------------- | clock | ns | timestamp | value +------------+-----------+------------+--------------------------------------------- | 1483175683 | 457847990 | 1483175131 | Device xxxxxx performance has deteriorated. | 1483175683 | 457847990 | 1483175132 | Device xxxxxx performance has improved. I/O | 1483175683 | 457847990 | 1483175133 | Device xxxxxx performance has improved. I/O | 1483175683 | 457847990 | 1483175176 | Lost access to volume xxxxxx (vmstorage) due | 1483175683 | 457847990 | 1483175176 | Successfully restored access to volume xxxxxx | 1483206283 | 521161429 | 1483206353 | Device xxxxxx performance has deteriorated. | 1483206283 | 521161429 | 1483206356 | Device xxxxxx performance has improved. I/O | 1483206583 | 647379269 | 1483206475 | Device xxxxxx performance has improved. I/O | 1483228483 | 132293831 | 1483228575 | Device xxxxxx performance has deteriorated. | 1483228483 | 132293831 | 1483228582 | Device xxxxxx performance has deteriorated. | 1483228483 | 132293831 | 1483228598 | Device xxxxxx performance has improved. I/O | 1483228783 | 283334836 | 1483228617 | Device xxxxxx performance has improved. I/O | 1483250684 | 17462313 | 1483175133 | Device xxxxxx performance has improved. I/O | 1483250684 | 17462313 | 1483175176 | Lost access to volume xxxxxx (vmstorage) due | 1483250684 | 17462313 | 1483175176 | Successfully restored access to volume xxxxxx | 1483250684 | 17462313 | 1483206353 | Device xxxxxx performance has deteriorated. | 1483250684 | 17462313 | 1483206356 | Device xxxxxx performance has improved. I/O | 1483250684 | 17462313 | 1483206475 | Device xxxxxx performance has improved. I/O | 1483250684 | 17462313 | 1483228575 | Device xxxxxx performance has deteriorated. | 1483250684 | 17462313 | 1483228582 | Device xxxxxx performance has deteriorated. | 1483250684 | 17462313 | 1483228598 | Device xxxxxx performance has improved. I/O | 1483250684 | 17462313 | 1483228617 | Device xxxxxx performance has improved. I/O | 1483354183 | 792116682 | 1483354259 | Lost access to volume xxxxxx (vmstorage) due | 1483354183 | 792116682 | 1483354259 | Successfully restored access to volume xxxxxx | 1483354183 | 792116682 | 1483354260 | Device xxxxxx performance has deteriorated. | 1483354183 | 792116682 | 1483354260 | Lost access to volume xxxxxx (vmstorage) due | 1483354183 | 792116682 | 1483354260 | Device xxxxxx performance has deteriorated. FYI. There is a possibly of a incorrect {item.value} could occur through duplicated nanoseconds. |
| Comments |
| Comment by dimir [ 2017 Jan 05 ] |
|
Yes, this is fixed for 2.4 and later. If you need the patch for 2.2 I could make it. |
| Comment by dimir [ 2017 Jan 06 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-11674 |
| Comment by Vladislavs Sokurenko [ 2017 Jan 09 ] |
|
Successfully tested. |
| Comment by dimir [ 2017 Jan 11 ] |
|
Fixed in pre-2.2.17rc1 (r65014). |