On Wed, May 25, 2016 at 10:31 PM, Ted Unangst <t...@tedunangst.com> wrote:
> Jeff Ross wrote: > > jross@fw:/home/jross $ tail -10 /var/log/messages > > May 21 04:00:01 fw syslogd: restart > > May 25 15:53:58 fw syslogd: exiting on signal 15 > > May 25 15:53:58 fw syslogd: start > > May 25 15:53:58 fw syslogd: recvfrom unix: Connection reset by peer > > May 25 15:56:00 fw syslogd: exiting on signal 15 > > May 25 15:57:42 fw syslogd: start > > May 25 15:57:42 fw syslogd: recvfrom unix: Connection reset by peer > > May 25 16:01:09 fw syslogd: exiting on signal 15 > > May 25 16:01:09 fw syslogd: start > > May 25 16:01:09 fw syslogd: recvfrom unix: Connection reset by peer > > This is quite unusual and not observed by anyone else. > > I'm not sure what else to suggest, but your environment seems quite > different. > > It looks like syslog starts and then exits immediately due to some kind of startup error. You have changed some default setting. Clear syslog env to defaults. Paste the output of ls -l /var/log/messages* to get a clue on what the message file sizes are.
