Raspyberry Pi 2 (Model B)

[faisalparkar]

Hey All,

I hope someone can assist. I have a 2 node cluster with PVE 8.2.2 running on both. I am trying to add a Raspberry Pi 2 Model B as a QDevice and I am running into the following problem. My 2 node cluster is fine but is obviously missing my QDevice.

root@pve02:~# pvecm qdevice setup 192.168.8.220 -f
/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed


/bin/ssh-copy-id: WARNING: All keys were skipped because they already exist on the remote system.
                (if you think this is a mistake, you may want to use -f option)




INFO: initializing qnetd server
Certificate database (/etc/corosync/qnetd/nssdb) already exists. Delete it to initialize new db


INFO: copying CA cert and initializing on all nodes


node 'pve01': Creating /etc/corosync/qdevice/net/nssdb
password file contains no data
node 'pve01': Creating new key and cert db
node 'pve01': Creating new noise file /etc/corosync/qdevice/net/nssdb/noise.txt
node 'pve01': Importing CAHost key verification failed.


INFO: generating cert request
Certificate database doesn't exists. Use /sbin/corosync-qdevice-net-certutil -i to create it
command 'corosync-qdevice-net-certutil -r -n pvecluster' failed: exit code 1

I have read through the following posts and can't seem to resolve this and not sure where I have gone wrong.


https://forum.proxmox.com/threads/qdevice-setup-still-harder-than-necessary.102436/

Any or all assistance is much appreciated.

 

[faisalparkar]

Just as another note, both my PVE nodes are showing their corosyn-qdevice service as failed.

root@pve02:~# systemctl status corosync-qdevice.service
× corosync-qdevice.service - Corosync Qdevice daemon
     Loaded: loaded (/lib/systemd/system/corosync-qdevice.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2024-12-04 21:40:37 GMT; 11h ago
       Docs: man:corosync-qdevice
    Process: 80227 ExecStart=/usr/sbin/corosync-qdevice -f $COROSYNC_QDEVICE_OPTIONS (code=exited, status=1/FAILURE)
   Main PID: 80227 (code=exited, status=1/FAILURE)
        CPU: 9ms


Dec 04 21:40:37 pve02 systemd[1]: corosync-qdevice.service: Scheduled restart job, restart counter is at 5.
Dec 04 21:40:37 pve02 systemd[1]: Stopped corosync-qdevice.service - Corosync Qdevice daemon.
Dec 04 21:40:37 pve02 systemd[1]: corosync-qdevice.service: Start request repeated too quickly.
Dec 04 21:40:37 pve02 systemd[1]: corosync-qdevice.service: Failed with result 'exit-code'.
Dec 04 21:40:37 pve02 systemd[1]: Failed to start corosync-qdevice.service - Corosync Qdevice daemon.
Dec 04 21:40:45 pve02 systemd[1]: corosync-qdevice.service: Start request repeated too quickly.
Dec 04 21:40:45 pve02 systemd[1]: corosync-qdevice.service: Failed with result 'exit-code'.
Dec 04 21:40:45 pve02 systemd[1]: Failed to start corosync-qdevice.service - Corosync Qdevice daemon.

Not sure if this is related.

 

[faisalparkar]

I dont quite know how, this is working for me now.

I redeployed my Raspberry Pi QDevice with an older version of OS (Raspbian GNU/Linux 11 (bullseye)).

Also ran through this:

M

Thread 'QDevice Setup still harder than necessary :('

Jan 4, 2022

I have succeeded in getting a Raspberry Pi QDevice running, but tore out too much hair along the way.
Starting Point

• Two Proxmox 7.1 nodes in a cluster
• Brand new Raspberry Pi Zero W (hardwired ethernet)

Issue One: Software not installing

• Resolution: Keep at it. Retry, reboot, etc. Clean out any partly-installed packages. Try again.

Issue Two: SSH keys

• I kept getting complaints about SSH keys not working or having been changed
• Resolution:
  • On every box, ensure /etc/hosts has correct entries for self and others
  • Delete stored keys in...

• MrPete
• Replies: 1
• Forum: Proxmox VE: Installation and configuration

POW!! Its working!