Support and News Forum

Hi,

I have the latest version of Eve-NG (2.0.3-77) installed and I have some IOU/IOL images in /opt/unetlab/addons/iol/bin/. I have iourc file in the same location

When I tried to start the node in GUI, I get the notification that the has been started. However the icon doesn't change and the node doesn't start either.

Digging a little deeper, I found the following error message in wrapper.txt log file

root@eve-ng:/opt/unetlab/data/Logs# tail /opt/unetlab/tmp/0/48f00314-8903-4a7c-b405-06540bae7dc9/1/wrapper.txt
27/7 7:4:23.208 ERR File 'iourc' does not exist.

But...

When I run this in the IOL bin directory, it seems to get start the node perfectly, and I can connect to the router's console. I just can't seem to start any IOL node from the web interface.

root@eve-ng:/opt/unetlab/addons/iol/bin# pwd
/opt/unetlab/addons/iol/bin
root@eve-ng:/opt/unetlab/addons/iol/bin# /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "R1" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l2-adventerprise-15.1b.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024
27/7 7:11:17.965 INF Tennant_id = 0
27/7 7:11:17.966 INF Device_id = 1
27/7 7:11:17.966 INF NETMAP file created.
27/7 7:11:17.966 INF TS configured.
27/7 7:11:17.966 INF TAP interface configured (s=8, n=vunl0_1_0).
27/7 7:11:17.967 INF TAP interface configured (s=10, n=vunl0_1_16).
27/7 7:11:17.967 INF TAP interface configured (s=12, n=vunl0_1_32).
27/7 7:11:17.968 INF TAP interface configured (s=14, n=vunl0_1_48).
27/7 7:11:17.968 INF Adding subprocess stdout descriptor (5).
27/7 7:11:17.969 INF Adding telnet socket descriptor (7).
27/7 7:11:17.969 INF Adding TAP interface descriptor (8).
27/7 7:11:17.969 INF Adding TAP interface descriptor (10).
27/7 7:11:17.970 INF Adding TAP interface descriptor (12).
27/7 7:11:17.970 INF Starting child (LD_LIBRARY_PATH=/opt/unetlab/addons/iol/lib /opt/unetlab/addons/iol/bin/i86bi-linux-l2-adventerprise-15.1b.bin -e 1 -s 0 -n 1024 -q -m 1024 16).
27/7 7:11:17.970 INF Adding TAP interface descriptor (14).
27/7 7:11:20.970 INF Local (6) and remote (3) AF_UNIX are configured.
27/7 7:11:20.970 INF Adding wrapper socket descriptor (6).

wrong iourc file or not fixed permisions for it..

Uldis (UD) wrote: ↑

Sun Aug 27, 2017 9:47 pm

wrong iourc file or not fixed permisions for it..

I am able to start the image files in CLI with the following commands (Dont think I can do that if iourc file is wrong?)
As for the permission, I have those fixed with /opt/unetlab/wrappers/unl_wrapper -a fixpermissions

And the iourc file itself has read permission by group, user and public

Hi,

I have the same error condition as senses0 using eve-ng 2.0.3-77

I’ve created & re-created the iourc file & fixed the permissions

I can also start all my iol images from the command line.

I just can’t get the devices to start from the GUI interface although it says it has started.


I have these images running & working in my UNETLAB VM, so I am familiar with the process of setting up from scratch
but I’m a bit lost as to what my next move should be?

Anyone else had this error & solved it??

what is senses0
??

The username of the original post

be sure that your iol images are fixed permissions...check by file!!
and if you say can't starti from gui, then its your browser issue!

Thanks for the reply Uldis..

I seem have resolved the error by re-creating the iourc file.

I think the problem I had was conflicting notes that I had from Unetlab on creating the iourc file

(1) /opt/unetlab/addons/iol/bin/iourc

and

(2) /opt/unetlab/addons/iol/bin/.iourc


Number 1 above seems to have done the trick

iourc file must have your present EVE hostname, thats why UNL one didnt work