Some IOL nodes crashing after start

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
zillow32
Posts: 3
Joined: Tue Jan 30, 2018 11:51 pm

Some IOL nodes crashing after start

Post by zillow32 » Wed Jan 31, 2018 12:04 am

I have a lab with 4 IOL L2 nodes. Two of the nodes continue to work, however, the other 2 are crashing right after starting. The only differences are the crashing nodes do have a LOT of config compared to the other nodes (BGP, VRFs, Interfaces, etc). The nodes seemed to be crashing once the config was put in place, however, when starting them with No startup config they continue to crash. Not sure what's going on. I know this isn't a licensing issue as 2 nodes with the same firmware load run just fine.

Code: Select all

***** EVE-NG INFORMATION TOOL - CREATED BY R! ******
Wed Jan 31 01:58:29 EET 2018
***** EVE-NG VERSION INSTALLED  *****
eve-ng 2.0.3-86
***** HOSTNAME INFORMATION *****
   Static hostname: eve-ng
    Virtualization: vmware
  Operating System: Ubuntu 16.04.3 LTS
            Kernel: Linux 4.9.40-eve-ng-ukms-2+
      Architecture: x86-64
***** FILE SYSTEM DISK SPACE USAGE *****
Filesystem                    Size  Used Avail Use% Mounted on
udev                          9.8G     0  9.8G   0% /dev
tmpfs                         2.0G   15M  2.0G   1% /run
/dev/mapper/eve--ng--vg-root   73G   20G   50G  29% /
tmpfs                         9.9G     0  9.9G   0% /dev/shm
tmpfs                         5.0M     0  5.0M   0% /run/lock
tmpfs                         9.9G     0  9.9G   0% /sys/fs/cgroup
/dev/sda1                     472M  217M  231M  49% /boot
 ***** CPU INFORMATION  *****
model name      : Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
 ***** FREE AND USED MEMORY *****
              total        used        free      shared  buff/cache   available
Mem:            19G        473M         18G         25M        579M         18G
Swap:          6.0G          0B        6.0G
 ***** INTERFACE INFORMATION *****
pnet0           8000.000c2962ba5b       no              eth0
pnet1           8000.000000000000       no
pnet2           8000.000000000000       no
pnet3           8000.000000000000       no
pnet4           8000.000000000000       no
pnet5           8000.000000000000       no
pnet6           8000.000000000000       no
pnet7           8000.000000000000       no
pnet8           8000.000000000000       no
pnet9           8000.000000000000       no
 ***** KVM CHECK INFORMATION  *****
INFO: /dev/kvm exists
KVM acceleration can be used
 ***** APACHE STATUS  *****
● apache2.service - LSB: Apache2 web server
   Active: active (running) since Wed 2018-01-31 01:12:07 EET; 46min ago
 ***** CHECKING INERNET STATUS  *****
PING www.google.com (172.217.11.36) 56(84) bytes of data.
64 bytes from lga25s61-in-f4.1e100.net (172.217.11.36): icmp_seq=1 ttl=55 time=21.5 ms
--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 21.517/21.517/21.517/0.000 ms
root@eve-ng:/opt/unetlab/data/Logs# cat unl_wrapper.txt

Code: Select all

Jan 31 00:54:32 INFO: sysctl -w net.ipv6.conf.vunl0_15_23.disable_ipv6=1
Jan 31 00:54:32 INFO: tunctl -u unl0 -g root -t vunl0_15_39 2>&1
Jan 31 00:54:32 INFO: sysctl -w net.ipv6.conf.vunl0_15_39.disable_ipv6=1
Jan 31 00:54:32 INFO: tunctl -u unl0 -g root -t vunl0_15_55 2>&1
Jan 31 00:54:32 INFO: sysctl -w net.ipv6.conf.vunl0_15_55.disable_ipv6=1
Jan 31 00:54:32 INFO: CWD is /opt/unetlab/tmp/0/bf879c37-0a65-47a0-96be-90215439504d/15
Jan 31 00:54:32 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 15 -t "test-node-01" -F /opt/unetlab/addons/iol/bin/i86bi-linux-l2-adventerprise-15.1b.bin -d 0 -e 8 -s 0 --  -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/bf879c37-0a65-47a0-96be-90215439504d/15/wrapper.txt 2>&1 &
root@eve-ng:/opt/unetlab/data/Logs# cat /opt/unetlab/tmp/0/bf879c37-0a65-47a0-96be-90215439504d/15/wrapper.txt

