Our Debian 64 bit VM crashed after an update was applied to our 3CX VOIP Phone system.
The attachments below are the details that we have been able to ascertain so far.
Has anyone any idea of what the problem might be and how we can possibly resolve it for the future?
We have no knowledge of this operating system, so any help would be much appreciated.
Also, is it possible to monitor for this type of event and then notify/email someone that an event has taken place?
Thanks.
VirtualBox Crashed after update was applied to 3CX
VirtualBox Crashed after update was applied to 3CX
- Attachments
-
- VBox.log.txt.7z
- This was the log file saved after restarting the VM later that day
- (41.85 KiB) Downloaded 11 times
-
- This was the png file created at the time of the crash
- VBox.png (36.61 KiB) Viewed 667 times
-
- This was the error received from the crash.
- IMG-20200927-WA0008.jpg (119.22 KiB) Viewed 667 times
-
scottgus1
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VirtualBox Crashed after update was applied to 3CX
This guest started from a saved state:
I would recommend not save-stating the guest. Find out how that happened and change it to a full shutdown. If the save-state was part of a power-failure script, ensure the host has enough backup power time to do complete shutdowns, and have the script order a shut-down of the guest.
Virtualbox does not have a send-an-email monitoring system. You can script a loop with 'vboxmanage showvminfo "vm name" ' redirected into a find/grep that looks for the 'state:' line to tell if the guest is running or not, and send an email from a 3rd-party program depending on the guest state.
It ran for almost 9 days then was reset, can't tell if from inside the OS, or from the Virtualbox controls:00:00:06.469118 Console: Machine state changed to 'Restoring'
It then rebooted and guru-meditated on a Triple Fault, meaning something really went wrong and Virtualbox couldn't figure out how to recover.211:10:59.696601 ACPI: Reset initiated by ACPI
211:10:59.708535 Changing the VM state from 'RUNNING' to 'RESETTING'
I would recommend not save-stating the guest. Find out how that happened and change it to a full shutdown. If the save-state was part of a power-failure script, ensure the host has enough backup power time to do complete shutdowns, and have the script order a shut-down of the guest.
Virtualbox does not have a send-an-email monitoring system. You can script a loop with 'vboxmanage showvminfo "vm name" ' redirected into a find/grep that looks for the 'state:' line to tell if the guest is running or not, and send an email from a 3rd-party program depending on the guest state.