Search results

it works!. thank you for saving me @fabian .

those packages installation was end with errors, if I install those package from bullseye, things should not be worse than now? thanks.

noVNC console not works for vm in the host now

have 3 pve host in 1 cluster, in customer's server room. ( those servers have no internet access, and under insanely restricted access control) was about to send some files to a new vm. ( package libpam-pwquality and it's dependencies). but I execute dpkg -i *.deb before qm terminal to the...

check the memory usage when (physical and swap ) no vm running 1 vm running then start 2nd vm , and monitor resource usage with htop

found real cause, in omv /export/folder is nfs 3 only, just mount /folder for v4/4.2 https://forum.openmediavault.org/index.php?thread/50726-nfs-options-ignored/

saw oom kill in logs

after change version to 3 in cluster storage, now pve-5 nfs mount works. thank you @fiona . seems is omv side issue, test on my station it's actually v3. v4 not work either.

yes, server is omv6, on nfs server : server has not upgrade recently, have tried recreate export rule. (same parameter as before), that is after issue noticed. assigned to 172.16.2.0/29.

just found this in dmesg of pve-5

above post of pve-5 is did not worked. below is pve-4 worked.

libpve-storage-perl are same. node 1/2/3/4/6 have upgrade to same version, but did not reboot yet ( the omv-1 nfs share has mounted 200+ days on 1/2/3/4/6 nodes). nfs server is openmediavault 6. storage.cfg mounts

there are 6 nodes in cluster ( going to replace a old node with pve-5. other 5 nodes can mount the nfs share automatically. )

the nfs share can be manually mount in the pve host by command "mount -t nfs4 172.16.0.31:/export/nfs-pve" , but auto mount failed. nfs share is configured in cluster - storage. nfs server side option is anongid=100, anonuid=100, insecure, no_root_squash, rw, subtree_check tried this...

never mind , found it. it can.

have 5 node in a cluster, 2 of them is about to replaced (still running). can I reuse removed nodes (by following wiki procedures ), and reuse removed node's name and ip address (with new physical server), then jion cluster? it's ok by doing so? or should I just use different name and ip...

if anyone have similar issue, use separate (only subnet of you pve cluster) nfs share profile, nfs 4.2 will work.

got a strange issue while mount nfs share from omv. both PVE and OMV has been upgraded to latest version. nfs options rw,subtree_check,insecure,no_root_squash,anonuid=100,anongid=100 , nfs client has all pve node's ip address included, even try whole lan subnets. what should I do to make...

in pve 7 and omv 6, do not specify nfs v4 or later version while mouting. only `default` version works. it will be connected as v3. omv is a little bit strange on this. https://docs.openmediavault.org/en/6.x/administration/services/nfs.html#clients

I thought 5.15.64-1 is stable enough (pbs vm is up for 13 days with some backup jobs), so create a new debian vm, while pulling docker images, kernel panic got me.o_O