Search results

Thanks - certainly a valid point for consideration. Since enabling IO Thread on all disks, even loading up the storage with other tasks, I've not managed to replicate it - I've run about 5 backups so far this morning, repeatedly. Will let it run for a few days and see.

Yep, it is on NFS, on a Synology NAS RAID10, but it's not heavily utilised at the time :-/ Any/all other tasks happen either side of the backup window and don't clash. The strange thing for me, is that I could often re-run the backup during the day, when it is more heavily utilised with...

Looks like I've got a zombie: root 1657739 0.0 0.0 0 0 ? Zl 07:41 0:00 [qemu-img] <defunct> INFO: Starting Backup of VM 101 (qemu) INFO: Backup started at 2022-08-04 07:41:30 INFO: status = running INFO: VM Name: Downloads INFO: include disk 'scsi0'...

Did you get to the bottom of this? I'm seeing the same: 110: 2022-08-03 21:34:41 INFO: pruned 1 backup(s) not covered by keep-retention policy 110: 2022-08-03 21:34:41 INFO: Finished Backup of VM 110 (00:01:06) 111: 2022-08-03 21:34:41 INFO: Starting Backup of VM 111 (qemu) 111: 2022-08-03...

Just come across something similar to another thread, although not identical as nf_conntrack is/does load, when trying to use SYNPROXY - you need to set on the container: net.netfilter.nf_conntrack_tcp_loose=0 However, whilst this exists on the host, it does not exist (since 6.2.x upgrade...

Same here, HP DL servers - would have been helpful to have been in the Known Issues.

Just curious, as I stumbled upon this, as 'apt' replaced 'apt-get'... shouldn't 'apt upgrade' in the above script be the equivalent of the previous recommended 'apt-get dist-upgrade', i.e the script should be 'apt full-upgrade' (the previous apt-get dist-upgrade) to avoid dependency issues?

Wonderful, many thanks, this fixed the problem.

Just come across the below - we have 3 unprivileged containers that replicate/pull data over SSH, every 10 seconds or so. Not directly related to Proxmox itself, but just in case any one else is seeing this. https://github.com/systemd/systemd/issues/8015 Tried setting 'features: nesting=1' in...

I understand that PPP requires CAP_NET_ADMIN, so I was hoping I could use an unprivileged container with the following specified: lxc.cap.keep = net_admin lxc.mount.entry: /dev/ppp dev/ppp none bind,create=file Whilst /dev/ppp is created, permission is denied when trying to access it - are...

As a last ditch attempt I converted to an unprivileged container... and it works as expected. Figured privileged would be easier to start with....seems not!

16:51:37.811153 IP radius.35619 > radius.radius: RADIUS, Access-Request (1), id: 0x07 length: 134 16:51:37.816497 IP radius.radius > radius.35619: RADIUS, Access-Accept (2), id: 0x07 length: 20 When running just 1 container on the host, the RADIUS auth requests are seen on the loopback. When...

Other than the generic OpenVPN AUTH_FAILED rejection, no. Yes, packets end up at the correct container. I suspect this is going to be something to do with the RADIUS plugin and/or FreeRADIUS server. I'll need to run some tests with regular certs etc next to remove that from the equation...

Hi there, I have a 2 node cluster, 2 LXC containers, setup and running an OpenVPN server on TCP 443 for each. Each container works fine individually (stop 1, start the other, etc) and when the containers are on separate nodes of the cluster. Each container has it's own unique IP address...

You select a node when performing Migrate of a container through the UI, there is no option to specify the datastore - it syncs to the replicated datastore. Setting my dedicated pve-zsync volumes to disabled removes them from the UI, allows the migration to complete but still seems to allow...

Should have RTFM-ed... set to disable, seems to then work. Apologies. dir: local path /var/lib/vz content backup,vztmpl,iso zfspool: local-zfs pool rpool/data content rootdir,images sparse 1 zfspool: backup-pm001 pool backup-pm001...

Hi there, Apologies if this has already been answered somewhere, I was not able to find a conclusive answer. Long story short - I have a 2 node cluster, using containers only, each node has SSD based zpool for the main disk storage and then an HDD zpool which I was planning to use for...

I use Zextras for mine - yes, it is a paid for license, but very reasonably priced. Also gives migration tools, backup, and push email.

Quite a few conditions to be exploitable, from the github lxc commit.