On 10/26/2012 3:31 PM, Angus McIntyre wrote: > Eric Broch wrote: >> ... I'm getting the following error after the fact and don't know >> what it means. >> >> /usr/share/toaster/isoqlog/bin/cron.sh: line 20: 12280 Segmentation >> fault $ISOQLOG > /dev/null 2> /dev/null > I see those occasionally during the course of normal operations. > > My guess has been that the program isn't able to handle all the possible > data that can occur in the logs, and segfaults when it hits something it's > not prepared to handle. Double-byte characters? Overlong strings? > Malformed log lines? > > Your crash might have corrupted one of the logs being processed. > > My experience has been that, left to itself, these errors will go away > after a while, as log rotation rotates the 'damaged' log out of the way. > > If you care particularly about the output of isoqlog, then you'll want to > identify the problem logfile and patch it up by hand. If you don't, then > you may be able to just wait it out. > > Angus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Angus. I just waited it out, and the error went away.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
