Hello!
Suddenly, out of nowhere, both of my proxmox 4.1 nodes would not start pxe-proxy after a reboot. All of my VM's are running just fine. This setup has been running good for about two weeks.
root@core01:~# ps -A | grep 'pve'
2825 ? 00:00:00 pvefw-logger
4042 ? 00:00:00 pve-firewall
4048 ? 00:00:01 pvestatd
4057 ? 00:00:00 pvedaemon
4058 ? 00:00:00 pvedaemon worke
4059 ? 00:00:00 pvedaemon worke
4060 ? 00:00:00 pvedaemon worke
4063 ? 00:00:00 pve-ha-crm
4067 ? 00:00:00 pve-ha-lrm
The two nodes are identical and so are the errors and outputs for core02. Tell me if theres any more information you might need.
Thanks!
Suddenly, out of nowhere, both of my proxmox 4.1 nodes would not start pxe-proxy after a reboot. All of my VM's are running just fine. This setup has been running good for about two weeks.
root@core01:~# ps -A | grep 'pve'
2825 ? 00:00:00 pvefw-logger
4042 ? 00:00:00 pve-firewall
4048 ? 00:00:01 pvestatd
4057 ? 00:00:00 pvedaemon
4058 ? 00:00:00 pvedaemon worke
4059 ? 00:00:00 pvedaemon worke
4060 ? 00:00:00 pvedaemon worke
4063 ? 00:00:00 pve-ha-crm
4067 ? 00:00:00 pve-ha-lrm
Code:
root@core01:~# pveproxy restart
Job for pveproxy.service failed. See 'systemctl status pveproxy.service' and 'journalctl -xn' for details.
command 'systemctl reload-or-restart pveproxy' failed: exit code 1
root@core01:~# systemctl status pveproxy.service
â pveproxy.service - PVE API Proxy Server
Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled)
Active: failed (Result: exit-code) since Sun 2016-02-21 08:07:46 CET; 6s ago
Process: 4838 ExecStart=/usr/bin/pveproxy start (code=exited, status=255)
Feb 21 08:07:46 core01 pveproxy[4838]: start failed - failed to get address info for: core01: Name or service not known
Feb 21 08:07:46 core01 pveproxy[4838]: start failed - failed to get address info for: core01: Name or service not known
Feb 21 08:07:46 core01 systemd[1]: pveproxy.service: control process exited, code=exited status=255
Feb 21 08:07:46 core01 systemd[1]: Failed to start PVE API Proxy Server.
Feb 21 08:07:46 core01 systemd[1]: Unit pveproxy.service entered failed state.
Code:
root@core01:~# cat /etc/hosts --> was changed only before creation of cluster
127.0.0.1 localhost.localdomain localhost
192.168.0.253 core01 core01.chrjsn.se pvelocalhost
192.168.0.254 core02 core02.chrjsn.se
# 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
Code:
root@core01:~# pveversion -v
proxmox-ve: 4.1-26 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-1 (running version: 4.1-1/2f9650d4)
pve-kernel-4.2.6-1-pve: 4.2.6-26
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-41
pve-firmware: 1.1-7
libpve-common-perl: 4.0-41
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-17
pve-container: 1.0-32
pve-firewall: 2.0-14
pve-ha-manager: 1.0-14
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessieThanks!
Last edited:
