Quoting Jochen Bern via stunnel-users <stunnel-users@stunnel.org>:
Am 25.02.26 um 03:48 schrieb Mike via stunnel-users:
It definitely executes the correct command, but then the whole service shuts down and I get this: Process: 5099 ExecStart=/usr/bin/stunnel4 /etc/stunnel/ attuverse.conf (code=exited, status=0/SUCCESS)
Off the top of my head: Since you apparently made only minimal changes to the config, chances are that the starting stunnel fork()s, the child puts itself in the background, and the parent exits (proper behaviour for getting fired up by initd). systemd likes to interact with the spawned services (notice when they've terminated abnormally, etc.), so it might expect stunnel *not* to detach itself. "status=0" suggests that stunnel *itself* did *not* see any problem.
I thought the same thing, however, there is no stunnel process running at all.
if I execute this command: /usr/bin/stunnel4 /etc/stunnel/myconffile.conf
(Is that an actual mismatch, or did you just forget to redact the config file's name above ... ?)
Redaction error. :) Thanks.
Kind regards, -- Jochen Bern Systemingenieur Binect GmbH