If your Auvik collector is not booting to the interactive menu and hangs at Ubuntu finished datasource, yet the system is pingable or appears online, this suggests it's stuck during the cloud-init or early user-space phase.
Here’s how to troubleshoot and recover:
1. Gain Direct Console Access
If it's a VM, open the VM console via:
- VMware vSphere / ESXi
- Hyper-V Manager
- Proxmox / other hypervisors
For bare metal, use a physical console or IPMI/iLO/iDRAC.
2. Bypass Cloud-Init (Temporary Fix)
Once at the Ubuntu finished datasource message:
- Try pressing Ctrl+Alt+F2 or Ctrl+Alt+F1 to switch to a shell login prompt.
- If available, log in with the auvikuser.
If it logs in, cloud-init may be blocking startup. You can disable it:
sudo touch /etc/cloud/cloud-init.disabledThen reboot:
sudo reboot
3. Clear Stale Cloud-Init State
If the menu still doesn’t appear, try:
sudo cloud-init clean --logsThen reboot again.
4. Check Disk Space & Logs
Boot to a shell (via F2 or recovery mode), and check:
df -h
journalctl -xe
sudo tail -n 100 /var/log/cloud-init.logLook for any obvious errors like disk full, permission issues, or failed services.
5. Fallback: Reinstall Collector
If it’s consistently failing and non-critical, consider redeploying the collector using the current OVA or script from Auvik.
For information on managing your collectors, click here.
Before reinstalling, ensure you delete the old one. For instructions on how to do that, click here.
