-
-
Notifications
You must be signed in to change notification settings - Fork 47
Description
I am trying to restart my stunnel service on Ubuntu 18.04. But whenever I do restart using systemctl restart stunnel4.service, it fails. But when I do /etc/init.d/stunnel4 restart, it works.
π₯ 4.1.0
π©βπ³ 16.8.14
π© Ubuntu 18.04. AWS Cloud
Steps To Reproduce
Steps to reproduce the behavior:
- systemctl restart stunnel4.service -> Fails
π Expected behavior
Stunnel restarting successfully.
π Actual behavior
stunnel4[19673]: [ ] Compression disabled stunnel4[19673]: [ ] Snagged 64 random bytes from /dev/urandom stunnel4[19673]: [!] PRNG seeded with 128 bytes total stunnel4[19673]: [!] PRNG was not seeded with enough random bytes stunnel4[19673]: [!] /etc/stunnel/stunnel.conf:49: "[redis]": Failed to initialize TLS sytemd[1]: stunnel4.service: Control process exited, code=exited status=1 stunnel4[19673]: [Failed: /etc/stunnel/stunnel.conf] stunnel4[19673]: You should check that you have specified the pid= in you configuration file systemd[1]: stunnel4.service: Failed with result 'exit-code'. systemd[1]: Failed to start LSB: Start or stop stunnel 4.x (SSL tunnel for network daemons).
β Additional context
As mentioned above, the restart is failing when used with systemctl, but works when I restart with /etc/init.d/stunnel4 restart