Recent content by kroem

(I know I must be missing something fundemental here, but my google-fu is failing me, so sorry in advance) I have been using a simple bind mount without problems for a long time, but since I restored this LXC I have all kinds of permission problems. It's the same for other LXC's too. Storage...

I'm running into the same problem here, is there anyway to get some support so it actually installable? Never had this problem when I first installed my pve hosts some 3-4 years ago. Ok, so I can install Debian and PVe over it, but getting a zfs root mirror is a whole other process. The PVE...

Actaully this is fine after a reboot it seems, but the output was (before reboot): root@cat:~# wc /proc/mounts 5966 35796 1072539 /proc/mounts Right now it is root@cat:~# wc /proc/mounts 137 822 12225 /proc/mounts

I have the same problem, did you file a bug that I can attach to maybe?

AH! It worked ! Thanks you so very very much!

Sorry, they are below. And to confirm - I have not remove the raspi, I have removed a node called "dog" (long time ago). I did not increment the config version when editing the corosync.conf files from the raspi (from wiki). Should I do that, and send the /etc/corosync/corosync.conf file to the...

Ok, thanks. The status is "running", quorum is fine, but I still have that error message root@cat:~# pve-ha-crm status running root@cat:~# ssh bug pve-ha-crm status running

OK, but on the pve nodes should I edit the /etc/pve/corosync files? If so, the wiki should be update :) No errors. Both nodes have been reloaded multiple times, but this is what the log says if I restart the service: root@cat:~# journalctl -u pve-ha-crm -- Logs begin at Mon 2019-04-08...

Ok, was just following the wiki: https://pve.proxmox.com/wiki/Raspberry_Pi_as_third_node (I did think it was a little bit strange) There's a log entry(?) root@cat:~# grep -r dog /etc/pve/ha/*...

Maybe, but the node is not there root@cat:~# cat /etc/pve/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: bug nodeid: 3 quorum_votes: 1 ring0_addr: bug } node { name: cat nodeid: 1 quorum_votes: 1 ring0_addr: cat } }...

I'm trying to add some HA config to my cluster, but the HA tab is locked due to an error saying: "unable to read file '/etc/pve/nodes/dog/lrm_status' (500)" "dog" is an old node which I have since removed. Any idea where I need to remove some config in order for PVE to not look for this config...

does this mean the feature will be added?

It's a bit outside the scope of Pve but you have some commercial ZFS-HA offerings like RSF-1, or - https://github.com/ewwhite/zfs-ha/wiki

I've discovered that the privilege Datastore.Allocate is needed in role in order to grant a user access/browse Content of a storage? This seems pretty backwards - what does then Datastore.AllocateTemplates do? Datastore.Allocate grants users the ability to remove datastores which is not...

I'm having the same problem - upgrading the cluster now to see if it helps.