Code: Select all

30/0 23:54:32.397 INF   Tennant_id = 0
30/0 23:54:32.397 INF   Device_id = 15
30/0 23:54:32.397 INF   NETMAP file created.
30/0 23:54:32.397 INF   TS configured.
30/0 23:54:32.397 INF   TAP interface configured (s=8, n=vunl0_15_0).
30/0 23:54:32.397 INF   TAP interface configured (s=10, n=vunl0_15_16).
30/0 23:54:32.397 INF   TAP interface configured (s=12, n=vunl0_15_32).
30/0 23:54:32.397 INF   TAP interface configured (s=14, n=vunl0_15_48).
30/0 23:54:32.397 INF   TAP interface configured (s=16, n=vunl0_15_1).
30/0 23:54:32.397 INF   TAP interface configured (s=18, n=vunl0_15_17).
30/0 23:54:32.397 INF   TAP interface configured (s=20, n=vunl0_15_33).
30/0 23:54:32.397 INF   TAP interface configured (s=22, n=vunl0_15_49).
30/0 23:54:32.397 INF   TAP interface configured (s=24, n=vunl0_15_2).
30/0 23:54:32.398 INF   TAP interface configured (s=26, n=vunl0_15_18).
30/0 23:54:32.398 INF   TAP interface configured (s=28, n=vunl0_15_34).
30/0 23:54:32.398 INF   TAP interface configured (s=30, n=vunl0_15_50).
30/0 23:54:32.398 INF   TAP interface configured (s=32, n=vunl0_15_3).
30/0 23:54:32.398 INF   TAP interface configured (s=34, n=vunl0_15_19).
30/0 23:54:32.398 INF   TAP interface configured (s=36, n=vunl0_15_35).
30/0 23:54:32.398 INF   TAP interface configured (s=38, n=vunl0_15_51).
30/0 23:54:32.398 INF   TAP interface configured (s=40, n=vunl0_15_4).
30/0 23:54:32.398 INF   TAP interface configured (s=42, n=vunl0_15_20).
30/0 23:54:32.398 INF   TAP interface configured (s=44, n=vunl0_15_36).
30/0 23:54:32.398 INF   TAP interface configured (s=46, n=vunl0_15_52).
30/0 23:54:32.398 INF   TAP interface configured (s=48, n=vunl0_15_5).
30/0 23:54:32.398 INF   TAP interface configured (s=50, n=vunl0_15_21).
30/0 23:54:32.398 INF   TAP interface configured (s=52, n=vunl0_15_37).
30/0 23:54:32.398 INF   TAP interface configured (s=54, n=vunl0_15_53).
30/0 23:54:32.398 INF   TAP interface configured (s=56, n=vunl0_15_6).
30/0 23:54:32.398 INF   TAP interface configured (s=58, n=vunl0_15_22).
30/0 23:54:32.398 INF   TAP interface configured (s=60, n=vunl0_15_38).
30/0 23:54:32.398 INF   TAP interface configured (s=62, n=vunl0_15_54).
30/0 23:54:32.398 INF   TAP interface configured (s=64, n=vunl0_15_7).
30/0 23:54:32.398 INF   TAP interface configured (s=66, n=vunl0_15_23).
30/0 23:54:32.398 INF   TAP interface configured (s=68, n=vunl0_15_39).
30/0 23:54:32.398 INF   TAP interface configured (s=70, n=vunl0_15_55).
30/0 23:54:32.398 INF   Adding subprocess stdout descriptor (5).
30/0 23:54:32.398 INF   Adding telnet socket descriptor (7).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (8).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (16).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (24).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (32).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (40).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (48).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (56).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (64).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (10).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (18).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (26).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (34).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (42).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (50).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (58).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (66).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (12).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (20).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (28).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (36).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (44).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (52).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (60).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (68).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (14).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (22).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (30).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (38).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (46).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (54).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (62).
30/0 23:54:32.398 INF   Adding TAP interface descriptor (70).
30/0 23:54:35.399 ERR   Error while connecting local AF_UNIX: Connection refused (2)
30/0 23:54:35.399 ERR   Cannot listen at AF_UNIX (240). ERR: Cannot open AF_UNIX sockets (2).
30/0 23:54:35.399 ERR   Failed to create AF_UNIX socket file (2).
30/0 23:54:35.399 INF   Caught SIGTERM, killing child.
30/0 23:54:35.399 INF   Child is no more running.
This is as far as I've been able to track the issue down so I'm hoping for some direction on the following errors.
30/0 23:54:35.399 ERR Error while connecting local AF_UNIX: Connection refused (2)
30/0 23:54:35.399 ERR Cannot listen at AF_UNIX (240). ERR: Cannot open AF_UNIX sockets (2).
30/0 23:54:35.399 ERR Failed to create AF_UNIX socket file (2).

Thanks!
Top
Uldis (UD)
Posts: 5182
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:
Contact Uldis (UD)

Re: Some IOL nodes crashing after start

Post by Uldis (UD) » Wed Jan 31, 2018 7:25 pm

Try other image and give more RAM.
Like 2048 for L2

But it is image issue..
Some older IOL were very unstable and sensible for heavy configs, specially VRFs
Top
zillow32
Posts: 3
Joined: Tue Jan 30, 2018 11:51 pm

Re: Some IOL nodes crashing after start

Post by zillow32 » Thu Feb 01, 2018 3:18 am

Will give the more ram a try. Is there a newer more stable L2 image you recommend?
Top
Uldis (UD)
Posts: 5182
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:
Contact Uldis (UD)

Re: Some IOL nodes crashing after start

Post by Uldis (UD) » Thu Feb 01, 2018 9:31 am

YES, L2 IRON from 09 Aug, 2017 is very good
search arround, google

Here is not allowed share anything like images...

UD
Top
zillow32
Posts: 3
Joined: Tue Jan 30, 2018 11:51 pm

Re: Some IOL nodes crashing after start

Post by zillow32 » Fri Feb 02, 2018 1:04 pm

No crashing with the same config on high iron. Thanks!
Top
dennis_alfaris
Posts: 1
Joined: Sat Apr 19, 2025 10:29 am

Re: Some IOL nodes crashing after start

Post by dennis_alfaris » Sun Apr 20, 2025 3:41 pm

Hi

I have kind of similar issue. After setting up the eve-ng as vm in esxi and i put the iol images and licenses in the correct path. But iol are stopping immmediatly after starting.
Top
debugnetiq1
Posts: 8
Joined: Sun Sep 10, 2017 11:22 pm

Re: Some IOL nodes crashing after start

Post by debugnetiq1 » Sat Jul 05, 2025 9:06 pm

Hi everyone. I am facing same issue but imho it is not related to the image itself but maybe to the unl_wrapper.
Testing with recommended images
L2/L3 Switch
- i86bi_linux_l2-adventerprisek9-ms.SSA.high_iron_20190423.bin (IOS 15.2 adventerprise)
- i86bi_LinuxL2-AdvEnterpriseK9-M_152_May_2018.bin (IOS 15.2 adventerprise)
L3 router
- i86bi_LinuxL3-AdvEnterpriseK9-M2_157_3_May_2018.bin (IOS 15.7 adventerprise)
L3 XE Router
- x86_64_crb_linux-adventerprisek9-ms.bin (IOS-XE 17.12.1 adventerprise)
L2/L3 XE Switch
- x86_64_crb_linux_l2-adventerprisek9-ms.bin (IOS-XE 17.12.1 adventerprise)

