Problem starting nodes
Moderator: mike
-
- Posts: 10
- Joined: Sat Feb 27, 2021 4:52 am
Re: Problem starting nodes
Any ideas? The system is working perfectly outside of starting qemu nodes. I'd _really_ like to avoid having to reinstall yet again...
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Problem starting nodes
to run qemu nodes on the EVE, you must have enabled nested virtualization on your EVE CPU
Read cookbook how to deploy eve
Read cookbook how to deploy eve
-
- Posts: 10
- Joined: Sat Feb 27, 2021 4:52 am
Re: Problem starting nodes
All virtualization is enabled in the BIOS. I double checked
Also, this server has been running correctly for a year and a half without any changes
The eve-ng environment seems to be sending malformed qemu commands to start up nodes. The commands lack the full path to the VM qcow disks
Also, this server has been running correctly for a year and a half without any changes
The eve-ng environment seems to be sending malformed qemu commands to start up nodes. The commands lack the full path to the VM qcow disks
-
- Posts: 10
- Joined: Sat Feb 27, 2021 4:52 am
Re: Problem starting nodes
Any chance of more support before I give up and do a full re-install?
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Problem starting nodes
We have an EVE-NG Live support help desk, you can join using your gmail account or create new chat account using own email.
https://www.eve-ng.net/index.php/live-helpdesk/
Last thing you can try on your EVE:
https://www.eve-ng.net/index.php/live-helpdesk/
Last thing you can try on your EVE:
Code: Select all
sed -i -e '/^PrivateTmp/d' /lib/systemd/system/apache2.service
reboot
-
- Posts: 1
- Joined: Fri Jan 13, 2023 9:04 am
Re: Problem starting nodes
Any luck on this? Did removing the PrivateTmp-line from /lib/systemd/system/apache2.service help?
We seem to experience a pretty similar issue...
VPC nodes DOES start but for example Linux-nodes, vIOS-nodes, Nexus-nodes or Windows-nodes does not.
Nodes already running, when this issue started, keep running. But if they are stopped they wont start again.
Anyone knows why this is happening?
We seem to experience a pretty similar issue...
VPC nodes DOES start but for example Linux-nodes, vIOS-nodes, Nexus-nodes or Windows-nodes does not.
Nodes already running, when this issue started, keep running. But if they are stopped they wont start again.
Anyone knows why this is happening?
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Problem starting nodes
Re-install eve, rebuil all EVE packages will help
-
- Posts: 2
- Joined: Wed Apr 06, 2022 11:02 pm
Re: Problem starting nodes
Hello, I have the same issue. I can't start every qemu node. I found that it happens only when starting a node from the Web. If I start the node using unl_wrapper, it works.
example.
unl_wrapper -a start -T 1 -U user -D 1 -F "/opt/unetlab/labs/path/to/lab.unl" 2
You should change the value of -T, -D, and -F.
You can see the exact command line of unl_wrapper by reading /opt/unetlab/data/Logs/php_errors.txt
Anyway, I couldn't find a solution to this issue. Use it for the workaround.
example.
unl_wrapper -a start -T 1 -U user -D 1 -F "/opt/unetlab/labs/path/to/lab.unl" 2
You should change the value of -T, -D, and -F.
You can see the exact command line of unl_wrapper by reading /opt/unetlab/data/Logs/php_errors.txt
Anyway, I couldn't find a solution to this issue. Use it for the workaround.
-
- Posts: 5086
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Problem starting nodes
First answer you have EVE Community or EVE Pro? and which versionbinoopang wrote: ↑Tue Feb 21, 2023 1:18 amHello, I have the same issue. I can't start every qemu node. I found that it happens only when starting a node from the Web. If I start the node using unl_wrapper, it works.
example.
unl_wrapper -a start -T 1 -U user -D 1 -F "/opt/unetlab/labs/path/to/lab.unl" 2
You should change the value of -T, -D, and -F.
You can see the exact command line of unl_wrapper by reading /opt/unetlab/data/Logs/php_errors.txt
Anyway, I couldn't find a solution to this issue. Use it for the workaround.