Hello, Well, I don't think this is a rate limit for following reasons: - The old server we will replace with this new one, is based on RHEL 5. It currently supports the same load (for rsyslog) than the new one on which we have the issues. FYI the load are tons of real time messaging server logs, coming from tens of linux postfix and microsoft exchange servers. - We did on the new server this test: we have sent only a few logs from a remote syslog "sender", and we also had the same issues.
One thing I forgot to mention in my first e-mail is that all the traffic is sent by the rsyslog server to a PostgreSQL 9.2.3 database (running of course on the same server). This afternoon, I downloaded the latest SOURCE vesion of rsyslog: 7.2.6-2 I did the compilation myself, including RELP and PGSQL modules. I did some testing again with this freshly compiled version, and again I've exactly the same issues... I don't know what to do now... :-( Thanks for your reply any way :-) KR. Nicolas - United Nations International Computing Center Geneva Rm Kml <[email protected]> a écrit : > Hi Nicolas, > Maybe you have found a bug or rate limit on imrelp... > Why cannot split few syslog src to few new relp ports like 20515 20516 > 20517...? (each différent ports on each différent cpu...) > Maybe add rate limit on syslog src srv ? > Regards > Rmkml > > ---------------------------------------------------------------- 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.
