[syslog-ng] [Bug 190] syslog-ng with TCP source, fails to shutdown properly, and generates core dump

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=190





--- Comment #13 from Marvin Nipper <marvin.nipper at stream.com>  2012-08-29 18:08:32 ---
Created an attachment (id=64)
 --> (https://bugzilla.balabit.com/attachment.cgi?id=64)
Output from truss-based execution

OK.   I didn't wait for a reply to the previous post, and just went ahead and tried to do this, so that I could get back to other things.

At first, I would start it, and stop it, and I was not getting a core dump (whereas I was previously able to force one of those almost immediately).  I'm
guessing that the use of truss may have altered the timing, or something.  Anyway, I then decided to just let it run for about 10 minutes, and then issued a
stop command, and it generated the standard output error that I had seen the other day:
iv_port_upload_one: got error 2[No such file or directory]

.... and it also generated a dump, and then the truss execution terminated as well.  At least under the context of truss, the syslog-ng process did not
continue to run (which is what they do without truss involved).

So... I'm attaching the file here.  Let me know if this is what you need, or not.  I've retained the core dump (if you need something from that), and also have
the original 3.3.6 executables still in place, so that I can swap between those, and the "working" version, if you need me to do something different with
truss.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.