From: Premjith R <premjith_r@amritatech.com>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] One cluster node get hang
Date: Tue, 17 Jan 2023 20:30:33 +0530 (IST) [thread overview]
Message-ID: <1040227390.2707882.1673967633283.JavaMail.zimbra@amritatech.com> (raw)
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
reply other threads:[~2023-01-17 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1040227390.2707882.1673967633283.JavaMail.zimbra@amritatech.com \
--to=premjith_r@amritatech.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox