Hi,
We’re having a strange problem where the server runs for just under an hour, then stops and we can’t work out why. Here is the systemctl output below (it was Active: active (running) since Wed 2022-11-16 22:49:47). Any other debugging we can do? A restart gives us another hour and we have the same issue on two different servers.
[XXX ~]$ systemctl status pritunl
● pritunl.service - Pritunl Daemon
Loaded: loaded (/etc/systemd/system/pritunl.service; enabled; vendor preset: disabled)
Active: failed (Result: signal) since Wed 2022-11-16 23:33:43 GMT; 1h 43min ago
Process: 555 ExecStart=/usr/lib/pritunl/bin/pritunl start (code=killed, signal=KILL)
Main PID: 555 (code=killed, signal=KILL)
Nov 16 22:59:20 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:20 http: TLS handshake error fr...9])
Nov 16 22:59:20 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:20 http: TLS handshake error fr...01]
Nov 16 22:59:21 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:21 http: TLS handshake error fr...eer
Nov 16 22:59:21 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:21 http: TLS handshake error fr...eer
Nov 16 22:59:21 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:21 http: TLS handshake error fr...eer
Nov 16 22:59:22 XXXX.compute.internal pritunl[555]: 2022/11/16 22:59:22 http: TLS handshake error fr...eer
Nov 16 23:10:02 XXXX.compute.internal pritunl[555]: 2022/11/16 23:10:02 http: TLS handshake error fr...eer
Nov 16 23:33:42 XXXX.compute.internal systemd[1]: pritunl.service: main process exited, code=killed,...ILL
Nov 16 23:33:43 XXXX.compute.internal systemd[1]: Unit pritunl.service entered failed state.
Nov 16 23:33:43 XXXX.compute.internal systemd[1]: pritunl.service failed.