-
Notifications
You must be signed in to change notification settings - Fork 36
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
Multiple Concierge on one system #275
Comments
"I have added appropriate labels to this issue." "The problem does not lie with an upstream dependency." |
Yes, it could be with upstream, but no real indication of what causes it. |
I will admit that. However it is async-await not raw promise so tracking down the source is possible |
@Awarua- Aside from the obvious issue in the screenshot above (can't have 2 instances of boss running on same machine unless they bind to a different port), I can't reproduce on the following configuration: |
In raising this issue, I confirm to the best of my ability the following (please check boxes, e.g. [X]):
Expected Behaviour:
I can run multiple instances of Concierge on the same system
Actual Behaviour:
One instance will run, the rest will crash on startup with a seg fault.
Steps to Reproduce:
Try to start more than one Concierge instance, from different directories
This is a problem for the future if we want horizontal scaling.
Work around atm, is to use docker containers.
The text was updated successfully, but these errors were encountered: