Hi -
I've setup up my first FreeNAS server and so far so good bar one issue I keep running into and haven't been able to resolve.
I'm running FreeNAS11.3-U4.1 on:
When I start up the VM I am able to connect to it using the noVNC straight from the VNC link in FreeNAS. I upped the resolution to 1920x1200 and have been able to access the VM just fine adding and running some software - so far so good. I made no other changes to default VNC settings.
The problem happens if I walk away for a random period of time - a few hours or more indeterminate and I am no longer able to VNC to the VM. The VM then stops.
If I restart it then it works all again just fine - until the next time.
I've tried disconnecting the VNC session first before closing the browser - and that makes no difference, nor does increasing/decreasing the CPU/RAM dedicated to the VM.
I *think* this sounds a bit like this issue in this thread here but I am not sure what the resolution is - I really do need to be able to VNC to the VM as I use it for some apps I run there.
I've looked in the logfiles for the VM and this is what I have when I reconnect (not sure why the same lines are repeated 3 times):
I'm really hoping someone can give me a steer and possibly answer some of these questions I have:
Many thanks in advance for you time - any guidance appreciated; I'm new to FreeNAS and newish to Linux - so if there's other information I need to extract please be explicit how to find it.
Regards
I've setup up my first FreeNAS server and so far so good bar one issue I keep running into and haven't been able to resolve.
I'm running FreeNAS11.3-U4.1 on:
- Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz 4 core
- 16Gb DDR4 RAM
- ASROCK B365M PRO4 Motherboard
- 3 x 2Tb WD Red disk
When I start up the VM I am able to connect to it using the noVNC straight from the VNC link in FreeNAS. I upped the resolution to 1920x1200 and have been able to access the VM just fine adding and running some software - so far so good. I made no other changes to default VNC settings.
The problem happens if I walk away for a random period of time - a few hours or more indeterminate and I am no longer able to VNC to the VM. The VM then stops.
If I restart it then it works all again just fine - until the next time.
I've tried disconnecting the VNC session first before closing the browser - and that makes no difference, nor does increasing/decreasing the CPU/RAM dedicated to the VM.
I *think* this sounds a bit like this issue in this thread here but I am not sure what the resolution is - I really do need to be able to VNC to the VM as I use it for some apps I run there.
I've looked in the logfiles for the VM and this is what I have when I reconnect (not sure why the same lines are repeated 3 times):
Code:
[2020-09-26 08:30:20,905] (DEBUG) VMService.vm_7.run():315 - Ubuntu: 26/09/2020 08:30:20 other clients: [2020-09-26 08:30:20,905] (DEBUG) VMService.vm_7.run():315 - Ubuntu: 26/09/2020 08:30:20 other clients: [2020-09-26 08:30:20,905] (DEBUG) VMService.vm_7.run():315 - Ubuntu: 26/09/2020 08:30:20 other clients: [2020-09-26 08:30:21,230] (INFO) VMService.vm_7.run():346 - ===> Error VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,230] (INFO) VMService.vm_7.run():346 - ===> Error VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,230] (INFO) VMService.vm_7.run():346 - ===> Error VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,242] (ERROR) VMService.vm_7.running():490 - ===> VMM Ubuntu is running without bhyve process. [2020-09-26 08:30:21,242] (ERROR) VMService.vm_7.running():490 - ===> VMM Ubuntu is running without bhyve process. [2020-09-26 08:30:21,242] (ERROR) VMService.vm_7.running():490 - ===> VMM Ubuntu is running without bhyve process. [2020-09-26 08:30:21,245] (DEBUG) VMService.vm_7.__teardown_guest_vmemory():376 - ===> Give back guest memory to ARC: 15235624960 [2020-09-26 08:30:21,245] (DEBUG) VMService.vm_7.__teardown_guest_vmemory():376 - ===> Give back guest memory to ARC: 15235624960 [2020-09-26 08:30:21,245] (DEBUG) VMService.vm_7.__teardown_guest_vmemory():376 - ===> Give back guest memory to ARC: 15235624960 [2020-09-26 08:30:21,246] (WARNING) VMService.vm_7.destroy_vm():353 - ===> Destroying VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,246] (WARNING) VMService.vm_7.destroy_vm():353 - ===> Destroying VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,246] (WARNING) VMService.vm_7.destroy_vm():353 - ===> Destroying VM: Ubuntu ID: 7 BHYVE_CODE: -11 [2020-09-26 08:30:21,257] (DEBUG) VMService.vm_7.kill_bhyve_web():458 - ==> Killing WEBVNC: 32559 [2020-09-26 08:30:21,257] (DEBUG) VMService.vm_7.kill_bhyve_web():458 - ==> Killing WEBVNC: 32559
I'm really hoping someone can give me a steer and possibly answer some of these questions I have:
- This feels like something or other timed out on the VM/FreeNAS - is there any other diagnostic I can check to find out?
- Is there a different type of VNC server I should use on the VM to bypass this issue?
- I've tried this with Fedora and got similar issues; any other distro I should possibly look at?
- Is this a known bug?
Many thanks in advance for you time - any guidance appreciated; I'm new to FreeNAS and newish to Linux - so if there's other information I need to extract please be explicit how to find it.
Regards