-
Notifications
You must be signed in to change notification settings - Fork 405
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
IOU VM "IOU1" process has stopped with return code: -6 (IOU L2 v17.12.1) #868
Comments
Running on VMware ESXi Server version 2.2.46 |
Maybe more RAM is needed? @Desposyni do you know? |
I've tried 256MB, 512MB , 768MB and 1028MB. Same result. The layer 3 (router) image of the same version number works fine with 256 MB. |
It's not the RAM, the L2-IOU only consumes around 150MB when idle, and as long as the 'use default memory' is checked the IOU file will choose to use 768MB as its max. It's something with the GNS3 VM. The L2-IOU works with Mint and Pop!_OS. Not sure if it's the kernel or something else within the distro. |
I've built a new GNS3 VM using Ubuntu 22.04.04 (fully updated) and GNS3 Server 2.2.46 and the image boots fine. sysadmin@gns3vm:~$ gns3server |
Not sure what happened, return code -6 means that the IOU process failed with SIGABRT. I don't think we can do anything about it. @Zero3Dash should we close this issue? |
@grossmj It runs fine on 22.04.04, but fails with the -6 error code on 20.04.04. Which would indicate its something within the Linux Distro. If it's not something that will be fix in the here and now, but later when the distro gets upgraded. Then, it might be worth including in the appliance file that the version IOU L2 v17.12.1 will only successfully run on GNS3 running 22.04.04 and possible higher.. I'm happy for you to close it, btw. |
Hey guys, @Zero3Dash @grossmj |
@Arash88 What I did was to create a new VM using Ubuntu Server 22.04 ISO, then manually installed GNS3 2.2.46, using the following guide. |
closed |
I'm using a GNS3 server running directly on Debian 12 (Bookworm) and I had the same issue. I could resolve it by commenting/deleting the Then I tested the GNS3VM (based on Ubuntu 20.04/focal). Also here the issue was resolved by removing the So it is not necessary to switch to a new OS. |
@Arash88 please try the suggestion above and let me know if it works for you. |
@grossmj On and unrelated note, I've also notice in the 17.12.1 base startup config file, "no ip domain-lookup" should be "no ip domain lookup" |
|
Thanks @grossmj, chmod and chown helped me edit it.
|
I have created this PR GNS3/gns3-server#2366 |
@grossmj What about removing scripts/provision.sh
|
I am considering it. I haven't removed it yet because the problem only affects Ubuntu Focal, so only older GNS3 VMs. For future releases, should we block xml.cisco.com using iptables instead or totally remove any blocking? |
Just tested the GNSVM image
I'm not sure. The iputils command blocks the DNS request to xml.cisco.com, so that a DNS lookup to that address will time out. That may slow down the IOU startup, but I haven't noticed a delay. If jammy doesn't show the issue, I won't add the iputils command. The xml.cisco.com entry in /etc/hosts should be sufficient. |
That's right, I forgot 2.2.x still uses Ubuntu Focal and 3.x uses Jammy. I think I will just remove xml.cisco.com from the hosts file and not mess with iptables. |
https://github.com/GNS3/gns3-registry/blob/master/appliances/cisco-iou-l2.gns3a
The Cisco IOU L2 image (IOU L2 v17.12.1) for x86_64_crb_linux_l2-adventerprisek9-ms presents IOU VM "IOU1" process has stopped with return code: -6 when attempting to run with the default options.
The text was updated successfully, but these errors were encountered: