-
Notifications
You must be signed in to change notification settings - Fork 7
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
CN is stuck in an infinite loop (almost denial-of-service like situation) for certain applications #56
Comments
Another example - for sqlpage, which runs a few sql's and takes about 20-25 seconds to load because of multiple SQL. This is where some controls around the application behaviour might help.
|
Regarding your first post: This looks like a misconfigured network / Regarding your second post: This seems a bit like an application issue to me... ContainerNursery tries to generate as little load as possible for the target service by using Do you have time to create a pull request for this? If not, I can take a look at this some time but I can't give you a timeframe. |
Hi !, thanks for your reply. The ping logs from within the CN container shows that it is able to reach the filebrowser container without any issues. Apologies If I dont understand this correctly, can you please help me understand what / how network configuration can be an issue here, because as soon as I restart the container, I am able to reach the applications via the url. Also the CN config file directly uses the container name, there is no other network specific configuration (apart from pi-hole that points the local dns - which I am sure is working fine as there are other applications that CN works with perfectly fine like handbrake, MkDocs, etc).
The ping logs from within the CN container shows that it is able to reach the filebrowser container.
|
Since you ping'ed If pinging works please also try |
Thanks for the reply @ItsEcholot . So, while the web browser is still stuck on the "waking up files" page, I ran the curl command from within CN container and getting the response from filebrowser (looks to be the html for the page file browser UI).
So it looks like even though the filebrowser container is up and ping / curl commands are responding correctly, the UI is still stuck in the "Waking up" page. |
Does CN need additional configurations for -
Because, looks like CN is basically Getting into a infinite requests loop situation for certain applications, and this is happening indefinitely until CN container is restarted manually. And because I have a pi-hole in my setup, the pihole container is seeing crazy amounts of traffic from CN.
I have also tried using the
proxyUseCustomMethod: GET
, and it doesn't seem to help.When manually looking at the docker logs for these applications, they are all starting up fine. Some start up really fast (Dozzle, FileBrowser) and some of them are slightly slower (code-server, homeAssistant), but even these are only a matter of about 3-8 seconds on a desktop.
In all these cases, I do not understand why CN is not able to recognize the container is up, because as soon as I restart CN the request for all of them is going thru successfully.
The issue seems to be when CN is starting the container. If the container is already running (i.e when CN is restarted), there is no issue it seems.
Applications I have seen this issue with - FileBrowser, dozzle, codeserver (vscode), n8n, HomeAssistant, etc (probably many more that I havent come across).
Debug Logs for File Browser -
Debug Logs for dozzle -
I also have few other containers where I do not see this issue. For example, MkDocs is another container I have which does take over 5 seconds to start up, however CN handles it well without any issues. Its only certain containers above that have this issue.
The text was updated successfully, but these errors were encountered: