[#ZBX-12390] Illegal trigger detection.

[ZBX-12390] Illegal trigger detection. Created: 2017 Jul 18 Updated: 2024 Apr 10 Resolved: 2018 May 13
Status:	Closed
Project:	ZABBIX BUGS AND ISSUES
Component/s:	Server (S)
Affects Version/s:	None
Fix Version/s:	4.0.0alpha7, 4.0 (plan)

Type:

Problem report

Priority:

Major

Reporter:

Kazuo Ito

Assignee:

Andris Zeila

Resolution:

Fixed

Votes:

Labels:

server, timestamp

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Zabbix2.2.15

Attachments:

ZBX-12390-reproduce.zip

reproduce_agent_resets_ns.zip

reproduce_history.png

reproduce_screenshot.png

reproduce_triggers.png

Issue Links:

Duplicate
is duplicated by	~~ZBX-12968~~	Server - Trapper item with regexp tri...	Closed
is duplicated by	~~ZBX-13616~~	As Trapper processes adjust monitorin...	Closed
Sub-task

Team:

Team A

Sprint:

Sprint 13, Sprint 14, Sprint 15, Sprint 16, Sprint 17, Sprint 18, Sprint 21, Sprint 22, Sprint 23, Sprint 24, Sprint 25, Sprint 26, Sprint 27, Sprint 28, Sprint 29, Sprint 30, Sprint 31, Sprint 32, Sprint 33

Story Points:

Description

The following item and triggers were registered.

name:test
key:log[/var/log/test.log]

name:test1 
Expression:{host:log[/var/log/test.log].regexp(test1)}=1

name:test2 
Expression:{host:log[/var/log/test.log].regexp(test2)}=1

name:test3 
Expression:{host:log[/var/log/test.log].regexp(test3)}=1

The following data was recorded in history_log table.

+-----------+--------+------------+--------------- ... +-----------+
| id        | itemid | clock      | value          ... | ns        |
+-----------+--------+------------+--------------- ... +-----------+
| 106038844 |  10101 | 1499264703 |test1           ... | 171101912 | <- here!
| 106038848 |  10101 | 1499264703 |test2           ... | 170707732 |
| 106038853 |  10101 | 1499264703 |test3           ... | 170752400 |

Time synchronization seems to have occurred.

An event of test 1 occurred three times.

Time                Description Status  Severity
2017/07/05 23:25:03 test1       PROBLEM ...
2017/07/05 23:25:03 test1       PROBLEM ...
2017/07/05 23:25:03 test1       PROBLEM ...

Comments

Comment by Vladislavs Sokurenko [ 2017 Jul 18 ]

Time synchronization seems to have occurred.

yes, this is correct, because they all have same clock as you see.

Could you please be so kind and double check if you can reproduce the issue or if 3 triggers simply had same name ?

If issue still persists, please attach screenshots of events, triggers, latest data and your configuration and export host.
Also can do:

select * from triggers t,events e where description in ('test1', 'test2', 'test3') and t.triggerid=e.objectid;

Also please make sure cache is reloaded between setup and test.

Comment by Vladislavs Sokurenko [ 2017 Jul 18 ]

cannot reproduce

Comment by Vladislavs Sokurenko [ 2017 Jul 19 ]

attached zip with info to reproduce, import template, host and launch start_test.sh

select * from history_log;
+----+--------+------------+-----------+--------+----------+--------------+------------+-----------+
| id | itemid | clock      | timestamp | source | severity | value        | logeventid | ns        |
+----+--------+------------+-----------+--------+----------+--------------+------------+-----------+
|  1 |  23688 | 1500446219 |         0 |        |        0 | test3 line 3 |          0 | 755650707 |
|  2 |  23688 | 1500446219 |         0 |        |        0 | test1 line 1 |          0 | 655542754 |
|  3 |  23688 | 1500446219 |         0 |        |        0 | test2 line 2 |          0 | 655597313 |
+----+--------+------------+-----------+--------+----------+--------------+------------+-----------+
3 rows in set (0.00 sec)

{
	"request":"agent data",
	"data":[
		{
			"host":"test server",
			"key":"log[\/tmp\/test.log]",
			"value":"test3 line 3",
			"lastlogsize":39,
			"clock":1500445751,
			"ns":810557214},
		{
			"host":"test server",
			"key":"log[\/tmp\/test.log]",
			"value":"test1 line 1",
			"lastlogsize":13,
			"clock":1500445751,
			"ns":710449261},
		{
			"host":"test server",
			"key":"log[\/tmp\/test.log]",
			"value":"test2 line 2",
			"lastlogsize":26,
			"clock":1500445751,
			"ns":710503820}],
	"clock":1500445756,
	"ns":713964349}

Comment by Vladislavs Sokurenko [ 2017 Jul 19 ]

similar feature request ZBXNEXT-3298

Comment by Andris Zeila [ 2017 Aug 08 ]

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

However time required for testing is most likely underestimated.

Generated at Thu Apr 25 01:27:42 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.

[ZBX-12390] Illegal trigger detection. Created: 2017 Jul 18 Updated: 2024 Apr 10 Resolved: 2018 May 13