
I've been running stunnel to tunnel syslog-ng messages to a loghost. On some occasions, be it a network maintenance issue or fluke, if a server loses connection to the loghost, stunnel starts spewing broken pipe messages to syslog. Sometimes shutting it down while it is doing this, it will dump core. Anyone have an idea on what might be causing this? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Stephen Tanner HP-UX Systems Administrator Network Support Services Lee County Clerk of Courts =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

"Stephen Tanner" <stanner@leeclerk.org> wrote:
Sometimes shutting it down while it is doing this, it will dump core.
Here is an axample of a good core dump error report. http://stunnel.mirt.net/pipermail/stunnel-users/2004-August/000009.html http://stunnel.mirt.net/pipermail/stunnel-users/2004-August/000015.html The report should include at least: - stunnel version line (for example "stunnel 4.05 on powerpc-ibm-aix5.2.0.0 FORK with OpenSSL 0.9.7d 17 Mar 2004"). - stack backtrace. It's a good idea to read: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Best regards, Mike
participants (2)
-
Michal Trojnara
-
Stephen Tanner