惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

量子位
F
Fortinet All Blogs
J
Java Code Geeks
Y
Y Combinator Blog
Stack Overflow Blog
Stack Overflow Blog
V
Visual Studio Blog
M
MIT News - Artificial intelligence
腾讯CDC
Last Week in AI
Last Week in AI
The Cloudflare Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Jina AI
Jina AI
Microsoft Security Blog
Microsoft Security Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
P
Proofpoint News Feed
博客园 - 叶小钗
Recent Announcements
Recent Announcements
T
Tailwind CSS Blog
Engineering at Meta
Engineering at Meta
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
人人都是产品经理
人人都是产品经理
L
LangChain Blog
博客园 - 司徒正美
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
[SOLVED] - Adding nodes while one member offline
invalid@exam · 2019-01-31 · via Proxmox Support Forum

I had a 5 node cluster with Ceph setup and running. Node2 was shutdown for maintenance and while that node was down I added two new nodes to expand to 7 nodes. Now that Node2 has been brought back online it does not appear in the cluster and is acting like a stand-alone PVE server. The other nodes in the cluster still show that node2 as down.

pve2.png

To make matters worse, it was also functioning as a Monitor for Ceph and is not joining the Ceph cluster either and reporting all OSDs down and not healthy. I used the GUI to remove the monitor while logged into another node and it looks like that worked as I'm only seeing two monitors and Ceph reports healthy. Is there any way to rejoin this node correctly without having to rebuild the entire cluster?
pve2.png pve3.png

Actually if possible how can I completely remove this node from the PVE and Ceph cluster? The proc needs to be replaced and that's going to take at least a week. I'm thinking I will need to rebuild the cluster entirely which would suck and kill off the remainder of my day.

dcsapak

Proxmox Staff Member

Staff member

Feb 1, 2016
10,682
1,735
273
37
Vienna

I had to rebuild the cluster as something got out of sync fortunately there was nothing of value yet installed. We will make note to make sure not to make cluster-wide changes with nodes offline without taking precautions.

I did repair this error by just manually syncing the
/etc/pve/corosync.conf on my at the time offline server.
After that it was in sync and working normal.

You dont need to reinstall for this simple error.

I did repair this error by just manually syncing the
/etc/pve/corosync.conf on my at the time offline server.
After that it was in sync and working normal.

You dont need to reinstall for this simple error.

I am still learning :) That i good to know and I will remember thank you.

thanks! the sync of the corosync.conf did work for me on a Proxmox 9.x node which was offline during the addition of 2 other nodes.
Copying the corosync.conf worked well:
scp root@existing-node:/etc/corosync/corosync.conf root@returned-node:/etc/corosync/corosync.conf

After this, I still had to reboot the returned node.