FreeBSD 10.0-RELEASE-p7

i suspect it might be caused by usermacros not supported as part of the item key parameter

rich, not 100% true

i get without a usermacro the same error, please look here

logrt["/var/log/pg_log/postgresql-.*\.log","PANIC|FATAL|ERROR|[Ee]rror"]

93306:20140821:144655.627 there are no files matching 'postgresql-.*\.log' in '/var/log/pg_log/'

i think this is a bug...

Does zabbix user have Read rights to the "pg_log" directory ?
I'd give 777 for path and files for testing.

Hi Oleksiy,
yes this should work.
But why not 744 = path and 644 = logfile ?
Only work if path have 777 and then works with logfile 644

Short Info, also work with Usermacro...

In order to read contents of a directory, one needs to have execution bit set on it.

That's right, so set the directory to 755 an the file to 644.

Hi,
yes 755 also works.

I read the *nix manual an found this:

Read allows you to list the files inside of it.
Execute allows you to enter it and access files (or other directories) inside.

This is the reason why we need also "execution bit".
Thanks for the help and sorry for the noise.
The ticket can be closed.

Greetings to Riga and zabbix team.

Closing, it is not a bug.

Note that in MC this bit named "execute/search by ...".

Reopening the issue. It should be investigated why a user was getting message "there are no files matching ..." instead of "Cannot open directory ...for reading" in case of wrong directory permissions.

Confirmed. My mistake - logrt[] item in Zabbix agent does not distinguish between absence of matching log files and insufficient rights to read their attributes (e..g. mtime, size). Both cases are processed as "we saw this file a moment ago, now we try to find its attributes and fail, no problem - probably the file has gone, proceed to the next one".

Proposed solution for logrt[] on UNIX/GNU/Linux platforms: if logrt[] does not find matching files in the directory, check access rights ("execute" permission on the directory). In case of insufficient access rights (no "execute" permission) write a warning into agent log file, otherwise write a warning about missing files. In both cases do not make the logrt[] item NOTSUPPORTED. "man access" warns about problems which can occur if log files reside on NFS or FUSE mounts, therefore we issue only a warning and continue, but do not turn the item NOTSUPPORTED if access() reports no "execute" permission on the directory.

Available in development branch svn://svn.zabbix.com/branches/dev/ZBX-8646 (for Zabbix 2.0.x)

(1) Does not compile on Windows:
..\..\..\src\zabbix_agent\logfiles.c(1313) : error C2065: 'X_OK' : undeclared identifier

andris RESOLVED in r48647.

wiper CLOSED

Successfully tested

Fixed in versions pre-2.0.13 r48663, pre-2.2.7 r48666, pre-2.3.5 r48671.

(2) A note
"If there are several matching log files for logrt[] item and Zabbix agent is following the most recent of them and this most recent log file is deleted, a warning message “there are no files matching ”<regexp mask>” in ”<directory>” is logged. Zabbix agent ignores log files with modification time less than the most recent modification time seen by the agent for the logrt[] item being checked."
added to:
https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/log_items?&#important_notes
https://www.zabbix.com/documentation/2.2/manual/config/items/itemtypes/log_items?&#important_notes
https://www.zabbix.com/documentation/2.4/manual/config/items/itemtypes/log_items?&#important_notes

wiper looks good, CLOSED