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.

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

Handling max. no. connections between Expedient and AMs #197

Open
CarolinaFernandez opened this issue Jan 30, 2014 · 1 comment
Open

Handling max. no. connections between Expedient and AMs #197

CarolinaFernandez opened this issue Jan 30, 2014 · 1 comment

Comments

@CarolinaFernandez
Copy link
Member

Matthew, via Vassilis, reported the following:

When the maximum number of connections between Expedient and the other islands' AMs is reached, everything seems down and the Expedient island admin needs to manually restart apache.

Idea: to check either Expedient or the daemon script that pings each AM in order to. See if the connections are active and remove those who are not. Even worse, automatically restarting Apache (!).

@CarolinaFernandez
Copy link
Member Author

Somewhat related to #177.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant