Multiple Concierge on one system

[Awarua-]

In raising this issue, I confirm to the best of my ability the following (please check boxes, e.g. [X]):

• There are no duplicate issues.
• The problem does not lie with an upstream dependency.
• An installed module/integration/service/other is not causing your problem.
• This is reproducible on the latest codebase with up to date NPM dependencies.
• I have added appropriate labels to this issue.

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.

[drkno]

"I have added appropriate labels to this issue."
Ummm... bug? Regression?

"The problem does not lie with an upstream dependency."
Segfault = node? Sure its our issue to work out why but still

[Awarua-]

Yes, it could be with upstream, but no real indication of what causes it.
It's also harder to track down now that the core is async.

[drkno]

It's also harder to track down now that the core is async.

I will admit that. However it is async-await not raw promise so tracking down the source is possible

[drkno]

@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:
Node: v8.5.0
OS: Windows
Modules: default (2 fresh clones)
Config: default (2 fresh clones)