Unable to reload Stunnel in Linux
Hi, Normally, I would call "kill -HUP" with Stunnel's process ID to make it reload the configuration in Linux. I was very surprised when I tried that and the process stopped. Why would HUP cause it to exit, rather than reload the config? It doesn't do that on every machine. Thanks.
On Tue, Apr 27, 2021 at 02:42:29AM -0400, [email protected] wrote:
Hi,
Normally, I would call "kill -HUP" with Stunnel's process ID to make it reload the configuration in Linux.
I was very surprised when I tried that and the process stopped. Why would HUP cause it to exit, rather than reload the config?
It doesn't do that on every machine.
Does it say anything in the logs? G'luck, Peter -- Peter Pentchev [email protected] [email protected] [email protected] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
On 2021-04-27 02:55, Peter Pentchev wrote:
On Tue, Apr 27, 2021 at 02:42:29AM -0400, [email protected] wrote:
Hi,
Normally, I would call "kill -HUP" with Stunnel's process ID to make it reload the configuration in Linux.
I was very surprised when I tried that and the process stopped. Why would HUP cause it to exit, rather than reload the config?
It doesn't do that on every machine.
Does it say anything in the logs?
G'luck, Peter
Hmm. The log file is empty. Maybe I need to enable logging.
On 2021-04-27 03:28, [email protected] wrote:
On 2021-04-27 02:55, Peter Pentchev wrote: On Tue, Apr 27, 2021 at 02:42:29AM -0400, [email protected] wrote: Hi,
Normally, I would call "kill -HUP" with Stunnel's process ID to make it reload the configuration in Linux.
I was very surprised when I tried that and the process stopped. Why would HUP cause it to exit, rather than reload the config?
It doesn't do that on every machine. Does it say anything in the logs?
G'luck, Peter
Hmm. The log file is empty. Maybe I need to enable logging. Hmm. I tried running it in the foreground to test. Receiving the HUP caused an error: 2021.04.27 07:30:19 LOG5[ui]: Configuration successful INTERNAL ERROR: Bad magic at options.c, line 1059 Aborted (core dumped)
On Tue, Apr 27, 2021 at 03:31:31AM -0400, [email protected] wrote:
On 2021-04-27 03:28, [email protected] wrote:
On 2021-04-27 02:55, Peter Pentchev wrote: On Tue, Apr 27, 2021 at 02:42:29AM -0400, [email protected] wrote: Hi,
Normally, I would call "kill -HUP" with Stunnel's process ID to make it reload the configuration in Linux.
I was very surprised when I tried that and the process stopped. Why would HUP cause it to exit, rather than reload the config?
It doesn't do that on every machine. Does it say anything in the logs?
G'luck, Peter
Hmm. The log file is empty. Maybe I need to enable logging.
Hmm. I tried running it in the foreground to test. Receiving the HUP caused an error:
2021.04.27 07:30:19 LOG5[ui]: Configuration successful INTERNAL ERROR: Bad magic at options.c, line 1059 Aborted (core dumped)
Ah. Oops. If this is stunnel from the official Debian package, this may be my fault: https://bugs.debian.org/987265 Are you running this on Debian? What version of Debian? If it is "testing" (what is soon to become Debian 11), could you try fetching the stunnel4_5.56+dfsg-10*.deb file for your architecture from https://ftp.debian.org/debian/pool/main/s/stunnel4/ and installing that using `apt install ./stunnel4_4.56*deb`? If you are on Debian 10 (buster), I will upload a bugfix to stable-proposed-updates today or tomorrow and see how long it takes to clear the queue, but from the line number (1059) it looks like you are running Debian testing. Sorry about that! G'luck, Peter -- Peter Pentchev [email protected] [email protected] [email protected] PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
participants (2)
-
gorf＠hyperfunk.club -
Peter Pentchev