Thank you very much for you support, Rainer! I noticed one more thing, which might be related to the crashes: It seems like rsyslog is comsuming quite a bit memory, at times. While it allocates a handful of MB, most of the time, sometimes uses humungous amounts of memory (just like right now):
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP (...) 2663 root 1455M 1452M sleep 59 0 0:01:07 0,0% rsyslogd/9 If a shortage in available memory would cause the crashes, it would also explain, why the process dependent core (dump) files that solaris generates for rsyslog always are several GB, I guess. If memory is short the server gets quite unresponsive (no wonder), which is a phenomenon that is also reported to me about the clients by the vendor who is running them. Ole P.S. Taking even a bit more memory, now: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP (...) 2663 root 1461M 1458M sleep 59 0 0:01:08 0,0% rsyslogd/9 -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Gesendet: Mittwoch, 25. Mai 2011 10:13 An: rsyslog-users Betreff: Re: [rsyslog] Heavy stability problems when using TLS OK, that makes it a bit harder ;) Rainer PS: I got the debug log, will try to make some sense out of it today _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
