pvedaemon start failed - unable to create socket - Address already in use

[Ovidiu]

This is a single host, no cluster, nothing complicated. The problem arose after creating a new LXC I tried starting it and it just hung so I refreshed the GUI and realized the GUI was showing everything as offline. I had this before so I attempted the steps that "fixed" it last time.I had a problem with a stale nfs share, again, so as per this thread: https://forum.proxmox.com/threads/2...-Connection-error-Timeout?p=124841#post124841 I tried to do a service pvedaemon restart and got:Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.root@james:~# systemctl status pvedaemon.service● pvedaemon.service - PVE API Daemon Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled) Active: failed (Result: exit-code) since Sun 2015-12-06 22:47:42 CET; 10s ago Process: 25178 ExecStop=/usr/bin/pvedaemon stop (code=exited, status=0/SUCCESS) Process: 4170 ExecStart=/usr/bin/pvedaemon start (code=exited, status=255) Main PID: 26362 (code=exited, status=0/SUCCESS)Dec 06 22:47:42 james pvedaemon[4170]: start failed - unable to create socket - Address already in use
Dec 06 22:47:42 james pvedaemon[4170]: start failed - unable to create socket - Address already in use
Dec 06 22:47:42 james systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Dec 06 22:47:42 james systemd[1]: Failed to start PVE API Daemon.
Dec 06 22:47:42 james systemd[1]: Unit pvedaemon.service entered failed state.cat /var/log/syslog
Dec 6 22:47:42 james pvedaemon[4170]: start failed - unable to create socket - Address already in use
Dec 6 22:47:42 james pvedaemon[4170]: start failed - unable to create socket - Address already in use
Dec 6 22:47:42 james systemd[1]: pvedaemon.service: control process exited, code=exited status=255
Dec 6 22:47:42 james systemd[1]: Failed to start PVE API Daemon.
Dec 6 22:47:42 james systemd[1]: Unit pvedaemon.service entered failed state.

root@james:~# pveversion -v
proxmox-ve: 4.0-22 (running kernel: 4.2.3-2-pve)
pve-manager: 4.0-57 (running version: 4.0-57/cc7c2b53)
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1libqb0: 0.17.2-1
pve-cluster: 4.0-24
qemu-server: 4.0-35
pve-firmware: 1.1-7lib
pve-common-perl: 4.0-36lib
pve-access-control: 4.0-9lib
pve-storage-perl: 4.0-29
pve-libspice-server1: 0.12.5-2vncterm: 1.2-1
pve-qemu-kvm: 2.4-12
pve-container: 1.0-21
pve-firewall: 2.0-13
pve-ha-manager: 1.0-13
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.4-3
lxcfs: 0.10-pve2
cgmanager: 0.39-pve1criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

 

[Ovidiu]

I'm so sorry but the formatting bar is missing. I had to go back and edit this thread and manually insert br html tags to get new lines.

 

[dietmar]

This is a single host, no cluster, nothing complicated. The problem arose after creating a new LXC I tried starting it and it just hung

What kind of container (what template)?

 

[Ovidiu]

Please see also this thread, similar problem of another user: http://forum.proxmox.com/threads/25012-pvedaemon-crashed-and-wont-start

Container: LXC
Template: Debian 8.0 Standard

 

[dietmar]

Container: LXC
Template: Debian 8.0 Standard

But that template does not start anything listening on port 85 by default? You installed additional software?

 

[Ovidiu]

OK, now I am totally confused would you mind explaining your question?

In the other thread I was asked to run some command to check port 85 (on the host) as that seems part of proxmox.
Now how does that relate to you asking me about the container?

I created the container as described, started it, the problem arose. No idea why you think there is something on port 85 inside that container? Am I missing something here?

 

[dietmar]

O
I created the container as described, started it, the problem arose. No idea why you think there is something on port 85 inside that container? Am I missing something here?

OK, we will investigate further. What kind of storage do you use for the container?

 

[Ovidiu]

The basic: local storage.

its a server with 2 HDs in a Hardware Raid so Proxmox only sees one disk and uses it.

Thanks for looking into it. The only thing I can add is that every time my GUI hung, my nfs mount became stale, or the other way around.

 

[dietmar]

Thanks for looking into it. The only thing I can add is that every time my GUI hung, my nfs mount became stale, or the other way around.

OK, I think we have an idea why it fails - we are working on a fix now.