[SOLVED] Wont boot - ipcc_send_rec[1] failed: Connection refused

Joel61

Member
Dec 1, 2019
15
0
6
34
Hi

I was having issues with not been able to login to my proxmox web ui after updating my server a few months ago. So I decided I should give it a reboot. After the reboot it wont even load the web UI. I can SSH into the server, but everything seems to be broken. When I try any qm commands I get this error:
Code:
ipcc_send_rec[1] failed: Connection refused
ipcc_send_rec[2] failed: Connection refused
ipcc_send_rec[3] failed: Connection refused
Unable to load access control list: Connection refused

Running systemctl list-units --state=failed gives me:
1668154143727.png

I read somewhere that it could be to do with my hosts file, but I think its correct?
Code:
root@mothership-pve:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.149 mothership-pve.localdomain mothership-pve

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

1668154319287.png

Code:
root@mothership-pve:~# lvs
  LV                         VG      Attr       LSize    Pool Origin        Data%  Meta%  Move Log Cpy%Sync Convert
  vm-100-disk-0              M.2-SSD -wi-a-----   32.00g
  vm-100-disk-1              M.2-SSD -wi-a-----    4.00m
  vm-101-disk-0              M.2-SSD -wi-a-----   20.00g
  vm-102-disk-0              M.2-SSD -wi-a-----   32.00g
  vm-102-disk-1              M.2-SSD -wi-a-----    4.00m
  vm-103-disk-0              M.2-SSD -wi-a-----   32.00g
  vm-104-disk-0              M.2-SSD -wi-a-----  600.00g
  vm-106-disk-0              M.2-SSD -wi-a-----   32.00g
  vm-107-disk-0              M.2-SSD -wi-a-----   32.00g
  data                       pve     twi-aotz-- <338.36g                    2.26   0.61
  root                       pve     -wi-ao----   96.00g
  snap_vm-105-disk-0_Working pve     Vri---tz-k   32.00g data vm-105-disk-0
  swap                       pve     -wi-ao----    8.00g
  vm-105-disk-0              pve     Vwi-a-tz--   32.00g data               18.12
  vm-105-state-Working       pve     Vwi-a-tz--   <8.49g data               13.39

Code:
root@mothership-pve:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   32G     0   32G   0% /dev
tmpfs                 6.3G  122M  6.2G   2% /run
/dev/mapper/pve-root   94G   94G     0 100% /
tmpfs                  32G     0   32G   0% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 6.3G     0  6.3G   0% /run/user/0

I am at a loss here. I dont know what to do as all my VM's are down and I cannot start them anymore. Does anyone here in this wonderful community have any ideas?
 
Last edited:
Solved!
/dev/mapper/pve-root filled up from backups causing proxmox to blow up. manually deleting a backup from ls /var/lib/vz/dump/ and then rebooting the server fixed the issue. After freeing up some space and rebooting the UI started up and I was able to login again without any issues. After doing so I then deleted some more backups from the web UI. Everything is now working as it should.

Is there a way to prevent this from happening in the future?

I am assuming its the backups that automatically happened that killed it.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!