move the old configuration file to syslog.conf.old and reinstall the RPM to be sure it replaced the config file. That said I don't think there's a problem with that file. Is there any other syslog daemon available for that version of FC? I'm kind of grasping at straws, though -- I can't think of any reasonable conditions to cause what you're seeing. Bad disk sectors would be throwing errors around, the binary that worked once should continue to work, as you said you've done no major upgrades...
I'm pretty stumped. Is there a reason to stick with FC5 as compared to a more recent release or distro? On Fri, Jul 3, 2009 at 3:13 PM, Robert <[email protected]> wrote: > > Thanks, I tried reinstalling the package but I'm not sure if > reinstalled fine. > > I downloaded the rpm according to the same version installed, stop > sysklogd service, and run > > rpm -Uvh --replacefiles --replacepkgs sysklogd-1.4.1-36.i386.rpm > > It finished with no errors. But doesn't replace the config file. > > Anyway here's the config file: > > ==== INIT /etc/syslog.conf ========================== > # Log all kernel messages to the console. > # Logging much else clutters up the screen. > #kern.* /dev/console > > # Log anything (except mail) of level info or higher. > # Don't log private authentication messages! > *.info;mail.none;authpriv.none;cron.none /var/log/ > messages > > # The authpriv file has restricted access. > authpriv.* /var/log/ > secure > > # Log all the mail messages in one place. > mail.* /var/log/ > maillog > > > # Log cron stuff > cron.* /var/log/cron > > # Everybody gets emergency messages > *.emerg * > > # Save news errors of level crit and higher in a special file. > uucp,news.crit /var/log/ > spooler > > # Save boot messages also to boot.log > local7.* /var/log/ > boot.log > > == END ========================== > > On Jul 3, 9:54 am, "Daniel Eggleston" <[email protected]> wrote: > > If debug mode resulted in proper logging, I can't think of anything other > > > than a bad configuration file that would cause syslog not to log. If the > > > reinstall doesn't fix it, could you send along the configuration you > have? > > > > Good luck, and keep us posted. > > > > On Fri, 03 Jul 2009 09:32:20 -0500, Robert <[email protected]> > > > wrote: > > > > > > > > > > > > > thanks Daniel, my answers below > > > > > On Jul 2, 7:23 pm, Daniel Eggleston <[email protected]> wrote: > > >> Are they all logging to the same location? > > > > > Yes, on /var/log > > > > >> Run df to see if any filesystems are full. > > > > > there's enough space > > > > >> Next I'd try running syslog debug mode and see if it prints out > > >> anything > > > > > I followed the steps on: > > > > >http://www.softpanorama.org/Logs/Syslog/syslog_configuration_debuggin. > .. > > > > > I didn't see any messages on the console, but they were logged to the > > > files. > > > During the time I was runnig syslog on debugging mode the log files > > > registered everything. > > > After return to the normal mode, they stop looging. > > > > >> Have you run any major upgrades (to anything at all) recently? You > > >> could try > > >> reinstalling syslog from the RPM to ensure you have a stock > > >> configuration. > > > > > I'll try this today. > > > > > thanks. > > > > > -- > > > Robert. > > > > -- > > Using Opera's revolutionary e-mail client:http://www.opera.com/mail/ > > > -- Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Linux Users Group. To post a message, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit our group at http://groups.google.com/group/linuxusersgroup -~----------~----~----~----~------~----~------~--~---
