hallo liste, seit einiger zeit stirbt regelmäßig mein cron daemon ab. dies hat zur folge das sachen in /etc/cron.weekly nicht ausgeführt werden ( unter anderem mein backup). Jun 1 21:15:21 sysiphus /usr/sbin/cron[530]: (CRON) INFO (pidfile fd = 3) Jun 1 21:15:21 sysiphus /usr/sbin/cron[531]: (CRON) STARTUP (fork ok) Jun 1 21:15:21 sysiphus /usr/sbin/cron[531]: (CRON) INFO (Running @reboot jobs) Jun 1 21:17:01 sysiphus kernel: cron[1060]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 21:34:01 sysiphus kernel: cron[2328]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 21:54:01 sysiphus kernel: cron[2698]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 22:00:01 sysiphus kernel: cron[2812]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 22:14:01 sysiphus kernel: cron[3098]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 22:17:01 sysiphus kernel: cron[3153]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 22:34:01 sysiphus kernel: cron[3487]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 22:54:01 sysiphus kernel: cron[3872]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 23:00:01 sysiphus kernel: cron[3987]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 23:14:01 sysiphus kernel: cron[479]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] Jun 1 23:17:01 sysiphus kernel: cron[550]: segfault at 0 ip 00000000 sp bfc3da1c error 4 in cron[8048000+7000] die fehlermeldung ist immer gleich. sysiphus:~$ cat /etc/default/cron # Cron configuration options # Uncomment this option for LSB name support in /etc/cron.d/ LSBNAMES='-l' # Whether to read the system's default environment files (if present) # This will make cron set a proper charset for the mails it sends # Comment this or set it to something other than 'yes' to prevent # cron from reading it. #READ_ENV="yes" # Extra options for cron, see cron(8) # For example, set a higher log level to audit cron's work EXTRA_OPTS="-L 10" profbunny@sysiphus:~$ cat /etc/crontab # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file. # This file also has a username field, that none of the other crontabs do. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin #MAILTO=root # m h dom mon dow user command 17 * * * * root run-parts --report /etc/cron.hourly 25 6 * * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6 * * 7 root test -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 6 1 * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly /etc/cron.hourly ist leer, ich geh davon aus, das der fehler aus /etc/cron.d kommt. loglevel hochsetzen (s.o.) hilft leider nicht. ll /etc/cron.d insgesamt 12K -rw-r--r-- 1 root root 244 1. Apr 2004 anacron -rw-r--r-- 1 root root 111 26. Jan 21:10 drupal5 -rw-r--r-- 1 root root 149 8. Mai 23:00 smtpd cron per gdb starten, funktioniert leider nicht. ich bin am ende mit meinem latein. bug report hab ich keinen gefunden. tagesaktuelles sid. ich hoffe jemand von euch hat einen tip für mich. tia micha
Attachment:
pgptpptiPPM92.pgp
Description: PGP signature