-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error on start nstat #117
Comments
Hello Luca, |
Here is the json file, I copied the contents to a txt file. |
Hi, I tried to change the name of the controller in the json file. From the error I found: File "/opt/nstat/stress_test/controller.py", line 81, in new I arrived therefore to this: if (name == 'ODL'): in the file stress_test / in controller py. That's why it can not connect to the pox controller? [2018-05-16 08: 42: 33,866 INFO] Authentication (password) failed. |
so better leave in you *.json configuration file "controller_name":"ODL",
Make sure to prepare your containers first. Check below for futher details |
hello, I had put the different ip (155.185.49.81) to connect to pox started not on docker. I had already installed nstat on docker following the instructions, so I should be ready to start the tests. The problem is that even if you do not change the addresses of the .json file, the test does not start. i have this error: I attach the file with the error |
From the error you sent it is now the controller build handler that complains destination path '/opt/nstat/controllers/odl_boron_pb/nstat-sdn-controllers' already exists and is not an empty directory.
|
Thanks, I deleted the folder and it worked. docker exec -i nstat /bin/bash -c "export PYTHONPATH=/opt/nstat; source /opt/venv_nstat/bin/activate; i have an error " /opt/nstat/emulators/mt_cbench/ directory not exists". I solved by changing the folder from I have another question: |
|
|
-It should not behave like this. If you run this within a container, the path is /opt/nstat/emulators/... or /opt/nstat/controllers/.. for which we have prepared /opt with proper rights so that sudo is not needed.
-If your controller/emulator node is your localhost then we have most probably to open a bug since in the build.sh script we do not check for directory rights. |
I tried to access the content odl_boron_pb via ssh, the command ./build.sh not start and after a few seconds this error appears: fatal: unable to access 'https://github.com/intracom-telecom-sdn/nstat-sdn-controllers.git/': Failed to connect to 172.28.40.9 port 3128: Connection timed out If I start with sudo ./build.sh privileges, it starts ... The error could be due to the command "sudo usermod -a -G docker $ (whoami)"? |
I modified the build.sh file in /opt/nstat/controllers/odl_boron_pb adding sudo before git clone ..., and the test start. A curiosity, how much RAM does the test need? Started the basic test and my 4GB of ram were immediately filled ... |
Hi Luca, |
I would like to try nstat, but can I start it with a controller that is not on docker?
If I try to start nstat by setting up a remote controller, i have this error:
2018-05-14 09:47:21,083 INFO ] [open_ssh_connection] Initiating SSH session with ODL node.
[2018-05-14 09:47:21,083 INFO ] [utils.netutils.ssh_connect_or_return] Trying to connect to 155.185.49.81:6633 (1/10)
[2018-05-14 09:49:28,322 ERROR ] Fail to establish ssh connection with controller node. :::::::::: Exception :::::::::::
[2018-05-14 09:49:28,323 ERROR ] Fail to establish ssh connection with controller node.
[2018-05-14 09:49:28,324 ERROR ] Error number:1
[2018-05-14 09:49:28,324 ERROR ] Fail to establish ssh connection with controller node. - ODL Exception: <class 'stress_test.controller_exceptions.CtrlNodeConnectionError'>, 132
Traceback (most recent call last):
File "/opt/nstat/stress_test/controller.py", line 125, in init_ssh
self.ssh_pass, 10)
File "/opt/nstat/util/netutil.py", line 246, in ssh_connect_or_return
password=password)
File "/usr/lib/python3.4/site-packages/paramiko/client.py", line 251, in connect
retry_on_signal(lambda: sock.connect(addr))
File "/usr/lib/python3.4/site-packages/paramiko/util.py", line 270, in retry_on_signal
return function()
File "/usr/lib/python3.4/site-packages/paramiko/client.py", line 251, in
retry_on_signal(lambda: sock.connect(addr))
TimeoutError: [Errno 110] Connection timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/nstat/stress_test/controller.py", line 132, in init_ssh
raise(stress_test.controller_exceptions.
stress_test.controller_exceptions.CtrlNodeConnectionError: Fail to establish ssh connection with controller node.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/nstat/stress_test/nstat.py", line 104, in
main()
File "/opt/nstat/stress_test/nstat.py", line 101, in main
nstat_test.test_selector(args)
File "/opt/nstat/stress_test/test_type.py", line 99, in test_selector
nstat_test_type_run)
File "/opt/nstat/stress_test/test_run.py", line 44, in init
json_conf)
File "/opt/nstat/stress_test/controller.py", line 77, in new
return ODL(ctrl_base_dir, test_config)
File "/opt/nstat/stress_test/controller.py", line 554, in init
self.init_ssh()
File "/opt/nstat/stress_test/controller.py", line 135, in init_ssh
self._error_handling(e.err_msg, e.err_code)
File "/opt/nstat/stress_test/controller.py", line 105, in _error_handling
raise(stress_test.controller_exceptions.CtrlError)
stress_test.controller_exceptions.CtrlError: Controller generic exception
[2018-05-14 09:49:28,362 INFO ] Run controller stop.
[2018-05-14 09:51:35,682 ERROR ] [ssh_connection_open] error: check connection object
[2018-05-14 09:51:35,682 ERROR ] Controller stop failure. :::::::::: Exception :::::::::::
[2018-05-14 09:51:35,683 ERROR ] Controller stop failure.
[2018-05-14 09:51:35,683 ERROR ] Error number:1
[2018-05-14 09:51:35,683 ERROR ] Controller stop failure. - ODL Exception: <class 'stress_test.controller_exceptions.CtrlStopError'>, 353
[2018-05-14 09:51:35,683 INFO ] Fail stopping Controller during cleanup. Exception message: Controller generic exception
[2018-05-14 09:51:35,683 INFO ] Run controller cleanup.
[2018-05-14 09:51:35,683 INFO ] [Controller] Cleaning up
The text was updated successfully, but these errors were encountered: