Recent content by woima

Yes, i did not wait enough.. Connection timed out. But ping and telnet to server 8007 port succeed from CLI. ~# time pvesm status --storage bu1 proxmox-backup-client failed: Error: error trying to connect: the handshake failed: Connection timed out (os error 110) Name Type Status...

If I set only datastore name then "pvesm status" just hangs and nothing happens.

Same, same error.. client version: 1.0.1 pve-manager/6.2-4/9824574a (running kernel: 5.4.41-1-pve) pvesm add pbs bu1 --server IP --datastore /datastore/zfs-pool --fingerprint 01:...36 --username root@pam --password xxx # pvesm status --storage bu1 Error: parameter verification errors...

I have similar problem. I had 3 dockers on this VM running java application and all went well, but after starting 4th java-docker all cpu:s jumped to 100% (this one process uses all). Strace for this process "hangs" in FUTEX_WAIT. Normally this java-process just idles. I have a vague memory that...

Thank you for taking me to tracks.. This is how i fixed this problem; mv /var/lib/dpkg/info/pve-manager.postinst /tmp/ mv /var/lib/dpkg/info/proxmox-ve.postinst /tmp/ apt-get install proxmox-ve mv /tmp/*postinst //var/lib/dpkg/info/

Just to make sure, this rbd_cache memory is located in ceph cluster (not on pve host)?

Good idea.. Don't have any ideas how long it takes / how much it takes to develop this. But we are involved if it happens!

I support this idea. Also ready to support developer economically too..

Same problem still exists.. Trying to clone running VM to another node and lvm target.. proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve) pve-manager: 3.4-6 (running version: 3.4-6/102d4547) pve-kernel-2.6.32-32-pve: 2.6.32-136 pve-kernel-2.6.32-39-pve: 2.6.32-156 lvm2: 2.02.98-pve4...

My Proxmox cluster uses nfs storage. Sometimes nfs server fails and VM remounts disks as readonly. Trying to avoid this by adding werror=stop,rerror=stop to vm.conf like this: ide0: nfs:101/vm-101-disk-1.qcow2,format=qcow2,rerror=stop,werror=stop,size=10G After this when nfs fails, it tryes to...

Yes, i tryed this allready, but it does work like that in proxmox 2.6 version.. https page is working well, but when java and vnc console starts it loads self-signed "default" www.proxmox.com certificate somehow from somewhere...

Just changed offical GoDaddy certificate to my nodes yesterday and today it took a while to figure out what is wrong. Thanks to Java update :) GUi is working great with GoDaddy certificate but Java somehow finds self-signed "www.proxmox.com" sertificate. Can't figure out how to change it to use...

Having this very same problem on all my 4 nodes. It just become after I lost my backup and templates storage nfs mountpoint. Rebooting node is not very good option. :~# /etc/init.d/rgmanager start Starting Cluster Service Manager: [FAILED] :~# tail /var/log/syslog Jan 8 09:46:06 PXX kernel...

Problem solved.. In Ubuntu nfs-kernel-server there is default option: RPCMOUNTDOPTS=--manage-gids Thanks to https://xkyle.com/solving-the-nfs-16-group-limit-problem/comment-page-1/#comment-5294