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

Unclear error message while launching experiment #53

Closed
KroArtem opened this issue Mar 8, 2016 · 4 comments
Closed

Unclear error message while launching experiment #53

KroArtem opened this issue Mar 8, 2016 · 4 comments

Comments

@KroArtem
Copy link

KroArtem commented Mar 8, 2016

Hello, I've downloaded imunes from git, compiled and installed it. Also I installed required dependencies. When I tried to launch a simple case and when I tried to launch an example from examples repo, I got the following error:
2016-03-08 04-26-58

However, I've got docker installed and running (1.6.2), ovs-vswitchd is said to be already working, xterm and ncenter are also installed. Is there any way to get some more additional output to understand what's working incorrectly?

P.S. I forgot to mention I use Ubuntu 16.04, kernel 4.4.0

@denisSal
Copy link
Member

denisSal commented Mar 8, 2016

Hi!

IMUNES checks if docker is running by executing docker ps command and checking if its return value is 0 (running) or 1 (error). I recommend that you try running docker ps and check its output.

@KroArtem
Copy link
Author

KroArtem commented Mar 9, 2016

Hello, thanks for the quick response, docker ps said about not having enough privileges. ok, sudo usermod -aG user fixed this. Then imunes asked about running it with sudo and after then asked to do imunes -p to download docker images. (or it was in another order, first imunes -p then request for sudo). After this examples load and seem to be working. I have some more questions but will dig into documentation first. :)

Thanks for your help. :) However, I think more precise error message would be good.

@denisSal
Copy link
Member

denisSal commented Mar 9, 2016

You are right, I modified the error messages and added some more details.

Actually, the main problem is that we should first check for sudo rights, and then requisites. I fixed that in edbdefb.

@denisSal denisSal closed this as completed Mar 9, 2016
@KroArtem
Copy link
Author

KroArtem commented Mar 9, 2016

Thanks!

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

No branches or pull requests

2 participants