-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Container crashing without any apparent reason #107
Comments
Could you try disabling services one by one to see the culprit ? |
Hi Thom-x, thanks for your reply |
Ok, at least everything else is OK.
|
No return of the command, I don't have ps in the image so I can't check if it's running, but I doubt it runs. Also, no message in logs following the start of thttpd. And no access to the page with the published port. |
Probably not working (it should be blocking). You could check the exit code |
Same issue with port 4242, and I get a "1" exit code. |
Strange, I would suggest changing path, ports, etc to see what's wrong. |
Okay, seems strange, I just popped the container on a new host, no persistent storage, basic options. In the meantime I will run without the WebUI. |
Sorry for that :/ |
No worries, you already did a great work, thanks! |
I can confirm the same problem: as soon as you enable SERVICE_ENABLE_HTTP -- it crashes. Starting @Thom-x, if you can provide any instructions on how and where to check |
|
This is also occurring for me on my PI Zero 2 W now. Host OS is Manjaro ARM aarch64. I can do any troubleshooting steps that might be needed to get to the bottom of this :) Only thing common I can see with fl0wfr is the same RTL2838 SDR but not sure how that could affect thttpd. |
@Littlejth Did you try starting the container with only HTTPD enabled ? |
With only the HTTP service enabled, it still just starts and stops again. Attached is the log file of a single time I attempted to start it after creating the container with only HTTP enabled. |
I created a branch to switch from thttpd to httpd, I'll let you now when the image is available so you can test and give me the feedback #114. |
You can test it with |
Hello Thom-x, |
What is the content of |
Ok funny, it's probably not compatible for all arch... |
It did start working on my aarch64 pi but obviously not a great solution if it doesn't work for AMD64 as well :) |
@fl0wfr which docker version are you running? v23? Users of my Home Assistant Add-On raised the same issue: MaxWinterstein/homeassistant-addons#149 I guess,
|
@MaxWinterstein yes I'm using Docker 23.0.4 |
@fl0wfr no linux memory expert here, but can you give the https://docs.docker.com/engine/reference/commandline/run/#ulimit Something like docker run --ulimit nofile=1048576 ...... might be worth a shot |
@MaxWinterstein it works now. That should do the trick for now, thanks. |
Thanks, I'll do a PR image for testing quickly and release of it's all good 👍 ! |
Awesome! Can't really test it myself here, hope it works 🤞 |
You let me know and I will test it ;) |
I still ran into issues with Max' update on his HA-addon. Still OOM errors on thttp. See screenshot in MaxWinterstein/homeassistant-addons#149 (comment) if helpful |
I guess the fix in my addon is placed wrongly. I think s6 starts the httpd stuff in another shell/session/thread/... where my adjustment is not read. #118 is made a little bit different |
You can try with the image |
It works, thank you :) |
Nice 😄 let's do a release then. |
It's now available with 1.21.0 or latest 👍 |
Running Unraid 6.11.5 (latest stable version), which has Docker v20.10.21. At least on my system, this update to 1.21.0 does not seem to work. After I update, my (otherwise so far completely stable) container stops automatically without any error logged. This happens a few seconds after start of the container. Downgrading back to v1.20.0 fixes the issue, so I would assume, that this is related to this issue? If I have time later on, I can try the dedicated PR tag/image, if that gives a clearer picture. |
@fl0wfr did you see any difference with the cpu usage? |
No, around 3 and 7% CPU usage, running on a Celeron N5105. |
Specifications
Expected Behavior
Simply start and feed FR24/PiAware
Actual Behavior
Crash loop without any error
Steps to Reproduce the Problem
--device=/dev/bus/usb:/dev/bus/usb
-v "/etc/localtime:/etc/localtime:ro"
-e "FR24FEED_FR24KEY=<>"
-e "PIAWARE_FEEDER_DASH_ID=<>"
-e "HTML_SITE_LAT=<>"
-e "HTML_SITE_LON=<>"
-e "HTML_SITE_NAME=<>"
-e "SERVICE_ENABLE_ADSBEXCHANGE=false"
-e "MLAT_EXACT_LAT=<>"
-e "MLAT_EXACT_LON=<>"
-e "MLAT_ALTITUDE_MSL_METERS=<>"
-e "SERVICE_ENABLE_PLANEFINDER=false"
-e "TZ=Etc/GMT+0"
--tmpfs /run:exec,size=32M
--tmpfs /planefinder/log:exec,size=32M
--tmpfs /usr/lib/fr24/public_html/data:size=32M
--restart=unless-stopped
--network=myNetwork
--name fr24feed
thomx/fr24feed-piaware:PR-106
I've attached some logs.
fr24feed.log
The text was updated successfully, but these errors were encountered: