[syslog-ng]syslog-ng - crond
Peter Bieringer
pb@bieringer.de
Thu, 13 Feb 2003 15:06:06 +0100
Hi again,
--On Wednesday, February 12, 2003 07:10:42 PM +0100 Peter Bieringer
<pb@bieringer.de> wrote:
>
>
> --On Wednesday, February 12, 2003 02:34:28 PM +0100 Achim Gsell
> <achim@cybercity.ch> wrote:
>
>> On Wednesday 12 February 2003 13:29, Roberto Nibali wrote:
>>
>>> I've not observed this behavior with glibc-2.1.3 yet (that's what
>>> I'm using for my distribution). Might it be that newer glibc's
>>> have this problem?
>>
>> glibc-2.1.3 has this problem but glibc-2.2.5 and glibc-2.3.1 not:
> ...
>
> My system is running glibc-2.2.5-42 (RHL 7.3). What now?
>
> Are there any other daemons known which do not log further on after
> syslog-ng restarts?
The broken crond logging with syslog-ng is syslog-ng related, because with
syslogd, it still works:
Feb 12 06:37:27 dhcp-1-66 kernel: Kernel logging (proc) stopped.
Feb 12 06:37:27 dhcp-1-66 kernel: Kernel log daemon terminating.
Feb 12 06:37:28 dhcp-1-66 syslog: klogd shutdown succeeded
Feb 12 06:37:29 dhcp-1-66 exiting on signal 15
Feb 12 06:37:29 dhcp-1-66 syslogd 1.4.1: restart.
Feb 12 06:37:29 dhcp-1-66 syslog: syslogd startup succeeded
Feb 12 06:37:29 dhcp-1-66 syslog: klogd startup succeeded
Feb 12 06:37:29 dhcp-1-66 kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Feb 12 06:37:29 dhcp-1-66 syslog: syslogd shutdown succeeded
Feb 12 06:33:00 dhcp-1-66 crond[852]: (*system*) RELOAD (/etc/crontab)
Feb 12 06:33:00 dhcp-1-66 CROND[1192]: (root) CMD (/bin/true)
Feb 12 06:33:01 dhcp-1-66 crond[1215]: (CRON) STARTUP (fork ok)
Feb 12 06:34:00 dhcp-1-66 CROND[1219]: (root) CMD (/bin/true)
Feb 12 06:35:00 dhcp-1-66 CROND[1221]: (root) CMD (/bin/true)
Feb 12 06:36:01 dhcp-1-66 CROND[1261]: (root) CMD (/bin/true)
Feb 12 06:37:00 dhcp-1-66 CROND[1309]: (root) CMD (/bin/true)
Feb 12 06:38:00 dhcp-1-66 CROND[1349]: (root) CMD (/bin/true)
vixie-cron-3.01-64
And here some more information.
Starting from above I've compiled syslog-ng on this clean system and
installed it. Steps
1) sysklogd is running, crond is logging
2) shutdown of sysklogd, start of syslog-ng, crond is logging further on
3) change syslog-ng settings
source local {
+ unix-stream("/dev/log");
+ unix-stream("/dev/log" keep-alive(yes) max-connections(512));
- udp(ip(0.0.0.0) port(514));
+ #udp(ip(0.0.0.0) port(514));
internal();
};
and restart syslog-ng, crond is logging further on
4) restart crond, crond is logging again
5) restart syslog-ng -> crond is no longer logging
Log:
Feb 12 06:56:37 dhcp-1-66 kernel: Kernel logging (proc) stopped.
Feb 12 06:56:37 dhcp-1-66 kernel: Kernel log daemon terminating.
Feb 12 06:56:39 dhcp-1-66 syslog: klogd shutdown succeeded
Feb 12 06:56:39 dhcp-1-66 exiting on signal 15
Feb 12 06:58:47 dhcp-1-66 syslog-ng[10279]: syslog-ng version 1.5.26
starting
Feb 12 06:58:47 dhcp-1-66 syslog-ng: ......
Feb 12 06:58:47 dhcp-1-66 syslog-ng: syslog-ng startup succeeded
Feb 12 07:00:02 dhcp-1-66 syslog-ng[10279]: syslog-ng version 1.5.26 going
down
Feb 12 07:00:02 dhcp-1-66 syslog-ng[10312]: syslog-ng version 1.5.26
starting
Feb 12 07:00:02 dhcp-1-66 syslog-ng: ......
Feb 12 07:00:02 dhcp-1-66 syslog-ng: syslog-ng startup succeeded
Feb 12 07:01:39 dhcp-1-66 syslog-ng[10312]: syslog-ng version 1.5.26 going
down
Feb 12 07:01:40 dhcp-1-66 syslog-ng[10349]: syslog-ng version 1.5.26
starting
Feb 12 07:01:40 dhcp-1-66 syslog-ng: ......
Feb 12 07:01:40 dhcp-1-66 syslog-ng: syslog-ng startup succeeded
Feb 12 07:02:13 dhcp-1-66 crond: crond shutdown succeeded
Feb 12 07:02:14 dhcp-1-66 crond: crond startup succeeded
Feb 12 07:03:03 dhcp-1-66 syslog-ng[10349]: syslog-ng version 1.5.26 going
down
Feb 12 07:03:04 dhcp-1-66 syslog-ng[10407]: syslog-ng version 1.5.26
starting
Feb 12 07:03:04 dhcp-1-66 syslog-ng: ......
Feb 12 07:03:04 dhcp-1-66 syslog-ng: syslog-ng startup succeeded
# tail -f /var/log/cron
Feb 12 06:53:00 dhcp-1-66 CROND[9013]: (root) CMD (/bin/true)
Feb 12 06:54:00 dhcp-1-66 CROND[9016]: (root) CMD (/bin/true)
Feb 12 06:55:00 dhcp-1-66 CROND[10040]: (root) CMD (/bin/true)
Feb 12 06:56:00 dhcp-1-66 CROND[10118]: (root) CMD (/bin/true)
Feb 12 06:59:00 dhcp-1-66 CROND[10283]: (root) CMD (/bin/true)
Feb 12 07:00:00 dhcp-1-66 CROND[10286]: (root) CMD (/bin/true)
Feb 12 07:01:00 dhcp-1-66 CROND[10319]: (root) CMD (/bin/true)
Feb 12 07:01:00 dhcp-1-66 CROND[10320]: (root) CMD (run-parts
/etc/cron.hourly)
Feb 12 07:02:00 dhcp-1-66 CROND[10353]: (root) CMD (/bin/true)
Feb 12 07:02:14 dhcp-1-66 crond[10376]: (CRON) STARTUP (fork ok)
Feb 12 07:03:00 dhcp-1-66 CROND[10381]: (root) CMD (/bin/true)
Strange?
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/