Hi there, have anyone faced a cron crashing in a jail when changing the /etc/crontab? I'm running a jail with nsswitch using pgsql backend and I've noticed a strange behaviour of my crontab. Every time I change the /etc/crontab file I get (or make crontab -e and save it) /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) in /var/log/cron and immediately after that the cron dies with a core (core file is in /var/cron/cron.core), I've made a ktrace but nothing strange can be seen in it, heres the link to the kdump file: http://valqk.ath.cx/ktrace.out.txt any ideas appriciated! cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
ok, just made a break trough, when I added cron to /etc/libmap.conf (here is my libnap.conf: user# cat /etc/libmap.conf [httpd] libpthread.so.2 libthr.so.2 libpthread.so libthr.so [cron] libpthread.so.2 libthr.so.2 libpthread.so libthr.so ) cron stopped crashing. I've wrote an angry mail at sunday morning (GMT+2) about apache crashing (apache-worker) after a buildworld (by ezjail-admin), and added the above lines fixed my problem. Seems like I'm having a problem with libpthread but I don't know exaclty what. pls anyone help me, I have no idea why all apps using libpthread are crashing after the upgrade. This is only in the jail! in real system everything works as expected. pls help with ideas and tips! thanks. Anton - Valqk wrote:> Hi there, > have anyone faced a cron crashing in a jail when changing the > /etc/crontab? > I'm running a jail with nsswitch using pgsql backend and I've noticed > a strange behaviour > of my crontab. > Every time I change the /etc/crontab file I get (or make crontab -e > and save it) > /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) > in /var/log/cron > and immediately after that the cron dies with a core (core file is in > /var/cron/cron.core), > I've made a ktrace but nothing strange can be seen in it, > heres the link to the kdump file: > > http://valqk.ath.cx/ktrace.out.txt > > any ideas appriciated! > > cheers, > valqk. >-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
We've found the problem with a friend of mine. /etc/crontab has wrong syntax in defining crons - I've used spaces instead of tab between the * * * * * and the username.... really my bad, maybe copied the string from the other machine it was running on and pasted without cheching but... I don't think it's normal an incorrect crontb syntax to crash the crontab with coredump? is it? the other strange thing, the line below the incorrect syntax there is a line with a correct one, that wasn't working too, and even if the cron don't core, the correct line wasn't working.... maybe the cron stops parsing if see incorrect line? is this a suggested behaviour? maybe it's a bug, along with the crashing with core when no tab used between the * * * * * and the user... dunno, pls someone that's familiar to tell... 10x! :-) Anton - Valqk wrote:> Hi there, > have anyone faced a cron crashing in a jail when changing the > /etc/crontab? > I'm running a jail with nsswitch using pgsql backend and I've noticed > a strange behaviour > of my crontab. > Every time I change the /etc/crontab file I get (or make crontab -e > and save it) > /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) > in /var/log/cron > and immediately after that the cron dies with a core (core file is in > /var/cron/cron.core), > I've made a ktrace but nothing strange can be seen in it, > heres the link to the kdump file: > > http://valqk.ath.cx/ktrace.out.txt > > any ideas appriciated! > > cheers, > valqk. >-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
I've found the actual line from which the cron was crashing. By mistake I've uncommented: #1,31 0-5 * * * root adjkerntz -a and that's in a jail enviornment, when I commented it again the cron started working as expected. I agree that it's stupid ti call this command when in jail, because jail don't have perms to touch system time, but is this behaviour of the cron a suggested one? cron to die if it calls this? I don't think so? what would you say? Anton - Valqk wrote:> Hi there, > have anyone faced a cron crashing in a jail when changing the > /etc/crontab? > I'm running a jail with nsswitch using pgsql backend and I've noticed > a strange behaviour > of my crontab. > Every time I change the /etc/crontab file I get (or make crontab -e > and save it) > /usr/sbin/cron[32864]: (*system*) RELOAD (/etc/crontab) > in /var/log/cron > and immediately after that the cron dies with a core (core file is in > /var/cron/cron.core), > I've made a ktrace but nothing strange can be seen in it, > heres the link to the kdump file: > > http://valqk.ath.cx/ktrace.out.txt > > any ideas appriciated! > > cheers, > valqk. >-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.