/etc/pve/priv/authorized_keys question

bread-baker

Member
Mar 6, 2010
432
0
16
root's .ssh/authorized_keys is a symlink to /etc/pve/priv/authorized_keys .

should ssh-copy-id from another system be expected to write to /etc/pve/priv/authorized_keys ?
 
ssh-copy-id to fbc1 does not works after I tried to setup a cluster.

rebooting it now.... lets see if this works from another system:
ssh-copy-id fbc1 ....

nope:
Code:
root@fbc1's password: 
cat: write error: Permission denied

and on fbc1:
Code:
root@fbc1 /etc/pve # ls > junkfile
-bash: junkfile: Permission denied

mount :
Code:
root@fbc1 /etc/pve # mount
/dev/mapper/pve-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
/dev/mapper/fbc1-bkup on /bkup type ext4 (rw,noatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
none on /sys/kernel/config type configfs (rw)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
root@rsync:/home/ on /home-fbc type fuse.sshfs (rw,nosuid,nodev,max_read=65536,allow_other)

Code:
root@fbc1 /etc/pve # pveversion -v
pve-manager: 2.0-12 (pve-manager/2.0/784729f4)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-53
pve-kernel-2.6.32-6-pve: 2.6.32-53
lvm2: 2.02.86-1pve2
clvm: 2.02.86-1pve2
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-12
qemu-server: 2.0-10
pve-firmware: 1.0-13
libpve-common-perl: 1.0-8
libpve-access-control: 1.0-2
libpve-storage-perl: 2.0-8
vncterm: 1.0-2
vzctl: 3.0.29-3pve3
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.1-1

suggestions?
 
Sure, because you always have quorum on a single node.

ok, obviously I'm doing something wrong. but fbc1 was running prox 2.0 form 1-st beta.
then per suggestions here, I did a fresh install on fbc186 and tried to add it .

as you can see in the other thread that did not work after a reinstall.

i do not mind reinstalling both of these systems, I've already used vzdump to save what we need.

If I do that, then I assume I should follow http://pve.proxmox.com/wiki/Proxmox_VE_2.0_Cluster more carefully ?
 
ok, obviously I'm doing something wrong.

The last error you posted is due to quorum loss. I guess you have 2 nodes, and on node is not working correctly.

but fbc1 was running prox 2.0 form 1-st beta.

and is is still running without problems (or do you have a problem there too - beside no quorum)?

then per suggestions here, I did a fresh install on fbc186 and tried to add it .

as you can see in the other thread that did not work after a reinstall.

Yes - I don't really have an idea whats wrong, sorry.
 

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!