Consolidated from both messages (so read in full ;)) > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of [email protected] > Sent: Friday, May 20, 2011 9:12 AM > To: [email protected] > Subject: Re: [rsyslog] Heavy stability problems when using TLS > > ... still crashes with 5.8.1 ... > > In the core dumps (as far as I can read something in there - had to > switch them to minimal content, otherwise they rapidly fill up my HD, > unfortunately that makes them unreadable to pstack), I see messages > like: > * errno=50: Cannot assign requested address. socket: 3 > * Urign requested address. socket (...binary rubbish...) Bind error, > errno=50: Cannot assign requested address. socket: 3 > > > No luck in capturing a crash, when running rsyslog in debug mode, so > far, will keep on trying... > > Any advice? > > We aim to use rsyslog for a centralized log server and log transmission > should be as safe and secure as possible. In our case, that means we > want to use syslog via TCP/TLS wherever possible and fall back to TCP > or UDP for those nodes that don't support TLS (or even TCP). > > I sent a post in April, already, in order to find out, if it is > possible to run plain TCP and TCP/TLS on the same server instance > (seems it does not work, so far).
Can you elaborate on what you exactly desire. I think it is possible even without modification. > At this time, we managed to connect a > few nodes via TCP/TLS, but the server and apparently even the clients > keep crashing several times a day, causing a loss messages. > > For obvious reasons, this is not what we want, at all. > > I already found a bug report, that seems to point in the right > direction, but I don't see a solution even though the status is > "resolved": > > * http://bugzilla.adiscon.com/show_bug.cgi?id=194 > > * and its spin off > http://bugzilla.adiscon.com/show_bug.cgi?id=222 > > What was the solution? You need to read the tracker in full. Unfortunately, some new bug was mangled into it when the real one was fixed. Bug 222 handles this new problem. 222 has solution information for it towards the end. >From what I read, I think your problem is not related to these two trackers (except that it seems to occur with TLS as well, which is not really a relationship ;)). > What can be done to prevent the crashes? > > I can provide whatever information you want (at least in regard to the > server), but I would rather not post our config to the public. > > The server is using rsyslog 5.8.0 on Solaris and the clients that are > currently connected run version 4.4.2 on Red Hat. I'd suggest to upgrade the clients first, and see if they continue crashing. Based on the results, let's look further. Alternatively, move the server to a Linux box and check if it keep crashing. Solaris is very different in regard to threading, so this may give us a clue. HTH Rainer > > Best regards > Ole > > > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
