OS/2, eCS & ArcaOS - Technical > Utilities

controlling stunnel as if it were a daemon

(1/2) > >>

Tom L:
Hi guys, I have a serious issue on a production system, I would appreciate any help anyone can give.

I am using Paul's stunnel port on ArcaOS 5 to provide TLS to a http server. Everything works well, except, occasionally, CPU will spike to 100% and stunnel has to be restarted. Then things are fine again for a couple of hours. I tried newer versions of the stunnel port, but they only make it worse.

I will open a ticket with Paul, but I need a workaround. On OS/2, stunnel will not run as a daemon/service, so I presume I cannot assign a PID to it and then kill it at will. I am launching it like this: stunnel.exe stunnel.conf

Even with debug = 7 (highest), there is nothing in the log that would as much as hint at what might be turning stunnel into a CPU hog.  :(

Is there a way I could automate the restarts? What I am doing now is: log on thru VNC, click in the stunnel window, press Ctrl-C and run it again.

Meta:

ArcaOS 5.0.6 EN
stunnel 5.50 on i386-pc-os2-emx
Lotus Domino Go 4.6.2.5

Andreas Schnellbacher:

--- Quote from: Tom L on May 17, 2021, 02:40:06 pm ---On OS/2, stunnel will not run as a daemon/service, so I presume I cannot assign a PID to it and then kill it at will.

--- End quote ---
Yes, you can, if there's an executable. The PID is not assigned by you, but by the system whenever a process is started. You may want to check it with Top. Another useful tool to kill a process without knowing the PID and much more is Pgmcntrl.

Neil Waldhauer:
Can you post the relevant part of stunnel.conf? I'm trying to do something like that, too.

Tom L:
Thank you, Andreas, that looks very promising! I'll check that out and post back.

Neil, here you go. Domino runs on localhost:8443, stunnel listens on :443 and just passes requests to Domino.

--- cut ---
[https]
accept  = x.x.x.x:443
connect = 127.0.0.1:8443
cert = webcrt.pem
sslVersion = TLSv1.2
ciphers = ECDHE-ECDSA-AES128-GCM-SHA256
--- cut ---

Andi B.:
If you want to find out the PID you can use something like

--- Code: ---pstat /C |find /I "clipview"
--- End code ---
Use your process name (stunnel?) instead clipview from my example.

Navigation

[0] Message Index

[#] Next page

Go to full version