Hi, I have 3.16.2 which was recently released. I see that under certain conditions rsyslogd spawns a lot of threads: 5949 root 11216 S rsyslogd 5950 root 11216 S rsyslogd 5951 root 11216 S rsyslogd 5952 root 11216 S rsyslogd 5953 root 11216 S rsyslogd 5954 root 11216 S rsyslogd 5985 root Z [rsyslogd] 6445 root Z [rsyslogd]
I had to kill the rsyslogd and restart it. The first invocation had a pid of 219 before it had to be killed. The second invocation of pid which you see above starts with 5949. The difference is the amount of zombie threads that were invoked by rsyslogd before I had to kill the first invocation of it. The question is under what conditions does rsyslogd spawn a new thread/process and why was it a zombie? I am running rsyslogd in an embedded environment and not a regular laptop/desktop. In addition, I am using busybox and I believe the syslog buffer size is set to something very low or perhaps none at all. Would this be a factor? Furthermore, I ran rsyslogd with -c3 and also without -c3 and both cases happen. Are these issues already known and fixed in a later version? Sorry, if I am asking the same questions or have the same issues as previous people but without the ability to search (or at least, I don't know how to) the archive, I don't know if my problem/questions has already been seen and/or resolved. Thank you very much for your support. Scott _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
