[SOLVED] can't create shared ssh key database '/etc/pve/priv/authorized_keys'

mirra

New Member
Jan 25, 2017
6
1
1
34
Hello,

my first cluster was working OK, Production cluster is just an armageddon...
I have 3 nodes cluster. 1 master is running in KVM to control other 2 servers.
This is pvecm status from reinstalled master

pvecm status
Quorum information
------------------
Date: Wed Jan 25 12:49:36 2017
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/4
Quorate: Yes

Votequorum information
----------------------
Expected votes: 1
Highest expected: 1
Total votes: 1
Quorum: 1
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.0.0.6 (local)


On the network, everything is OK, /etc/hosts are ok.

When I want to add those 2 other servers it shows me following:
othermachine:# pvecm add 10.0.0.6
can't create shared ssh key database '/etc/pve/priv/authorized_keys'
authentication key already exists

ls /etc/pve/ shows there is NO priv directory on the othermachine.
othermachine:/etc/pve# ls -lah
total 4.5K
drwxr-xr-x 2 root www-data 0 Jan 1 1970 .
drwxr-xr-x 97 root root 4.0K Jan 25 12:18 ..
-r--r----- 1 root www-data 357 Jan 1 1970 .clusterlog
-r--r----- 1 root www-data 543 Jan 25 11:30 corosync.conf
-rw-r----- 1 root www-data 2 Jan 1 1970 .debug
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 local -> nodes/taxodium
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 lxc -> nodes/taxodium/lxc
-r--r----- 1 root www-data 268 Jan 1 1970 .members
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 openvz -> nodes/taxodium/openvz
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 qemu-server -> nodes/taxodium/qemu-server
-r--r----- 1 root www-data 208 Jan 1 1970 .rrd
-r--r----- 1 root www-data 380 Jan 1 1970 .version
-r--r----- 1 root www-data 18 Jan 1 1970 .vmlist


Even through I am root I cannot create directories here:
othermachine:/etc/pve# mkdir priv
mkdir: cannot create directory ‘priv’: Permission denied

How to resolve this issue?

I do not want to reinstall everything again. Do not tell me this is so useless so administrators have to always reinstall proxmox whenever some problem like this appears.
 
Good community makes good technology, so let me rather answer myself for this:
stop pve-cluster
stop corosync
pmxcfs -l
then you can make:
mkdir /etc/pve/priv/
and touch the file authorized_keys

Thanks, you can close this topic.
 
  • Like
Reactions: BerndKleinert

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!