[ZBX-9917] wrong logging for zbx_open_eventlog() Created: 2015 Sep 29  Updated: 2017 May 30  Resolved: 2015 Oct 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 2.2.11rc1, 2.4.7rc1, 3.0.0alpha2
Fix Version/s: 2.2.11rc1, 2.4.7rc1, 3.0.0alpha3

Type: Incident report Priority: Blocker
Reporter: Oleksii Zagorskyi Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: eventlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Regression after r55104 in ZBX-9716

In agent log file with DebugLevel=4 I can see:

   128:20150929:130059.442 In process_eventlog() source:'Alarm' lastlogsize:0
   128:20150929:130059.442 In zbx_open_eventlog()
   128:20150929:130059.442 End of zbx_open_eventlog():FAIL FirstID:1 LastID:11 numIDs:11
   128:20150929:130059.442 End of zbx_open_eventlog():SUCCEED
   128:20150929:130059.442 In zbx_get_eventlog_message() lastlogsize:1
   128:20150929:130059.442 End of zbx_get_eventlog_message():SUCCEED
   128:20150929:130059.442 End of process_eventlog():SUCCEED

It's just about wrong logging (from wrong point).
wiper is aware already about such regression and confirmed it.

I believe we should not issue 2.4.7 release with such a regression, that's why this issue is blocker.



 Comments   
Comment by Oleksii Zagorskyi [ 2015 Sep 29 ]

wiper, take a look here.

Comment by Andris Zeila [ 2015 Sep 29 ]

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

Comment by dimir [ 2015 Sep 29 ]

(1) [G] dwNumRecords may be uninitialized in the print in case of failure.

Perhaps in case of failure it would be enough to just print result string.

wiper RESOLVED in r55836

<dimir> CLOSED

Comment by Andris Zeila [ 2015 Sep 30 ]

Released in:

  • pre-2.2.11rc1 r55854
  • pre-2.4.7rc1 r55855
  • pre-3.0.0alpha3 r55856
Generated at Fri Mar 29 13:56:21 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.