|
sponsored links |
|
|
sponsored links
|
|
1
29th October 20:30
External User
Posts: 1
|
syslog-ng did not write to /var/log/messages for more than 6 days
Hi,
as I see from 'ps', syslog-ng is running and in state Ss. In syslog-ng.conf I find the option sync(0), the console output is current, but the last entry in /var/log/message is more than 6 days old. Sending signal -1 to syslog-ng forces syslog-ng to write new entries to /var/log/messages. What could be the reason for that long break? Juergen -- Juergen Rose <rose@rz.uni-potsdam.de> Max-Delbrueck-Zentrum -- gentoo-user@gentoo.org mailing list |
|
|
|
2
29th October 20:30
External User
Posts: 1
|
syslog-ng did not write to /var/log/messages for more than 6 days
Maybe you're rotating /var/log/message and didn't send an HUP signal to
syslog-ng. In this case, /var/log/message inode changed but syslog-ng doesn't know yet. greetings -- gentoo-user@gentoo.org mailing list |
|
|
|
3
29th October 20:30
External User
Posts: 1
|
syslog-ng did not write to /var/log/messages for more than 6 days
Hi José,
Thank you. I thought, that logrotate itself should send this signal, but I will check this. Juergen Juergen Rose <rose@rz.uni-potsdam.de> Max-Delbrueck-Zentrum -- gentoo-user@gentoo.org mailing list |
|
|
Linear Mode
