-
-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to restart Stunnel #87
Comments
I have the same issue and I am using Ubuntu 18.04.6 LTS on my server |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
π 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
The text was updated successfully, but these errors were encountered: