Recent content by borpin

On the target node, doing a systemctl restart pveproxy Fixes the problem immediately

Many thanks - solved it for me :)

Yes you will. You need to remove the enterprise add the no-subscription repositories (assuming you have no subscription). sed -i 's/^\([^#].*\)/# \1/g' /etc/apt/sources.list.d/pve-enterprise.list echo "deb http://download.proxmox.com/debian/pve buster pve-no-subscription" >...

Old thread I know but you need to configure /etc/apcupsd/apcupsd.conf such that the NISIP 0.0.0.0 so it will accept connections from a machine other than itself (the netstat command at the top told you that. You still cannot connect from a browser, but if you wish to read the data you may be...

I realised something today that should have been blindingly obvious; data should be stored outside the container. Doh! I'm using Proxmox at home on an old laptop to run things like pi-hole, mosquito - not much data so not an issue. I'm also running InfluxDB and Postgresql - lots of data writes...

OK, so is the fact the other node looking for it a bug, when a container has been migrated that previously used it for backup? Would it be worth adding to the Wiki a how to add a USB Drive? If I was starting from scratch, what is the best way to do it? Does it need Ceph to be installed (I have...

That could be the issue. I have used the USB as a directory Is that not the right way?

Hi @Dominic How do I access that Menu item?

I have 2 old laptops in a PVE cluster (which is brilliant). One of the nodes has a USB drive attached for backup. In the GUI, I can see the USB attached to the first node, but it also appears on the second node (with a question mark). I continually get errors in the second node logs Mar 10...

I have exactly the same question. I had previously added in the no-subscription repository, but that entry had mysteriously disappeared. Adding it in again and running an apt-update, trying the ifupdown2 install (dry run) - it worked fine. I have no idea how the deb entry got removed (the...

Got there in the end. Fist find out who had the lock fuser /var/lock/qemu-server/lock-101.conf Then kill the process and then stop/shutdown the server. Thanks for the assist!

Root is by default prevented from logging in by SSH. edit /etc/ssh/sshd_config from the web console/shell. and set PermitRootLogin yes A better way is to add a drop-in and include it and an even better way is to set up some keys.

I cannot force a VM to shutdown - I need to simply pull the plug. I continually get trying to acquire lock... TASK ERROR: can't lock file '/var/lock/qemu-server/lock-101.conf' - got timeout How can I kill the process?

I am getting an error trying to update Ign:4 https://apt.iteas.at/iteas buster InRelease Err:5 https://apt.iteas.at/iteas buster Release Could not handshake: Error in the pull function. [IP: 77.235.68.36 443] Reading package lists... Done E: The repository 'https://apt.iteas.at/iteas buster...

Having let it run, you are correct. It is what I would hope the backup system would do, but that isn't really how it is described. "Max Backups per VM" would be an improvement I'd suggest. Thanks for your help.