On Wed, Jun 26, 2013 at 4:03 PM, wm-lists <wm-li...@nixpeeps.com> wrote:

> Interestingly I found the issue, or at least a solution to it yesterday.  I
> assumed there was some issue in cached syslog entries since the debug info
> showed connections to one or both of the udp destinations for syslog.
>
> Eventually I found my way to /var/lib/rsyslog and discvored about 10 files
> in there.
> $WorkDirectory /var/lib/rsyslog # where to place spool files
>
> Ended up whacking those files and rsyslog started up fine.
>
> Since it's only one server, I assumed there was some kinda garbage in
> there..
>
>
ah, that could be related to spool files - the 5.8.x series was especially
picky in this regard...

Rainer

>
>
> On Wed, Jun 26, 2013 at 9:54 AM, Rainer Gerhards
> <rgerha...@hq.adiscon.com>wrote:
>
> > could you run it under valgrind control?
> >
> > Also note that this version is no longer project-supported, but I could
> at
> > lest have a quick look. In any case, I suggest upgrading to the currently
> > supported 7.4 version. RPM repositories are available here:
> >
> > http://www.rsyslog.com/rhelcentos-rpms/
> >
> > Rainer
> >
> >
> > On Tue, Jun 25, 2013 at 3:47 PM, wm-lists <wm-li...@nixpeeps.com> wrote:
> >
> > > I hate Lotus Domino.  Terrible software.   Using different mail client
> > now.
> > >
> > > So here's some output that may be useful.
> > >
> > > Thanks! Will
> > >
> > > [root@ ~]#  /sbin/rsyslogd -c5 -f /etc/rsyslog.conf  -dn^C
> > > [root@ ~]# rpm -q rsyslog
> > > rsyslog-5.8.10-6.el6.x86_64
> > > [root@ ~]# cat /etc/redhat-release
> > > Red Hat Enterprise Linux Server release 6.4 (Santiago)
> > >
> > > # uname -r
> > > 2.6.32-358.2.1.el6.x86_64
> > >
> > > Here's the end of the startup
> > >
> > > strace /sbin/rsyslogd -c5 -f /etc/rsyslog.conf  -dn
> > >
> > > 6520.727364975:7fb1db0bb700: action 0x7fb1de2db5b0 call returned 0
> > > 6520.727368077:7fb1db0bb700: regular consumer finished, iret=0, szlog
> > 3562
> > > sz phys 3570
> > > 6520.727372912:7fb1db0bb700: we deleted 8 objects and enqueued 0
> objects
> > > 6520.727380039:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727383102:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727393242:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727396631:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727406629:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727409757:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727420332:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727423526:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727433838:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727436855:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727445030:7fb1db0bb700: strm 0x7fb1de2defa0: file 7 read 4096
> bytes
> > > 6520.727452367:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727455551:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727474937:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727479294:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727490402:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727493783:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727500364:7fb1db0bb700: delete batch from store, new sizes: log
> > 3562,
> > > phys 3562
> > > 6520.727507175:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727510138:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727520683:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727523924:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727533601:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727536923:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727546593:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727549532:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727559126:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727562358:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > 6520.727572405:7fb1db0bb700: MsgSetTAG in: len 7, pszBuf: kernel:
> > > 6520.727575567:7fb1db0bb700: MsgSetTAG exit: pMsg->iLenTAG 7,
> > > pMsg->TAG.szBuf: kernel:
> > > futex(0x7fb1dc989b60, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
> > > +++ killed by SIGSEGV +++
> > > Segmentation fault
> > > _______________________________________________
> > > rsyslog mailing list
> > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > http://www.rsyslog.com/professional-services/
> > > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a
> myriad
> > > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > > DON'T LIKE THAT.
> > >
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com/professional-services/
> > What's up with rsyslog? Follow https://twitter.com/rgerhards
> > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> > DON'T LIKE THAT.
> >
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
> of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
> DON'T LIKE THAT.
>
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to