Hi,
After upgrading to stunnel 5.19 I noticed the log file no long reports the pid of stunnel processes. Instead I find the constant string [0].
Sep 14 12:15:30 hostname stunnel: LOG6[0]: SSL closed (SSL_read)
This information is very useful to isolate individual connections. Do later stunnel versions report the pid correctly?
I am using fork mode. My syslog is defined as local6.debug and stunnel.conf contains debug=local6.info.
Thank you.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 14.09.2015 18:27, Philippe Anctil wrote:
After upgrading to stunnel 5.19 I noticed the log file no long reports the pid of stunnel processes. Instead I find the constant string [0].
https://www.stunnel.org/static/stunnel.html The option name is logId.
I am using fork mode. My syslog is defined as local6.debug and stunnel.conf contains debug=local6.info.
You are right. The default log id type (sequential) does not work with fork threads. Why do you use fork threads? Just don't do it.
Mike
2015-09-14 12:41 GMT-04:00 Michal Trojnara Michal.Trojnara@mirt.net:
I am using fork mode. My syslog is defined as local6.debug and stunnel.conf contains debug=local6.info.
You are right. The default log id type (sequential) does not work with fork threads. Why do you use fork threads? Just don't do it.
Quite a while ago we tested the thread mode. We say memory leaks and went with fork for that reason.
Thanks very much for the logId bit. logId=thread is exactly what I needed.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 15.09.2015 23:08, Philippe Anctil wrote:
I am using fork mode. My syslog is defined as local6.debug and stunnel.conf contains debug=local6.info.
You are right. The default log id type (sequential) does not work with fork threads. Why do you use fork threads? Just don't do it.
Quite a while ago we tested the thread mode. We say memory leaks and went with fork for that reason.
I'll be glad to see the configuration that caused the per-thread memory leak. Are you sure it wasn't simply heap fragmentation?
stunnel is way faster with PTHREADS, because SSL/TLS session cache doesn't work in stunnel with FORK threading.
Thanks very much for the logId bit. logId=thread is exactly what I needed.
Great. I have fixed incrementing the sequential thread number in the FORK threading mode. The fix will be included in the next release of stunnel. Thank you for reporting the problem.
Mike
-
Michal Trojnara -
Philippe Anctil