Thanks Rainer, Jumping from 5.8.10 to 8.11.0 would take some time to adapt. Is there a way this could be debugged and solved?
Prashant On Fri, Jul 3, 2015 at 7:10 PM, Rainer Gerhards <[email protected]> wrote: > As first measure, please update to the currently supported version > 8.11.0. There are package repositories for major distros on the > rsyslog site. We had many changes in that area since 5.8 was current > and chances are good a simple upgrade will solve your issue. > > Rainer > > 2015-07-03 14:34 GMT+02:00 Prashant Batra <[email protected]>: > > Hi, > > > > I have a rsyslog client and server running and configured to talk using > > RELP. > > > > Things work fine, but intermittently, I see the messages are not > delivered > > to the server, a restart of rsyslogd on the client solves the problem. > > > > rsyslog version on both client and server is 5.8.10 > > rsyslogd 5.8.10, compiled with: > > FEATURE_REGEXP: Yes > > FEATURE_LARGEFILE: No > > GSSAPI Kerberos 5 support: Yes > > FEATURE_DEBUG (debug build, slow code): No > > 32bit Atomic operations supported: Yes > > 64bit Atomic operations supported: Yes > > Runtime Instrumentation (slow code): No > > > > > > During problematic time period, if I put strace on all the threads of > > rsyslod, I observe, one of the threads read log message from /dev/log. > The > > other thread which I suppose is responsible for sending it out to the > > server reports a failure in one of the futex calls- > > > > futex(0x7f94eb898240, FUTEX_WAKE_PRIVATE, 1) = 0 > > write(4, "INFO 2015/07/03 10:52:04.837 AN"..., 93) = 93 > > futex(0x7f94eb898e34, FUTEX_WAIT_PRIVATE, 31973, NULL) = 0 > > futex(0x7f94eb898240, FUTEX_WAKE_PRIVATE, 1) = 0 > > futex(0x7f94eb889f04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, > > 20781, {1435920724, 838367278}, ffffffff) = -1 ETIMEDOUT (Connection > > timed out) > > futex(0x7f94eb888ea0, FUTEX_WAKE_PRIVATE, 1) = 0 > > write(6, "WARN 2015/07/03 10:52:04.838 AN"..., 53) = 53 > > > > > > I wasnt able to find an exact bug on this problem already open on > > rsyslog, but some related problem statements exist on the internet. > > > > I am looking out for help to figure out what could the problem be, > > what could be the cause, and how to fix it. > > > > Regards, > > > > Prashant > > _______________________________________________ > > 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. > -- Prashant Batra Follow the dreams!! _______________________________________________ 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.
