[ZBX-6929] Log size for log[*] based items is not stored in database Created: 2013 Aug 25  Updated: 2017 May 30  Resolved: 2013 Sep 03

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 2.0.7
Fix Version/s: 2.0.9rc1, 2.1.4

Type: Incident report Priority: Major
Reporter: Marc Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: log
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, CentOS-6.4, PostgreSQL 9.1.9, Apache HTTPD-2.2.15, PHP-5.3.3



 Description   

According to the documentation does:
The server [...] keep a trace of the monitored log's size [...] stored in the Zabbix database [...]

If I'm not wrong storing in database would never be happen for log[*] based items due to lack of mtime (code based on 2.0.8):

  1. sed -n '1324,1331p' ./src/libs/zbxdbcache/dbcache.c
    if (-1 == lastlogsize || -1 == mtime)
    continue;

zbx_snprintf_alloc(&sql, &sql_alloc, &sql_offset,
"update items set lastlogsize=" ZBX_FS_UI64 ",mtime=%d where itemid=" ZBX_FS_UI64 ";\n",
lastlogsize,
mtime,
ids[i]);



 Comments   
Comment by Alexander Vladishev [ 2013 Aug 26 ]

Š¢hanks for your report! I confirm the issue.

Comment by Alexander Vladishev [ 2013 Aug 26 ]

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

Comment by Alexander Vladishev [ 2013 Aug 26 ]

It's a regression. Broken in version 2.0.0rc5 by:

------------------------------------------------------------------------
r27570 | sasha | 2012-05-16 18:18:50 +0300 (Wed, 16 May 2012) | 2 lines

...G...PS. [ZBXNEXT-1220] added support of monitoring of log files more than 2GB
...G...... [ZBX-3151] added support of monitoring files more than 2GB in the vfs.file.size[] item
Comment by richlv [ 2013 Aug 26 ]

(1) documented in https://www.zabbix.com/documentation/2.0/manual/installation/known_issues - please verify

as clarified by sasha, this only affected proxy, server processed data normally. updated the note, please review again

sasha CLOSED

Comment by Andris Zeila [ 2013 Sep 02 ]

Successfully tested

Comment by Alexander Vladishev [ 2013 Sep 02 ]

Fixed in pre-2.0.9 r38265 and pre-2.1.4 (trunk) r38266.

Generated at Fri Apr 26 13:42:25 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.