Re: [syslog-ng] I/O error since upgrade to v1.9.9-1 [again w/o attachments]
Yesterday I updated my Debian Etch (kernel 2.6.16-1) with syslog-ng v1.9.9-1.
I had to modify syslog-ng.conf, cause syslog-ng did not start after upgrading (syntax error line xxx).
I already reported similar issues in our bugzilla about (currently) unimplemented features in the 1.9 branch which were working in the 1.6 branch. Hopefully Bazsi will implement the missing features or convert these errors into warnings and FIXME-s in the near future :))
OK, I merged my old .conf with the new .conf and cleaned some old .log files in /var/log/.
syslog-ng script started now w/o any syntax errors, but in /var/log/messages folowing occurs massively and rapidly:
syslog-ng: I/O error occurred while writing, error='Operation not permitted (1)', fd='5' | fd='17'
If your configuration isn't confidental, please post your configuration OK, attached. (now compressed ;) with the list of the /proc/[syslog-ng_pid]/fd directory. Hm, unbeliebvable, but true: I only restarted syslog-ng and it seems to work. No more errors like mentioned above occurred anymore (until now =).
But a question besides: How can I hide the syslog-ng 'log statistics' list from being displayed in syslog? It nerves a little bit ;)
Unfortunately there are issues with the current 1.9.9 version. Syslog-ng 1.9.x entered into debian unstable and testing, so it's getting used/tested more widely than before. If your machine is in production use, I recommend to downgrade to the latest 1.6.x package, and hold it until the remaining issues will be fixed.
-- Thx in advance. E-Mails und Internet immer und �berall! 1&1 PocketWeb, perfekt mit GMX: http://www.gmx.net/de/go/pocketweb
On Wed, 2006-04-05 at 20:00 +0200, ma.LAN.ge wrote:
Yesterday I updated my Debian Etch (kernel 2.6.16-1) with syslog-ng v1.9.9-1.
I had to modify syslog-ng.conf, cause syslog-ng did not start after upgrading (syntax error line xxx).
I already reported similar issues in our bugzilla about (currently) unimplemented features in the 1.9 branch which were working in the 1.6 branch. Hopefully Bazsi will implement the missing features or convert these errors into warnings and FIXME-s in the near future :))
OK, I merged my old .conf with the new .conf and cleaned some old .log files in /var/log/.
syslog-ng script started now w/o any syntax errors, but in /var/log/messages folowing occurs massively and rapidly:
syslog-ng: I/O error occurred while writing, error='Operation not permitted (1)', fd='5' | fd='17'
If your configuration isn't confidental, please post your configuration OK, attached. (now compressed ;) with the list of the /proc/[syslog-ng_pid]/fd directory. Hm, unbeliebvable, but true: I only restarted syslog-ng and it seems to work. No more errors like mentioned above occurred anymore (until now =).
It must have been some kind of permission problem on one/more of the destination files. "Operation not permitted" was returned in response for write().
But a question besides: How can I hide the syslog-ng 'log statistics' list from being displayed in syslog? It nerves a little bit ;)
use stats_freq(-1) in your global options. -- Bazsi
On Wed, 2006-04-05 at 20:00 +0200, ma.LAN.ge wrote:
Yesterday I updated my Debian Etch (kernel 2.6.16-1) with syslog-ng v1.9.9-1.
I had to modify syslog-ng.conf, cause syslog-ng did not start after upgrading (syntax error line xxx).
I already reported similar issues in our bugzilla about (currently) unimplemented features in the 1.9 branch which were working in the 1.6 branch. Hopefully Bazsi will implement the missing features or convert these errors into warnings and FIXME-s in the near future :))
OK, I merged my old .conf with the new .conf and cleaned some old .log files in /var/log/.
syslog-ng script started now w/o any syntax errors, but in /var/log/messages folowing occurs massively and rapidly:
syslog-ng: I/O error occurred while writing, error='Operation not permitted (1)', fd='5' | fd='17'
If your configuration isn't confidental, please post your configuration OK, attached. (now compressed ;) with the list of the /proc/[syslog-ng_pid]/fd directory. Hm, unbeliebvable, but true: I only restarted syslog-ng and it seems to work. No more errors like mentioned above occurred anymore (until now =).
It must have been some kind of permission problem on one/more of the destination files. "Operation not permitted" was returned in response for write().
But a question besides: How can I hide the syslog-ng 'log statistics'
list
from being displayed in syslog? It nerves a little bit ;)
use stats_freq(-1) in your global options.
Hmmm, I restarted my firewall script, but no errors from syslog-ng appeared in /var/log/syslog ..... Maybe there is another reason or it happens only while rebooting or syslog-ng conflicts with another service. I dunno :/ How can we analyze this problem? I'm not a real linux geek, so please have some patience with me =) -- Thx in advance GMX Produkte empfehlen und ganz einfach Geld verdienen! Satte Provisionen f�r GMX Partner: http://www.gmx.net/de/go/partner
participants (2)
-
Balazs Scheidler
-
ma.LAN.ge