[ZBX-15267] Log monitoring doesn't work when log file is on non-system drive Created: 2018 Dec 05  Updated: 2018 Dec 05  Resolved: 2018 Dec 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 4.0.2
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Vadims Kurmis Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: activeagent, log
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File App.log    

 Description   

Steps to reproduce:

  1. I have a log file App.log on E:\ disk.
    Created 2 items (zabbix agent active):
    1) Log monitoring, key: Log[E:\Temp\App.log,ERROR]
    2) Check for file existance: vfs.file.exists[E:\Temp\App.log]
    vfs.file.exists[E:\Temp\App.log] - shows "1" in Latest data.
    Log monitoring item - never get updated. I manually add Error string in log file, but it never get updated for item data.
    When I changed log file location to C:\ drive (C:\Temp) - only then it started working for log monitoring item.

Result:
See log file.

As you can see from log file it sends value "null" for log item.
Expected:
Should just work.

 Comments   
Comment by Vadims Kurmis [ 2018 Dec 05 ]

Forgot to add:

I add the following line to log file:

09:26:11.004 ERROR 123!

 

Anyways, it works when file is on C: drive.

These are regular vmware hard drives.

Comment by Vadims Kurmis [ 2018 Dec 05 ]

Okay, found it was not related to drive location.

It was because of Unicode encoding of log file in E:\

After I changed file encoding to UTF-8 it started working fine.

 

Comment by Vadims Kurmis [ 2018 Dec 05 ]

Not an issue.

Generated at Sat Apr 20 18:34:59 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.