Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Repeated container failures on ShinyProxy startup #529

Open
kramerrs opened this issue Oct 15, 2024 · 2 comments
Open

Repeated container failures on ShinyProxy startup #529

kramerrs opened this issue Oct 15, 2024 · 2 comments
Labels
enhancement

Comments

@kramerrs
Copy link

This is related to the uptime monitoring thread: #517
As well as the restarter thread:
#510

I implemented a rudimentary monitoring solution, which searches the logs and finds when a Delegate fails to start, then sends an email.

One thing that I have noticed is that when I restart ShinyProxy in our test environment and in production with a larger memory and more CPU the containers often fail repeatedly to start, likely due to competition for resources.

These apps don't typically take five or ten tries to launch after a new user connects, the new container comes up with only the normal docker mesh delay.

Is there any way to serialize or stagger the launches?
@kramerrs
Copy link
Author

Just add some more info. I can reduce the number of startup failures by increasing the container-wait-time, though this is very long.

container-wait-time: 1200000

@LEDfan
Copy link
Member

LEDfan commented Oct 28, 2024

Hi, this is currently not possible, but I do see the need for this. I created an internal ticket for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LEDfan @kramerrs
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy