You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this when the listening port was already taken:
$ blocky --config /path/to/config.yaml
[...]
[2023-09-20 11:55:23] INFO server: Starting server
[2023-09-20 11:55:23] INFO server: http server is up and running on addr/port 4000
[2023-09-20 11:55:23] ERROR server start failed: start tcp listener failed: listen tcp :53: bind: address already in use
$ echo $?
0
I think blocky should exit with non-zero status in this case. That should signal the error to systemd, unlike now where systemd thinks the exited blocky process is completely fine/expected.
blocky version: 0.21
EDIT: Pasted wrong log -- this one shows the address already in use error.
The text was updated successfully, but these errors were encountered:
I noticed this when the listening port was already taken:
I think blocky should exit with non-zero status in this case. That should signal the error to systemd, unlike now where systemd thinks the exited blocky process is completely fine/expected.
blocky version: 0.21
EDIT: Pasted wrong log -- this one shows the
address already in use
error.The text was updated successfully, but these errors were encountered: