IOU Devices not starting
Moderator: mike
-
- Posts: 4
- Joined: Sun Mar 26, 2017 12:40 am
IOU Devices not starting
I have setup EVE and created a simple two router one switch topology to test with. I right click on a device and start and it says started on the right but the device doesn't actually start. The error log is blank. The unl_wrapper.txt file looks something like below. Answers to some other questions you might have.
Yes, I watched the videos.
Yes, I ran the command to fix permissions.
Yes I created a license file. I have created license files for IOU before so I know how to do it.
I can view the license file using the command in your documentation cat /opt/unetlab/addons/iol/bin/iourc
running the command to test the IOU image from a terminal window is successful. I am able to start an IOU image using a set of commands like the one below. It just won't start in an actual eve webpage when I have created a topology.
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
Log file below
File output start
Mar 26 01:45:26 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:45:26 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Mar 26 01:45:20 INFO: stopping fuser -n tcp -k -TERM 32772 > /dev/null 2>&1
Mar 26 01:45:10 INFO: starting /opt/vpcsu/bin/vpcs -m 4 -N VPC -i 1 -p 32772 -e -d vunl0_4_0 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/4/wrapper.txt 2>&1 &
Mar 26 01:45:10 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/4
Mar 26 01:45:10 INFO: entering into vpcs getcommand
Mar 26 01:45:10 INFO: tunctl -u unl0 -g root -t vunl0_4_0 2>&1
Mar 26 01:45:00 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:45:00 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
Mar 26 01:45:00 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Mar 26 01:45:00 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Mar 26 01:44:59 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Mar 26 01:44:59 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Mar 26 01:34:14 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:34:14 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
Yes, I watched the videos.
Yes, I ran the command to fix permissions.
Yes I created a license file. I have created license files for IOU before so I know how to do it.
I can view the license file using the command in your documentation cat /opt/unetlab/addons/iol/bin/iourc
running the command to test the IOU image from a terminal window is successful. I am able to start an IOU image using a set of commands like the one below. It just won't start in an actual eve webpage when I have created a topology.
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
Log file below
File output start
Mar 26 01:45:26 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:45:26 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Mar 26 01:45:26 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Mar 26 01:45:20 INFO: stopping fuser -n tcp -k -TERM 32772 > /dev/null 2>&1
Mar 26 01:45:10 INFO: starting /opt/vpcsu/bin/vpcs -m 4 -N VPC -i 1 -p 32772 -e -d vunl0_4_0 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/4/wrapper.txt 2>&1 &
Mar 26 01:45:10 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/4
Mar 26 01:45:10 INFO: entering into vpcs getcommand
Mar 26 01:45:10 INFO: tunctl -u unl0 -g root -t vunl0_4_0 2>&1
Mar 26 01:45:00 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:45:00 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
Mar 26 01:45:00 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Mar 26 01:45:00 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Mar 26 01:44:59 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Mar 26 01:44:59 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Mar 26 01:34:14 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l3-adventerprisek9-15.4.1T.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1/wrapper.txt 2>&1 &
Mar 26 01:34:14 INFO: CWD is /opt/unetlab/tmp/0/35d56352-ee70-406d-af47-41572faef651/1
-
- Posts: 5176
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOU Devices not starting
IOU nodees need iourc licence sir
-
- Posts: 4
- Joined: Sun Mar 26, 2017 12:40 am
Re: IOU Devices not starting
I understand they need a license. As my post indicates I created a license, I can view the license, I can start a IOU device from the command line. I just can't start one from the web page.
-
- Posts: 5176
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: IOU Devices not starting
another thing,
fix permissions, and be sure you did clear browser chache and refresh browser.
all is in FAQ.
fix permissions, and be sure you did clear browser chache and refresh browser.
all is in FAQ.
-
- Posts: 4
- Joined: Sun Mar 26, 2017 12:40 am
Re: IOU Devices not starting
As i indicated in my original post I have done those as well.
Here again is what I have tried.
Yes, I watched the videos.
Yes, I ran the command to fix permissions.
Yes I created a license file. I have created license files for IOU before so I know how to do it.
I can view the license file using the command in your documentation cat /opt/unetlab/addons/iol/bin/iourc
running the command to test the IOU image from a terminal window is successful. I am able to start an IOU image using a set of commands like the one below. It just won't start in an actual eve webpage when I have created a topology.
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
Here again is what I have tried.
Yes, I watched the videos.
Yes, I ran the command to fix permissions.
Yes I created a license file. I have created license files for IOU before so I know how to do it.
I can view the license file using the command in your documentation cat /opt/unetlab/addons/iol/bin/iourc
running the command to test the IOU image from a terminal window is successful. I am able to start an IOU image using a set of commands like the one below. It just won't start in an actual eve webpage when I have created a topology.
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
-
- Posts: 4
- Joined: Sun Mar 26, 2017 12:40 am
Re: IOU Devices not starting
Ok. That was strange. I rebooted the host again and then it started working. I had already tried rebooting once so strange.
-
- Posts: 5
- Joined: Sun Mar 26, 2017 2:40 am
Re: IOU Devices not starting
I am having the same exact problem. I've generated the license file and implemented the permission fix, and even these commands:
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
Having absolutely no luck getting the router to turn on. The message is green that it has started. Ccie79, was it just a reboot that cleared it up? I've restarted my machine (both virtual and physical) and I'm having no luck getting the router to turn on.
cd /opt/unetlab/addons/iol/bin
touch NETMAP
LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/<iosname.bin> 1
Having absolutely no luck getting the router to turn on. The message is green that it has started. Ccie79, was it just a reboot that cleared it up? I've restarted my machine (both virtual and physical) and I'm having no luck getting the router to turn on.
-
- Posts: 5
- Joined: Sun Mar 26, 2017 2:40 am
Re: IOU Devices not starting
One thing I have noticed, and maybe this helps with troubleshooting, is that whenever I add a new node that it will always fail and give me an error message the first time I try to start it, but then supposedly succeeds each subsequent time I get start the device.
-
- Posts: 5
- Joined: Sun Mar 26, 2017 2:40 am
Re: IOU Devices not starting
Nevermind, I figured it out. My iourc file had a .txt appended at the end, and removing the extension along with reboot the VM did the trick.
-
- Posts: 9
- Joined: Sun Mar 26, 2017 3:51 pm
Re: IOU Devices not starting
Lucky you! Unfortunately, my situation still stuck in the same situation, I followed the videos, fixed the permissions, created a license, a NETMAP file and I'm able to run all my IOL images from CLI but when I attempt to run a device into the lab, it says started but nothing happens. I 've also tried with two browser and cleaned the cache. I'm running EVE version 2.0.3. Any Clue ? thanks in advance...