Container crashing without any apparent reason about docker-fr24feed-piaware-dump1090 HOT 39 CLOSED

Thanks, I'll do a PR image for testing quickly and release of it's all good 👍 !

from docker-fr24feed-piaware-dump1090.

Could you try disabling services one by one to see the culprit ?

from docker-fr24feed-piaware-dump1090.

Hi Thom-x, thanks for your reply
Seems to come from SERVICE_ENABLE_HTTP, no issue with :
SERVICE_ENABLE_DUMP1090
SERVICE_ENABLE_PIAWARE
SERVICE_ENABLE_FR24FEED
set to true

from docker-fr24feed-piaware-dump1090.

Ok, at least everything else is OK.
Could you try to start manually the HTTP server by executing the same command ?

from docker-fr24feed-piaware-dump1090.

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.

from docker-fr24feed-piaware-dump1090.

Probably not working (it should be blocking). You could check the exit code $?.
Could you change the port by a random one -p 4242?

from docker-fr24feed-piaware-dump1090.

Same issue with port 4242, and I get a "1" exit code.

from docker-fr24feed-piaware-dump1090.

Strange, I would suggest changing path, ports, etc to see what's wrong.
I'm not sure if I can help more. 😕

from docker-fr24feed-piaware-dump1090.

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.
Thanks anyway!

from docker-fr24feed-piaware-dump1090.

Sorry for that :/

from docker-fr24feed-piaware-dump1090.

No worries, you already did a great work, thanks!

from docker-fr24feed-piaware-dump1090.

I can confirm the same problem: as soon as you enable SERVICE_ENABLE_HTTP -- it crashes. Starting thttpd inside the container crashes it as well.

@Thom-x, if you can provide any instructions on how and where to check thttpd logs (I'm RedHat guy, not Debian :)) so I can troubleshot the issue.

from docker-fr24feed-piaware-dump1090.

@Thom-x, if you can provide any instructions on how and where to check thttpd logs (I'm RedHat guy, not Debian :)) so I can troubleshot the issue.

thttpd is logging on stdout (no daemon), what strange is that I'm also using it on amd64 without error.

from docker-fr24feed-piaware-dump1090.

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.

from docker-fr24feed-piaware-dump1090.

@Littlejth Did you try starting the container with only HTTPD enabled ?

from docker-fr24feed-piaware-dump1090.

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.

fr24feed-piaware.log

from docker-fr24feed-piaware-dump1090.

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.

from docker-fr24feed-piaware-dump1090.

You can test it with docker pull thomx/fr24feed-piaware:PR-114

from docker-fr24feed-piaware-dump1090.

Hello Thom-x,
Same issue, and I see this message in logs:
[http] /httpd-foreground: 7: exec: httpd: not found

from docker-fr24feed-piaware-dump1090.

What is the content of /usr/local/apache2/bin it's probably not the same between different arch ?

from docker-fr24feed-piaware-dump1090.

from docker-fr24feed-piaware-dump1090.

Ok funny, it's probably not compatible for all arch...
I need to find another candidate 😄.

from docker-fr24feed-piaware-dump1090.

It did start working on my aarch64 pi but obviously not a great solution if it doesn't work for AMD64 as well :)

from docker-fr24feed-piaware-dump1090.

@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, thttpd does what is explained here: https://developers.home-assistant.io/blog/2023/04/13/new_limits_for_add_ons/

With Home Assistant OS 10, we update to the latest Docker release 23.0. With the new Docker version the maximum number of open file descriptors for add-ons changed to infinity (sort of).
...
Also in all three cases, memory got allocated dynamically depending on the number of open file descriptors allowed (which can be determined via prlimit64 syscall, which returns a limit of 1073741816).

from docker-fr24feed-piaware-dump1090.

@MaxWinterstein yes I'm using Docker 23.0.4

from docker-fr24feed-piaware-dump1090.

@fl0wfr no linux memory expert here, but can you give the ulimit idea a try?

https://docs.docker.com/engine/reference/commandline/run/#ulimit

Something like

docker run --ulimit nofile=1048576 ......

might be worth a shot

from docker-fr24feed-piaware-dump1090.

@MaxWinterstein it works now. That should do the trick for now, thanks.

from docker-fr24feed-piaware-dump1090.

@Thom-x this might hit more and more people who switch to docker 23

I created #118 as quickfix, but switching to some more recent webserver might be a better approach ;)

from docker-fr24feed-piaware-dump1090.

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 🤞

from docker-fr24feed-piaware-dump1090.

You let me know and I will test it ;)

from docker-fr24feed-piaware-dump1090.

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

from docker-fr24feed-piaware-dump1090.

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

from docker-fr24feed-piaware-dump1090.

You can try with the image thomx/fr24feed-piaware:PR-118

from docker-fr24feed-piaware-dump1090.

It works, thank you :)

from docker-fr24feed-piaware-dump1090.

Nice 😄 let's do a release then.

from docker-fr24feed-piaware-dump1090.

It's now available with 1.21.0 or latest 👍

from docker-fr24feed-piaware-dump1090.

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.

from docker-fr24feed-piaware-dump1090.

It works, thank you :)

@fl0wfr did you see any difference with the cpu usage?

from docker-fr24feed-piaware-dump1090.

It works, thank you :)

@fl0wfr did you see any difference with the cpu usage?

No, around 3 and 7% CPU usage, running on a Celeron N5105.

from docker-fr24feed-piaware-dump1090.