* [PVE-User] One cluster node get hang
@ 2023-01-17 15:00 Premjith R
0 siblings, 0 replies; only message in thread
From: Premjith R @ 2023-01-17 15:00 UTC (permalink / raw)
To: pve-user
Dear Team ,
Myself using Proxmox VE community edition for my testing environment. Using three node cluster for this setup, but today noticed one node is not accessible and getting following error.
Jan 17 02:49:13 pve21atrs001 pmxcfs[1534595]: [status] notice: received log
Jan 17 02:49:14 pve21atrs001 kernel: [8871754.354335] server[1534598]: segfault at 7f3aee6c79c5 ip 0000555e7ed1ec3a sp 00007f3a7bffe7f0 error 4 in pmxcfs[555e7ed05000+1b000]
Jan 17 02:49:14 pve21atrs001 kernel: [8871754.354348] Code: 48 83 c4 20 45 85 e4 0f 84 93 00 00 00 41 8b 47 04 44 39 e0 73 0e 05 00 10 00 00 44 39 e0 0f 83 7c 00 00 00 44 89 e3 4c 01 fb <44> 8b 23 44 39 6c 24 0c 76 6c 48 85 ed 74 06 48 39 6b 18 75 c5 0f
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Main process exited, code=killed, status=11/SEGV
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Failed with result 'signal'.
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Consumed 5h 7min 49.498s CPU time.
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 19.
Jan 17 02:49:14 pve21atrs001 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Consumed 5h 7min 49.498s CPU time.
Jan 17 02:49:14 pve21atrs001 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jan 17 02:49:14 pve21atrs001 pmxcfs[3872894]: fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
Jan 17 02:49:14 pve21atrs001 pmxcfs[3872894]: [main] crit: fuse_mount error: Transport endpoint is not connected
Jan 17 02:49:14 pve21atrs001 pmxcfs[3872894]: [main] crit: fuse_mount error: Transport endpoint is not connected
Jan 17 02:49:14 pve21atrs001 pmxcfs[3872894]: [main] notice: exit proxmox configuration filesystem (-1)
Jan 17 02:49:14 pve21atrs001 pmxcfs[3872894]: [main] notice: exit proxmox configuration filesystem (-1)
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
Jan 17 02:49:14 pve21atrs001 systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Jan 17 02:49:14 pve21atrs001 systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Jan 17 02:49:15 pve21atrs001 pveproxy[3870252]: ipcc_send_rec[1] failed: Connection refused
Jan 17 02:49:15 pve21atrs001 pveproxy[3870252]: ipcc_send_rec[2] failed: Connection refused
Jan 17 02:49:15 pve21atrs001 pveproxy[3870252]: ipcc_send_rec[3] failed: Connection refused
Jan 17 02:49:15 pve21atrs001 systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 20.
Jan 17 02:49:15 pve21atrs001 systemd[1]: Stopped The Proxmox VE cluster filesystem.
Jan 17 02:49:15 pve21atrs001 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jan 17 02:49:15 pve21atrs001 pmxcfs[3872895]: fuse: failed to access mountpoint /etc/pve: Transport endpoint is not connected
Thanks for reply.
Regards,
Premjith R
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-01-17 15:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-01-17 15:00 [PVE-User] One cluster node get hang Premjith R
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox