apwiggins
Dabbler
- Joined
- Dec 23, 2016
- Messages
- 41
I'm seeing behavior similar to this link on my server (Xeon E5-2620 v4 @ 2.10GHz (16 cores):
https://www.reddit.com/r/freenas/comments/8zkcva/112_why_are_my_vms_stopping/
I have an entirely new Rancher VM created in FreeNAS-11.2-U4.1. It runs and I've been able to add Docker containers, including an OwnCloud website for file-hosting.
After some period of time, the OwnCloud instance was disappearing, so http://xx.xx.xx.210:80 returned nothing and the RancherUI interface also returned nothing (http://xx.xx.xx.210:8080). Investigating further, the RancherVM when pinged (xx.xx.xx.210), was unreachable. Using the Docker web interface, the Virtual Machine instance was accessed via web interface Serial option (it invokes cu -l /dev/nmdm11B) to access the Rancher VM. The CLI popped up quickly. Pings to the RancherVM (xx.xx.xx.210) started immediately and the OwnCloud website (http://xx.xx.xx.210:80) content appeared. This exhibits all the behavior of a pause rather than a restart.
Why does the RancherVM pause on its own? A parallel UbuntuVM hosting a gitlab instance (xx.xx.xx.211) created on the same machine doesn't pause like this, ever.
A clue from the logs could be the following:
May 27 22:09:54 freenas kernel: tap1: link state changed to DOWN
May 27 22:09:54 freenas kernel: tap1: link state changed to DOWN
May 27 22:11:02 freenas tap1: Ethernet address: 00:xx:xx:xx:07:01
May 27 22:11:02 freenas kernel: tap1: promiscuous mode enabled
May 27 22:11:04 freenas kernel: tap1: link state changed to UP
May 27 22:11:04 freenas kernel: tap1: link state changed to UP
The tap1 interface MAC doesn't match the RancherVM NIC MAC (00:xx:xx:xx:E7:39), but maybe the VM's NIC talks to the tap1 interface on the host?
https://www.reddit.com/r/freenas/comments/8zkcva/112_why_are_my_vms_stopping/
I have an entirely new Rancher VM created in FreeNAS-11.2-U4.1. It runs and I've been able to add Docker containers, including an OwnCloud website for file-hosting.
After some period of time, the OwnCloud instance was disappearing, so http://xx.xx.xx.210:80 returned nothing and the RancherUI interface also returned nothing (http://xx.xx.xx.210:8080). Investigating further, the RancherVM when pinged (xx.xx.xx.210), was unreachable. Using the Docker web interface, the Virtual Machine instance was accessed via web interface Serial option (it invokes cu -l /dev/nmdm11B) to access the Rancher VM. The CLI popped up quickly. Pings to the RancherVM (xx.xx.xx.210) started immediately and the OwnCloud website (http://xx.xx.xx.210:80) content appeared. This exhibits all the behavior of a pause rather than a restart.
Why does the RancherVM pause on its own? A parallel UbuntuVM hosting a gitlab instance (xx.xx.xx.211) created on the same machine doesn't pause like this, ever.
A clue from the logs could be the following:
May 27 22:09:54 freenas kernel: tap1: link state changed to DOWN
May 27 22:09:54 freenas kernel: tap1: link state changed to DOWN
May 27 22:11:02 freenas tap1: Ethernet address: 00:xx:xx:xx:07:01
May 27 22:11:02 freenas kernel: tap1: promiscuous mode enabled
May 27 22:11:04 freenas kernel: tap1: link state changed to UP
May 27 22:11:04 freenas kernel: tap1: link state changed to UP
The tap1 interface MAC doesn't match the RancherVM NIC MAC (00:xx:xx:xx:E7:39), but maybe the VM's NIC talks to the tap1 interface on the host?