On Tue, 2013-03-12 at 16:42 +0100, Nicolas HAHN wrote: > Also, if it can helps, my infrastructure is designed like that: > > Our syslog senders are with latest Rsyslog V 5.10 RPMs, of course sending > with omrelp on one rsyslog receiver (the new ones I have issues with), and > with another rsyslog receiver in production runing rsyslog version 4.8.x. > > So basically we have: > > rsyslog omrelp senders 5.10.x ---> rsyslog imrelp receiver 4.8.x on RHEL 5 > (working like a charm) ---> PostgreSQL 9.2.3 with ompgsql > ---> rsyslog imrelp > receiver 7.2.6-2 on RHEL 6 (having issues) ---> Postgresql 9.2.3 with ompgsql > > Do you think I should try to upgrade on rsyslog sender from version 5.10.x to > the same version of the server I've issues with ? > I don't think so (but I may be wrong). If I were troubleshooting this, I wouldn't do. The most important thing is to see what is actually happening at the central server.
Rainer > KR. > Nicolas > - > United Nations International Computing Center > Geneva > > Rainer Gerhards <[email protected]> a écrit : > > > On Tue, 2013-03-12 at 14:57 +0100, Nicolas HAHN wrote: > >> Hello David, > >> > >> As written at the top of my e-mail, I confirm SELINUX is disabled > >> and there is no firewall rules preventing the traffic to come. > >> Furthermore, it works like a charm on the current rsyslog production > >> server we try to replace, and which is using rsyslog 4.8.x on RHEL 5. > >> > >> When syslog stops, nothing shows in the debug logs as like rsyslog > >> "loose" some IMRELP servers, it also looses its debugging ability. > >> That's what I wrote in a previous e-mail: it display tons of things > >> on the screen when ran with the -d flag, then it stops displaying > >> and give you back the hand on the shell. But we can still see > >> rsyslog in the process table running with its -d flag... > >> > > Do you run it with just -d or -dn? Without -n (As in -dn), it > > auto-backgrounds and this means you usually lose the debug information. > > > > Also, I would suggest to run it under valgrind control, as this can > > bring up any misadressing problems. That would be along the lines of > > > > $ valgrind rsyslogd -dn ...other options.... > > > > Rainer > > _______________________________________________ > > 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. > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > _______________________________________________ > 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.
