Closed jokob-sk closed 10 months ago
jokob-sk
commented
10 months ago Hey @lzsix,
Can you please let me know what issue you are facing in more detail? I can't spot anything out of the ordinary in the log file. Please provide screenshots if they would help me to understand your issue.
Thanks, j
jokob-sk
commented
10 months ago It would be also useful to enable debug logging as described here: https://bit.ly/PiAlertDebug for a more detailed logging output.
lzsix
commented
10 months ago @jokob-sk thanks for the fast reply.
i tried spinning up the container with the above mentioned docker compose file. I will try to change the config file and see if i can enable debug logging from there.
I cannot access the web interface. The container seems to be disconnecting from my network after a while. Also nmap doesn´t show any open ports.
It seems to me that it has an issue while first booting the container. I´ll update my post with screenshots as soon as im able to get more information out of the logs.
jokob-sk
commented
10 months ago Thanks 👍
I think the main thing to look out for then is the network config (screenshot of my Synology host):
Your compose file seems to be correct (host mode is enabled), but it's worth double-checking.
Also, if the container drops off after a while then it may restart, so please disable the restart behavior so we get an exception if there is one: https://github.com/jokob-sk/Pi.Alert/blob/main/docs/DEBUG_TIPS.md#4-disable-restart-behavior-
Alternatively, try starting the container via the terminal and wait until it crashes: https://github.com/jokob-sk/Pi.Alert/blob/main/docs/DEBUG_TIPS.md#2-surfacing-errors-when-container-restarts-
Thanks, j
lzsix
commented
10 months ago I rechecked all the settings. (i am using docker on a raspi 4 with 8GB RAM)
I have setup my own network inside of portainer to have the container in my hostnetwork. See attached screenshot for the network:
I disabled automatic restarts. so far the container is running since around 15minutes. my specified address answers to ping, however no ports are open.
I am starting to suspect that the container is running fine but the webserver has a problem. is there a way i can check/alter the webserver configs.
if there is no way to look into the webserver and check if it is running into some issues i don´t want to take up any more of your valuable time as it seems to be a misconfiguration on my end. Feel free to close the issue after your reply. I very much appreciate your help and the fast replys :)
jokob-sk
commented
10 months ago I think we are getting closer. IN my Portainer instance, this is how the network looks on my end:
Are you getting anything when accessing HTTP://<your rpi IP>/20211?
You can always ssh into the container and have a look if nginx is running, but even if it isn't I assume you should be able to access HTTP://<your rpi IP>/20211.
Here is the top output inside of the running container:
20211 port by any chance?jokob-sk
commented
10 months ago Another thing, try running the pi.alert_dev container. It contains a little bit more of NGINX related logging during the startup:
pialert | [INSTALL] Setup NGINX
pialert | Removing existing PiAlert web-UI
pialert | Removing existing PiAlert NGINX config
pialert | Setting webserver to user-supplied port (20211)
pialert | [INSTALL] Run the hardware vendors update
pialert | The file ieee-oui.txt exists. Skipping update_vendors.sh...
pialert | [INSTALL] Fixing file permissions
pialert | [INSTALL] Fixing WEB_UI_DIR: /var/www/html/pialert
pialert | [INSTALL] Fixing INSTALL_DIR: /home/pi
pialert | [INSTALL] Copy starter pialert.db and pialert.conf if they don't exist
pialert | [INSTALL] Fixing permissions after copied starter config & DB
pialert | Starting nginx: nginx.
@jokob-sk i am getting connection denied error when i try to access it via the webpage. I assume it is due to no open ports. will try with the dev image later. also i will try to test a bit with the network settings.
A while back i got it running easily. Had to reinstall my raspi because i had a weird 32/64bit system.
will report back after my testing. Thanks again :)
lzsix
commented
10 months ago @jokob-sk ok final update on the issue.
on the port question: it had it´s own ip address in my network so nothin really was running on that ip other than pialert.
the top page was just the right tip. i checked and nginx wasn´t running. when i startet it port 80 opened with the default page.
I then deleted all traces of pialert and kinda got it working now with the dev image.
I very much appreciate your help on the issue, thanks 🥇
jokob-sk
commented
10 months ago Thanks for the update @lzsix - glad it's working now. Weird setup issue though, hope it was only a blip. Will close this :)
Please note that i a fairly new to this topic so it´s not of the table that i misconfigured something.
No need to rush, thanks for the help in advance :)
docker-compose.yml:
Here are some logs:
Portainer Log:
Originally posted by @lzsix in https://github.com/jokob-sk/Pi.Alert/issues/520#issuecomment-1874683683