-
Notifications
You must be signed in to change notification settings - Fork 406
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
Demo stack launch order #23
Comments
Hi, This exception is thrown when the service tries to register itself in We probably should handle this exception more gracefully. But anyhow, this should not be related. I tried to reproduce the ordering Cheers, Éric On Tue, Apr 23, 2013 at 1:30 AM, sharpyfox notifications@github.com wrote:
|
Yes, I recheck logfiles. Seems that first generated exception looks like:
and only after this crash router fail with zookeper exception. |
That's interesting... I pushed a very small update so that the exception actually prints the port range it tries to bid to. If you could run that and check that this port is actually not used on your machine, that would be helpful. Thanks! Éric |
I've modified your code a bit, and receive this message:
|
Hello Eric, do you have any news on this issue? |
I'll do some research and saw that |
Hi, Yes, please do. I was just investigating something else and it seems that a Thanks! Éric On Wed, Jun 5, 2013 at 2:36 AM, Nikita Vasiliev notifications@github.comwrote:
|
Seems like everything is resolved here so I'm closing this issue. |
added video parsing for width and height
Hello guys. Seems that if I launch demo stack as described in wiki in this order:
./build/x86_64/bin/mock_exchange_runner
./build/x86_64/bin/launcher --node localhost --script ./launch.sh sample.launch.json
router failed with exception:
Though if I launch in another order:
./build/x86_64/bin/launcher --node localhost --script ./launch.sh sample.launch.json
./build/x86_64/bin/mock_exchange_runner
the launch is successful. I do not think that this is a serious problem, but still unpleasant
The text was updated successfully, but these errors were encountered: