Closed denji closed 5 years ago
At least on Debian, systemd restores the daemon if it exits with error (after 30s). And the ui is updated as expected:
(...)
jun 17 21:21:07 opensnitchd[25020]: created by github.com/evilsocket/opensnitch/daemon/vendor/google.golang.org/grpc/transport.newHTTP2Client
jun 17 21:21:07 opensnitchd[25020]: /home/test/go/src/github.com/evilsocket/opensnitch/daemon/vendor/google.golang.org/grpc/transport/http2_client.go:289 +0xcc6
jun 17 21:21:07 systemd[1]: opensnitchd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
jun 17 21:21:37 systemd[1]: opensnitchd.service: Service RestartSec=30s expired, scheduling restart.
jun 17 21:21:37 systemd[1]: opensnitchd.service: Scheduled restart job, restart counter is at 2.
jun 17 21:21:37 systemd[1]: Stopped OpenSnitch is a GNU/Linux port of the Little Snitch application firewall..
jun 17 21:21:37 systemd[1]: Starting OpenSnitch is a GNU/Linux port of the Little Snitch application firewall....
jun 17 21:21:37 systemd[1]: Started OpenSnitch is a GNU/Linux port of the Little Snitch application firewall..
If the connection to the UI is not restored maybe it's a different problem. journalctl/daemon logs would be helpful
We need a procedure to restoring connect
opensnitch-ui
after the fall of the demonopensnitchd
and restartingopensnitchd.service
.