Initially on EVE-NG 6.2 the L3 XE Router is the only image not dying with this error after a couple of seconds. All other give that AF_UNIX connect error.
Then moving to an older EVE-NG 2.0.77 with same images
On this one the L2/L3 Switch and L3 Router start fine
Instead both L3 XE Router and L2/L3 XE Switch die with the same error
root@EVE-NG-203-77:/opt/unetlab#
root@EVE-NG-203-77:/opt/unetlab/tmp/0/c62b3ddf-5c8d-4c30-995e-2e6eae4071d5/5# cat wrapper.txt
5/6 20:49:12.889 INF Tennant_id = 0
5/6 20:49:12.889 INF Device_id = 5
5/6 20:49:12.889 INF NETMAP file created.
5/6 20:49:12.889 INF TS configured.
5/6 20:49:12.890 INF TAP interface configured (s=8, n=vunl0_5_0).
5/6 20:49:12.890 INF TAP interface configured (s=10, n=vunl0_5_16).
5/6 20:49:12.890 INF TAP interface configured (s=12, n=vunl0_5_32).
5/6 20:49:12.890 INF TAP interface configured (s=14, n=vunl0_5_48).
5/6 20:49:12.890 INF Adding subprocess stdout descriptor (5).
5/6 20:49:12.890 INF Adding telnet socket descriptor (7).
5/6 20:49:12.890 INF Adding TAP interface descriptor (8).
5/6 20:49:12.890 INF Adding TAP interface descriptor (10).
5/6 20:49:12.890 INF Adding TAP interface descriptor (12).
5/6 20:49:12.890 INF Adding TAP interface descriptor (14).
5/6 20:49:15.890 ERR Error while connecting local AF_UNIX: No such file or directory (2)
5/6 20:49:15.890 ERR Cannot listen at AF_UNIX (80). ERR: Cannot open AF_UNIX sockets (2).
5/6 20:49:15.890 ERR Failed to create AF_UNIX socket file (2).
5/6 20:49:15.890 INF Caught SIGTERM, killing child.
5/6 20:49:15.890 INF Child is no more running.
Top
rusty725
Posts: 368
Joined: Thu Mar 29, 2018 4:19 pm

Re: Some IOL nodes crashing after start

Post by rusty725 » Sat Jul 05, 2025 10:37 pm

debugnetiq1 wrote: ↑
Sat Jul 05, 2025 9:06 pm
 Hi everyone. I am facing same issue but imho it is not related to the image itself but maybe to the unl_wrapper.
Testing with recommended images
L2/L3 Switch
- i86bi_linux_l2-adventerprisek9-ms.SSA.high_iron_20190423.bin (IOS 15.2 adventerprise)
- i86bi_LinuxL2-AdvEnterpriseK9-M_152_May_2018.bin (IOS 15.2 adventerprise)
L3 router
- i86bi_LinuxL3-AdvEnterpriseK9-M2_157_3_May_2018.bin (IOS 15.7 adventerprise)
L3 XE Router
- x86_64_crb_linux-adventerprisek9-ms.bin (IOS-XE 17.12.1 adventerprise)
L2/L3 XE Switch
- x86_64_crb_linux_l2-adventerprisek9-ms.bin (IOS-XE 17.12.1 adventerprise)

Initially on EVE-NG 6.2 the L3 XE Router is the only image not dying with this error after a couple of seconds. All other give that AF_UNIX connect error.
Then moving to an older EVE-NG 2.0.77 with same images
On this one the L2/L3 Switch and L3 Router start fine
Instead both L3 XE Router and L2/L3 XE Switch die with the same error
root@EVE-NG-203-77:/opt/unetlab#
root@EVE-NG-203-77:/opt/unetlab/tmp/0/c62b3ddf-5c8d-4c30-995e-2e6eae4071d5/5# cat wrapper.txt
5/6 20:49:12.889 INF Tennant_id = 0
5/6 20:49:12.889 INF Device_id = 5
5/6 20:49:12.889 INF NETMAP file created.
5/6 20:49:12.889 INF TS configured.
5/6 20:49:12.890 INF TAP interface configured (s=8, n=vunl0_5_0).
5/6 20:49:12.890 INF TAP interface configured (s=10, n=vunl0_5_16).
5/6 20:49:12.890 INF TAP interface configured (s=12, n=vunl0_5_32).
5/6 20:49:12.890 INF TAP interface configured (s=14, n=vunl0_5_48).
5/6 20:49:12.890 INF Adding subprocess stdout descriptor (5).
5/6 20:49:12.890 INF Adding telnet socket descriptor (7).
5/6 20:49:12.890 INF Adding TAP interface descriptor (8).
5/6 20:49:12.890 INF Adding TAP interface descriptor (10).
5/6 20:49:12.890 INF Adding TAP interface descriptor (12).
5/6 20:49:12.890 INF Adding TAP interface descriptor (14).
5/6 20:49:15.890 ERR Error while connecting local AF_UNIX: No such file or directory (2)
5/6 20:49:15.890 ERR Cannot listen at AF_UNIX (80). ERR: Cannot open AF_UNIX sockets (2).
5/6 20:49:15.890 ERR Failed to create AF_UNIX socket file (2).
5/6 20:49:15.890 INF Caught SIGTERM, killing child.
5/6 20:49:15.890 INF Child is no more running.
Which Eve version ? How many cores and ram assigned. Some your nodes are old and have bugs.
Top
debugnetiq1
Posts: 8
Joined: Sun Sep 10, 2017 11:22 pm

