Look at the date! (Transmit Errors)

Andrei Bulucea andrewb@ituner.com
Tue Nov 2 18:02:31 1999


Look at this one. Check out the minute in the time stamp!

[root@build Content]# cat /var/log/mess* | grep "Tran"
Oct 31 16:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 10219/10235 command 000c0000. 
Oct 31 21:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 18338/18354 command 00030000. 
Nov  1 06:03:10 build kernel: eth0: Transmit timed out: status 0000  0000 at 9809/9825 command 00030000. 
Nov  1 17:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 10126/10142 command 00030000. 
Nov  1 22:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 18257/18273 command 00030000. 
Nov  2 03:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 26664/26680 command 00030000. 
Nov  2 08:01:13 build kernel: eth0: Transmit timed out: status 0000  0000 at 35345/35361 command 00030000. 

Well, it looks like the ethernet crash is *actually* generated by a cron
job, in my case. This program is using sound drivers (OSS). 

[nobody@build /]$ crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/cron.txt installed on Thu Oct 28 15:34:57 1999)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
1 * * * * /home/cron-cntl/executor.sh OneClickAudioEncoder-1 /usr/local/rprod/bin/realproducer.nobody --force-overwrite -a 2 -l 6:1 -t 1 -f 1 -s localhost:4040/audio1.rm -u broadcast -p live2me  -b "" -c " "

It could be something else, not necessarly Donald's driver, no?

And a correction from my previous posting: 

The third machine, the one that was OK was not running the cron job!!!!
Andrei