Arch Linux

Description:
I believe this started after the first upgrade to 3.0.3-1. The errors began on the 31st after I rebooted.

The behavior before 3.0.3 allowed files not owned as root to be written to. After the upgrade syslog-ng complains and refuses to write to the files. The daemon syslog-ng is running as root so I don't understand why it doesn't have permission. I have Zimbra installed and the log files aren't owned by root. If I delete the log file and restart syslog then syslog will recreate it with the owner zimbra and the group log with the permissions 640. It will actually write a few lines before the ownership is changed and then complain that it doesn't have permission. If I remove owner("zimbra") from the syslog-ng.conf file and delete the file it will write to the file without any errors since it gets recreated and is owned by root. I upgraded syslog to the latest version today and the problem still exists.


Additional info:
-rw-r--r-- 1 zimbra zimbra 0 2009-08-04 11:13 zimbra.log

Aug 4 11:14:15 mycotoxin syslog-ng[25406]: Error opening file for writing; filename='/var/log/zimbra.log', error='Permission denied (13)'

[2009-07-21 21:21] upgraded syslog-ng (3.0.1-6 -> 3.0.3-1)
[2009-08-04 09:43] upgraded syslog-ng (3.0.3-1 -> 3.0.3-2)

filter f_local0 { facility(local0); }; # zimbra
destination zmail { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_mail); destination(zmail); }; # zimbra
destination local0 { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_local0); destination(local0); }; # zimbra
filter f_auth { facility(auth); }; # zimbra
destination zmauth { file("/var/log/zimbra.log" owner("zimbra") ); }; # zimbra
log { source(src); filter(f_auth); destination(zmauth); }; # zimbra


Steps to reproduce:
chown bin /var/log/everything.log
/etc/rc.d/syslog-ng restart

tail -100 /var/log/syslog.log

You should see a permission denied as soon as something is written.