Re: Some IOL nodes crashing after start

Post by debugnetiq1 » Sun Jul 06, 2025 12:40 am

Rather then blindly trying in the dark (cpu, memory, CPU flags, etc) is there a way to obtain more information on the actual root cause?
This would greatly help

As per the template in eve-ng 6.2 (1MB NVRAM, 1MB RAM). The EVE-NG server itself has 8 cores and 32GB RAM.
In fact I suspect the iol_wrapper (which is an ELF binary). The top-level folder for the pipes is visibly created in /tmp once the 1'st image is launched: /tmp/netio32768. Not sure the pipe should be created under this folder.
root@eve-ng-63-ce:/opt/unetlab/data/Logs# ls -l /tmp/netio32768
total 0
root@eve-ng-63-ce:/opt/unetlab/data/Logs#
this is visible in /opt/unetlab/data/Logs/unl_wrapper.txt
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_0.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_16.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_32.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_48.disable_ipv6=1
Jul 06 02:08:49 INFO: CWD is /opt/unetlab/tmp/0/5a27f9d0-fba5-4ca6-acf5-076c7d69d781/1
Jul 06 02:08:49 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "SW1-L2-SSA-HI-AE" -F /opt/unetlab/addons/iol/bin/i86bi_Linux-L2-Adventerprisek9-ms.SSA.high_iron_20190423.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/5a27f9d0-fba5-4ca6-acf5-076c7d69d781/1/wrapper.txt 2>&1 &

The error in wrapper.txt does not give much detail on what file is missing
6/6 0:8:52.186 ERR Error while connecting local AF_UNIX: No such file or directory (2)
6/6 0:8:52.186 ERR Cannot listen at AF_UNIX (16). ERR: Cannot open AF_UNIX sockets (2).
6/6 0:8:52.186 ERR Failed to create AF_UNIX socket file (2).
6/6 0:8:52.186 INF Caught SIGTERM, killing child.
6/6 0:8:52.186 INF Child is no more running.

Not sure whether relevant but replacing in 6.2 the original iol_wrapper with the one from 2.0.77 gives the same error although on 2.0.77 the same image runs fine . The XE images on 2.0.77 stop after a few seconds with the same AF_UNIX error
6/6 0:33:54.493 INF Tennant_id = 0
6/6 0:33:54.493 INF Device_id = 4
6/6 0:33:54.493 INF NETMAP file created.
6/6 0:33:54.493 INF TS configured.
6/6 0:33:54.493 INF TAP interface configured (s=8, n=vunl0_4_0).
6/6 0:33:54.493 INF TAP interface configured (s=10, n=vunl0_4_16).
6/6 0:33:54.493 INF TAP interface configured (s=12, n=vunl0_4_32).
6/6 0:33:54.493 INF TAP interface configured (s=14, n=vunl0_4_48).
6/6 0:33:54.493 INF Adding subprocess stdout descriptor (5).
6/6 0:33:54.493 INF Adding telnet socket descriptor (7).
6/6 0:33:54.493 INF Adding TAP interface descriptor (8).
6/6 0:33:54.493 INF Adding TAP interface descriptor (10).
6/6 0:33:54.493 INF Adding TAP interface descriptor (12).
6/6 0:33:54.493 INF Adding TAP interface descriptor (14).
6/6 0:33:57.493 ERR Error while connecting local AF_UNIX: No such file or directory (2)
6/6 0:33:57.493 ERR Cannot listen at AF_UNIX (64). ERR: Cannot open AF_UNIX sockets (2).
6/6 0:33:57.493 ERR Failed to create AF_UNIX socket file (2).
6/6 0:33:57.493 INF Caught SIGTERM, killing child.
6/6 0:33:57.493 INF Child is no more running.
You do not have the required permissions to view the files attached to this post.
Top
rusty725
Posts: 368
Joined: Thu Mar 29, 2018 4:19 pm

Re: Some IOL nodes crashing after start

Post by rusty725 » Sun Jul 06, 2025 2:28 am

