Hi Pavan - for the NMS VM the correct shutdown command is "SevOne-shutdown shutdown" from the command line as root. For the DI VM the regular "sudo shutdown -h now" from the CLI should work fine.
If you're finding that the VM is not coming back up cleanly then please raise a ticket with support for investigation. Note - the DI VM may take a short time (~10mins) for all the containers to start and stabilise.
Regards,
Rupert
------------------------------
Rupert Gregory
------------------------------
Original Message:
Sent: Wed January 10, 2024 11:33 PM
From: Pavan Gumireddy
Subject: SevOne VMs (both NMS and DI) shutdown hosted on AWS
We have set up our NPM and DI on AWS Techzone and we are still at POV mode so we are not required to run it regularly and only needing it as per the need basis, hence we are looking to shut down the VM and bring it up as needed. When we shutdown nthe VMs last time, the graphql pod went into CrashLoopBackoff state and the DI crashed. We resolved it by bringing the cluster down and making connection to NMS again. Is there any way that we can shutdown the VMs and bring them up again when needed without facing these type of issues.
------------------------------
Pavan Gumireddy
------------------------------