jokob-sk
commented
1 month ago Hi @nathang21 ,
I see the app restarting when new devices are created.
22:29:34 [Update Devices] - (if not empty) cur_SSID -> (if empty) dev_SSID
22:29:34 [Update Devices] - (if not empty) cur_Type -> (if empty) dev_DeviceType
22:29:34 [Update Devices] - (if not empty) cur_Name -> (if empty) dev_NAME
22:29:37 [MAIN] Setting up ...
22:29:37 [conf.tz] Setting up ...
22:29:37
22:29:37 The backend restarted (started). If this is unexpected check https://bit.ly/NetAlertX_debug for troubleshooting tips.
22:29:37
22:29:37 Permissions check (All should be True)
22:29:37 ------------------------------------------------
22:29:37 /config/app.conf | READ | True
22:29:37 /config/app.conf | WRITE | True
22:29:37 /db/app.db | READ | True
22:29:37 /db/app.db | WRITE | True
22:29:37 ------------------------------------------------Can you try to surface the exception which can't be captured in logs by following this guide: https://github.com/jokob-sk/NetAlertX/blob/main/docs/DEBUG_TIPS.md#2-surfacing-errors-when-container-restarts-
Start the container via the terminal with a command similar to this one:
docker run --rm --network=host \
-v local/path/netalertx/config:/app/config \
-v local/path/netalertx/db:/app/db \
-e TZ=Europe/Berlin \
-e PORT=20211 \
jokobsk/netalertx:latest⚠ Please note, don't use the -d parameter so you see the error when the container crashes. Use this error in your issue description.Or check the docker or Portainer logs? You should be able to see an exception before the container restarts.
Thanks in advance, j
nathang21
Is there an existing issue for this?
Current Behavior
App is frequently unresponsive, but the container remains healthy. It appears from the log the backend restarts frequently, from my experience it happens at least a couple times per hour.
One thing to add, this happened earlier on when I was setting up netalertx, and I scrapped the entire config/db because I couldn't figure out the issue, and it was stable for some period of time (I didn't monitor closely). Now that it has reoccured, i'm opening an issue to report since I've failed to debug on my own.
Expected Behavior
The backend to remain stable or at least the logs to clearly indicate why it is unstable.
Steps To Reproduce
This happens continuously, even after restarting/recreating the docker container, perhaps there is an invalid config or a corrupted DB but i'm not sure.
app.conf
docker-compose.yml
What branch are you running?
Production
app.log
app.log was too big to upload here, hosted here instead.
Debug enabled