Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ● pve-cluster.service - The Proxmox VE cluster filesystem
- Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled)
- Active: failed (Result: signal) since Mon 2016-10-24 06:39:07 EDT; 1h 41min ago
- Process: 93984 ExecStart=/usr/bin/pmxcfs $DAEMON_OPTS (code=exited, status=0/SUCCESS)
- Main PID: 93995 (code=killed, signal=KILL)
- Oct 24 06:38:55 pve11 pmxcfs[93995]: [status] notice: queue not emtpy - resening 365 messages
- Oct 24 06:38:57 pve11 systemd[1]: pve-cluster.service start-post operation timed out. Stopping.
- Oct 24 06:39:04 pve11 pmxcfs[93995]: [status] notice: members: 1/1757, 2/1695, 3/93995, 4/1813, 5/1618, 6/1578, 7...2/1565
- Oct 24 06:39:04 pve11 pmxcfs[93995]: [status] notice: queue not emtpy - resening 372 messages
- Oct 24 06:39:06 pve11 pmxcfs[93995]: [status] notice: members: 1/1757, 2/1695, 3/93995, 4/1813, 5/1618, 6/1578, 7...2/1565
- Oct 24 06:39:06 pve11 pmxcfs[93995]: [status] notice: queue not emtpy - resening 372 messages
- Oct 24 06:39:07 pve11 systemd[1]: pve-cluster.service stop-sigterm timed out. Killing.
- Oct 24 06:39:07 pve11 systemd[1]: pve-cluster.service: main process exited, code=killed, status=9/KILL
- Oct 24 06:39:07 pve11 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
- Oct 24 06:39:07 pve11 systemd[1]: Unit pve-cluster.service entered failed state.
- Hint: Some lines were ellipsized, use -l to show in full.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement