Can not login from Web UI

karyuu

Member
Jun 20, 2020
8
0
6
45
I have 2 nodes in cluter and remove one node from cluster by the following code.

Code:
systemctl stop pve-cluster corosync
pmxcfs -l
rm /etc/corosync/*
rm /etc/pve/corosync.conf
killall pmxcfs
systemctl start pve-cluster

check the status by systemctl status pve-cluster pveproxy
Code:
● pve-cluster.service - The Proxmox VE cluster filesystem
     Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor pr
     Active: active (running) since Thu 2022-06-09 16:14:32 EDT; 8min ago
    Process: 9567 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
   Main PID: 9569 (pmxcfs)
      Tasks: 6 (limit: 18964)
     Memory: 38.9M
        CPU: 513ms
     CGroup: /system.slice/pve-cluster.service
             └─9569 /usr/bin/pmxcfs

Jun 09 16:14:31 bd systemd[1]: Starting The Proxmox VE cluster filesystem...
Jun 09 16:14:32 bd systemd[1]: Started The Proxmox VE cluster filesystem.

● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor prese
     Active: active (running) since Thu 2022-06-09 15:36:59 EDT; 45min ago
    Process: 5320 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited,
    Process: 5322 ExecStart=/usr/bin/pveproxy start (code=exited, status=0/SUCCE
   Main PID: 5341 (pveproxy)
      Tasks: 4 (limit: 18964)
     Memory: 253.4M
        CPU: 4.349s
     CGroup: /system.slice/pveproxy.service
             ├─5341 pveproxy
             ├─5342 pveproxy worker
             ├─5343 pveproxy worker
             └─5344 pveproxy worker

Jun 09 15:36:58 bd systemd[1]: Starting PVE API Proxy Server...
Jun 09 15:36:59 bd pveproxy[5341]: starting server
Jun 09 15:36:59 bd pveproxy[5341]: starting 3 worker(s)
Jun 09 15:36:59 bd pveproxy[5341]: worker 5342 started
Jun 09 15:36:59 bd pveproxy[5341]: worker 5343 started
Jun 09 15:36:59 bd pveproxy[5341]: worker 5344 started
Jun 09 15:36:59 bd systemd[1]: Started PVE API Proxy Server.

Also I have used pvecm updatecerts to update the certificate.

I can open the web ui , but can not login by root. it shows

Code:
Login failed. Please try again

How can I fix this issue?

Thanks
 
Good morning,

please read https://pve.proxmox.com/pve-docs-6/pve-admin-guide.html#_remove_a_cluster_node. Your commands are there also but you've probably missed pvecm delnode oldnode.

For the current situation: log in at the local console and tell PVE that there is only one node: ~# pvecm expected 1. Then you should be able to login again at the web gui.

Good luck

I ran the code on two seperated node, and it shows the following message.

Code:
root@local:~# pvecm delnode pro-bd
Node/IP: pro-bd is not a known host of the cluster.
root@local:~# pvecm expected 1
Error: Corosync config '/etc/pve/corosync.conf' does not exist - is this node part of a cluster?

On the both hosts, I can login on web ui now, but it still shows the other host name under the datacenter, all VMs under the other host with question mark.

How can I delete the useless host?

Thanks
 
I have seperated node, but the host still shows the other node, and all VMs with question mark.

How can I delete the node?

Thanks
 

Attachments

  • Capture.PNG
    Capture.PNG
    38.1 KB · Views: 5
The node with the name "local"?

Take a look into /etc/pve/nodes/. I expect you'll see two directories, one for each node known by PVE. Correct?

Examine those folders - there is a lot of interesting configuration settings stored there. Always remember: "/etc/pve/" is an artificial filesystem implemented by the PVE database.

I can not test this here, of course - and manual manipulations under /etc/pve are generally dangerous! Usually I do create a backup before I play with settings which I do not understand completely.

Finally: to eliminate "local" from the presentation view in the Web-Gui simply delete that corresponding folder with the same name below ".../nodes/".

Caution: this is NOT "/etc/pve/local"! If I read your screenshot correctly /etc/pve/local should be a link to /etc/pve/nodes/bd, if "bd" is your actual node. This link should remain, of course.


(Again: nothing tested --> at your own risk.)


Best regards
 
  • Like
Reactions: datschlatscher