When vic-admin is not answering, then the customer will need to enable ssh and ssh in and manually collect the logs. We should have an option for vic-machine debug that will login to the vch, collect the logs.
Work around for now is the enable ssh with vic-machine debug and then capture the logs with scp -r to the VCH.
When vic-admin is not answering, then the customer will need to enable ssh and ssh in and manually collect the logs. We should have an option for vic-machine debug that will login to the vch, collect the logs.
Work around for now is the enable ssh with vic-machine debug and then capture the logs with scp -r to the VCH.