Я создаю кластер. Кластер создан на моем первом узле.
`code_language.shell: # cat /etc/pve/.members`
```json
{
"nodename": "proxmox1",
"version": 3,
"cluster": { "name": "proxcluster", "version": 1, "nodes": 1, "quorate": 1 },
"nodelist": {
"proxmox1": { "id": 1, "online": 1, "ip": "172.16.1.2"}
}
}
```
Я проверил, что на моём втором узле есть ключ авторизации в папке `priv`.
`code_language.shell: # ls /etc/pve/priv/`
```
acme authkey.key authorized_keys lock pve-root-ca.key pve-root-ca.srl
```
Когда я использую assisted join на этом втором узле, он зависает на "request addition of node".
`code_language.shell: Establishing API connection with host '172.16.1.2'`
`Login succeeded.`
`check cluster join API version`
`No cluster network links passed explicitly, fallback to local node IP '172.16.1.3'`
`Request addition of this node`
На узле 1 proxmox2 был добавлен, но показывает как offline.
`code_language.shell: # cat /etc/pve/.members`
```json
{
"nodename": "proxmox1",
"version": 4,
"cluster": { "name": "proxcluster", "version": 2, "nodes": 2, "quorate": 0 },
"nodelist": {
"proxmox1": { "id": 1, "online": 1, "ip": "172.16.1.2"},
"proxmox2": { "id": 2, "online": 0}
}
}
```
На узле 2 папка `priv` была удалена процессом присоединения, но не была воссоздана.
`code_language.shell: # ls /etc/pve/`
```
corosync.conf local lxc openvz qemu-server
```
На узле 2 я вижу ошибку аутентификации на `pvedaemon` из моего существующего UI tab.
`May 30 06:49:01 proxmox2 pvedaemon[1221]: authentication failure; rhost=::ffff:my.public.ip user=root@pam msg=Authenti>`
`code_language.shell: # cat /etc/pve/corosync.conf`
```
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox1
nodeid: 1
quorum_votes: 1
ring0_addr: 172.16.1.2
}
node {
name: proxmox2
nodeid: 2
quorum_votes: 1
ring0_addr: 172.16.1.3
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: proxcluster
config_version: 2
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
```
`code_language.shell: # journalctl -u pve-cluster.service --since "30min ago"`
```
May 30 06:48:50 proxmox2 systemd[1]: Stopping pve-cluster.service - The Proxmox VE cluster filesystem...
May 30 06:48:50 proxmox2 pmxcfs[897]: [main] notice: teardown filesystem
May 30 06:48:50 proxmox2 pmxcfs[897]: [main] notice: exit proxmox configuration filesystem (0)
May 30 06:48:50 proxmox2 systemd[1]: pve-cluster.service: Deactivated successfully.
May 30 06:48:50 proxmox2 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 30 06:48:50 proxmox2 systemd[1]: pve-cluster.service: Consumed 1.082s CPU time.
May 30 06:48:51 proxmox2 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 30 06:48:51 proxmox2 pmxcfs[7400]: [main] notice: resolved node name 'proxmox2' to '172.16.1.3' for default node IP>
May 30 06:48:51 proxmox2 pmxcfs[7400]: [main] notice: resolved node name 'proxmox2' to '172.16.1.3' for default node IP>
May 30 06:48:51 proxmox2 pmxcfs[7413]: [quorum] crit: quorum_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [quorum] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [confdb] crit: cmap_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [confdb] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [dcdb] crit: cpg_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [dcdb] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [status] crit: cpg_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [status] crit: can't initialize service
May 30 06:48:52 proxmox2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: update cluster info (cluster name proxcluster, version = 2)
May 30 06:48:57 proxmox2 pmxcfs[7413]: [dcdb] notice: members: 2/7413
May 30 06:48:57 proxmox2 pmxcfs[7413]: [dcdb] notice: all data is up to date
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: members: 2/7413
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: all data is up to date
```
Какие есть предложения по устранению этой проблемы? Спасибо за ваше время.
`code_language.shell: # cat /etc/pve/.members`
```json
{
"nodename": "proxmox1",
"version": 3,
"cluster": { "name": "proxcluster", "version": 1, "nodes": 1, "quorate": 1 },
"nodelist": {
"proxmox1": { "id": 1, "online": 1, "ip": "172.16.1.2"}
}
}
```
Я проверил, что на моём втором узле есть ключ авторизации в папке `priv`.
`code_language.shell: # ls /etc/pve/priv/`
```
acme authkey.key authorized_keys lock pve-root-ca.key pve-root-ca.srl
```
Когда я использую assisted join на этом втором узле, он зависает на "request addition of node".
`code_language.shell: Establishing API connection with host '172.16.1.2'`
`Login succeeded.`
`check cluster join API version`
`No cluster network links passed explicitly, fallback to local node IP '172.16.1.3'`
`Request addition of this node`
На узле 1 proxmox2 был добавлен, но показывает как offline.
`code_language.shell: # cat /etc/pve/.members`
```json
{
"nodename": "proxmox1",
"version": 4,
"cluster": { "name": "proxcluster", "version": 2, "nodes": 2, "quorate": 0 },
"nodelist": {
"proxmox1": { "id": 1, "online": 1, "ip": "172.16.1.2"},
"proxmox2": { "id": 2, "online": 0}
}
}
```
На узле 2 папка `priv` была удалена процессом присоединения, но не была воссоздана.
`code_language.shell: # ls /etc/pve/`
```
corosync.conf local lxc openvz qemu-server
```
На узле 2 я вижу ошибку аутентификации на `pvedaemon` из моего существующего UI tab.
`May 30 06:49:01 proxmox2 pvedaemon[1221]: authentication failure; rhost=::ffff:my.public.ip user=root@pam msg=Authenti>`
`code_language.shell: # cat /etc/pve/corosync.conf`
```
logging {
debug: off
to_syslog: yes
}
nodelist {
node {
name: proxmox1
nodeid: 1
quorum_votes: 1
ring0_addr: 172.16.1.2
}
node {
name: proxmox2
nodeid: 2
quorum_votes: 1
ring0_addr: 172.16.1.3
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: proxcluster
config_version: 2
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
```
`code_language.shell: # journalctl -u pve-cluster.service --since "30min ago"`
```
May 30 06:48:50 proxmox2 systemd[1]: Stopping pve-cluster.service - The Proxmox VE cluster filesystem...
May 30 06:48:50 proxmox2 pmxcfs[897]: [main] notice: teardown filesystem
May 30 06:48:50 proxmox2 pmxcfs[897]: [main] notice: exit proxmox configuration filesystem (0)
May 30 06:48:50 proxmox2 systemd[1]: pve-cluster.service: Deactivated successfully.
May 30 06:48:50 proxmox2 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
May 30 06:48:50 proxmox2 systemd[1]: pve-cluster.service: Consumed 1.082s CPU time.
May 30 06:48:51 proxmox2 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
May 30 06:48:51 proxmox2 pmxcfs[7400]: [main] notice: resolved node name 'proxmox2' to '172.16.1.3' for default node IP>
May 30 06:48:51 proxmox2 pmxcfs[7400]: [main] notice: resolved node name 'proxmox2' to '172.16.1.3' for default node IP>
May 30 06:48:51 proxmox2 pmxcfs[7413]: [quorum] crit: quorum_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [quorum] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [confdb] crit: cmap_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [confdb] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [dcdb] crit: cpg_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [dcdb] crit: can't initialize service
May 30 06:48:51 proxmox2 pmxcfs[7413]: [status] crit: cpg_initialize failed: 2
May 30 06:48:51 proxmox2 pmxcfs[7413]: [status] crit: can't initialize service
May 30 06:48:52 proxmox2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: update cluster info (cluster name proxcluster, version = 2)
May 30 06:48:57 proxmox2 pmxcfs[7413]: [dcdb] notice: members: 2/7413
May 30 06:48:57 proxmox2 pmxcfs[7413]: [dcdb] notice: all data is up to date
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: members: 2/7413
May 30 06:48:57 proxmox2 pmxcfs[7413]: [status] notice: all data is up to date
```
Какие есть предложения по устранению этой проблемы? Спасибо за ваше время.
