Thanks for the ideas. Fortunately It was something much more benign: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551885
All fixed now! Dylan On Mon, Nov 16, 2009 at 6:47 PM, Bill Broadley <b...@broadley.org> wrote: > Dylan Beaudette wrote: >> U just noticed that some cron events were not firing, and the following >> errors >> in dmesg: >> >> [6514433.261103] cron[9252]: segfault at 6fab8db0 ip b7f16012 sp bfc305e3 >> error 4 in ld-2.9.so (deleted)[b7f16000+1c000] >> [6514433.263982] cron[9253]: segfault at 6fab8db0 ip b7f16012 sp bfc305e3 >> error 4 in ld-2.9.so (deleted)[b7f16000+1c000] >> [6514990.285433] cron[9385]: segfault at 6fab8db0 ip b7f16012 sp bfc305e3 >> error 4 in ld-2.9.so (deleted)[b7f16000+1c000] > > Out of ram or disk? An unchecked failed malloc or fopen if used might well > generated that error. ALso a corrupted disk, but I'd expect more disk related > errors with something like that. > > >> >> >> yikes! Any ideas? >> >> Cheers, >> Dylan >> > > _______________________________________________ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
