Linuxserver/sabnzbd: stops responding on port 8080 after a few days and requires restart
I have sabnzbd running in a portainer stack with a vpn and after a couple of days it stops responding although the container is still passing its healthcheck and shows as healthy in portainer. There is a dependency on a vpn and that works fine. Port 8080 access to sabnzbd is enabled on the vpn container and works fine for a few days and then stops.
When the container is in the failed state, I can still get to the console via portainer although it fails if I try to communicate outbound like this: ‘curl ipconfig.io’
After a quick restart it is fine again. I am using autoheal and the following healthcheck command.
test: curl -fSs 127.0.0.1:8080 || exit 1
Any idea what I might need to do to restart the container auto-magically?
The only reference I get to 8080 in my logs are the following on start-up of the container.
2021-11-25T11:28:34.495985557Z 2021-11-25 06:28:34,495::INFO::[SABnzbd:1437] Starting web-interface on :::8080
2021-11-25T11:28:34.496244047Z 2021-11-25 06:28:34,496::INFO::[_cplogging:213] [25/Nov/2021:06:28:34] ENGINE Bus STARTING
2021-11-25T11:28:39.684937669Z /usr/local/lib/python3.8/dist-packages/cherrypy/process/servers.py:416: UserWarning: Unable to verify that the server is bound on 8080
2021-11-25T11:28:39.685427890Z 2021-11-25 06:28:39,684::INFO::[_cplogging:213] [25/Nov/2021:06:28:39] ENGINE Serving on http://:::8080
2021-11-25T11:28:39.685475761Z 2021-11-25 06:28:39,684::INFO::[_cplogging:213] [25/Nov/2021:06:28:39] ENGINE Bus STARTED
2021-11-25T11:28:39.685511502Z 2021-11-25 06:28:39,684::INFO::[SABnzbd:1473] Starting SABnzbd.py-3.4.2
2021-11-25T11:28:39.690755858Z 2021-11-25 06:28:39,690::INFO::[dirscanner:117] Dirscanner starting up
2021-11-25T11:28:39.692120187Z 2021-11-25 06:28:39,691::INFO::[panic:239] Launching browser with http://127.0.0.1:8080/sabnzbd