debugnetiq1 wrote: ↑
Sun Jul 06, 2025 12:40 am
 Rather then blindly trying in the dark (cpu, memory, CPU flags, etc) is there a way to obtain more information on the actual root cause?
This would greatly help

As per the template in eve-ng 6.2 (1MB NVRAM, 1MB RAM). The EVE-NG server itself has 8 cores and 32GB RAM.
In fact I suspect the iol_wrapper (which is an ELF binary). The top-level folder for the pipes is visibly created in /tmp once the 1'st image is launched: /tmp/netio32768. Not sure the pipe should be created under this folder.
root@eve-ng-63-ce:/opt/unetlab/data/Logs# ls -l /tmp/netio32768
total 0
root@eve-ng-63-ce:/opt/unetlab/data/Logs#
this is visible in /opt/unetlab/data/Logs/unl_wrapper.txt
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_0.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_16 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_16.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_32 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_32.disable_ipv6=1
Jul 06 02:08:49 INFO: tunctl -u unl0 -g root -t vunl0_1_48 2>&1
Jul 06 02:08:49 INFO: sysctl -w net.ipv6.conf.vunl0_1_48.disable_ipv6=1
Jul 06 02:08:49 INFO: CWD is /opt/unetlab/tmp/0/5a27f9d0-fba5-4ca6-acf5-076c7d69d781/1
Jul 06 02:08:49 INFO: starting /opt/unetlab/wrappers/iol_wrapper -T 0 -D 1 -t "SW1-L2-SSA-HI-AE" -F /opt/unetlab/addons/iol/bin/i86bi_Linux-L2-Adventerprisek9-ms.SSA.high_iron_20190423.bin -d 0 -e 1 -s 0 -- -n 1024 -q -m 1024 > /opt/unetlab/tmp/0/5a27f9d0-fba5-4ca6-acf5-076c7d69d781/1/wrapper.txt 2>&1 &

The error in wrapper.txt does not give much detail on what file is missing
6/6 0:8:52.186 ERR Error while connecting local AF_UNIX: No such file or directory (2)
6/6 0:8:52.186 ERR Cannot listen at AF_UNIX (16). ERR: Cannot open AF_UNIX sockets (2).
6/6 0:8:52.186 ERR Failed to create AF_UNIX socket file (2).
6/6 0:8:52.186 INF Caught SIGTERM, killing child.
6/6 0:8:52.186 INF Child is no more running.

Not sure whether relevant but replacing in 6.2 the original iol_wrapper with the one from 2.0.77 gives the same error although on 2.0.77 the same image runs fine . The XE images on 2.0.77 stop after a few seconds with the same AF_UNIX error
6/6 0:33:54.493 INF Tennant_id = 0
6/6 0:33:54.493 INF Device_id = 4
6/6 0:33:54.493 INF NETMAP file created.
6/6 0:33:54.493 INF TS configured.
6/6 0:33:54.493 INF TAP interface configured (s=8, n=vunl0_4_0).
6/6 0:33:54.493 INF TAP interface configured (s=10, n=vunl0_4_16).
6/6 0:33:54.493 INF TAP interface configured (s=12, n=vunl0_4_32).
6/6 0:33:54.493 INF TAP interface configured (s=14, n=vunl0_4_48).
6/6 0:33:54.493 INF Adding subprocess stdout descriptor (5).
6/6 0:33:54.493 INF Adding telnet socket descriptor (7).
6/6 0:33:54.493 INF Adding TAP interface descriptor (8).
6/6 0:33:54.493 INF Adding TAP interface descriptor (10).
6/6 0:33:54.493 INF Adding TAP interface descriptor (12).
6/6 0:33:54.493 INF Adding TAP interface descriptor (14).
6/6 0:33:57.493 ERR Error while connecting local AF_UNIX: No such file or directory (2)
6/6 0:33:57.493 ERR Cannot listen at AF_UNIX (64). ERR: Cannot open AF_UNIX sockets (2).
6/6 0:33:57.493 ERR Failed to create AF_UNIX socket file (2).
6/6 0:33:57.493 INF Caught SIGTERM, killing child.
6/6 0:33:57.493 INF Child is no more running.
come to our chat https://webchat.eve-ng.net/ and give me anydesk id so I can connect to you and check
Top
Post Reply

Return to “EVE-NG Help-Desk”