Hi, I guess, it is not a new topic, but I could not find any solution, yet. As always, deadlines are near and things seems to get worse and worse, so I thought I give the list a try...
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). 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? 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. Best regards Ole _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
