for the record, this issue appears to not be about backup and recovery, but something that has recently broken which has resulted in my UID mapping to 'www-data' no longer working.
It seemed quite distinct from the issue as I understood it here, so have posted a separate thread: Unable to map...
For the last year or so I've had a container running that has map of an 'nc' user (uid: 1005) on my pve host to 'www-data' (uid: 33) in an LXC unprivileged container. Has worked flawlessly.
However, recently I had cause to restore from a backup and I was getting a bunch of errors related to...
Hi
I've had cause to recover one of my (unprivileged) containers from backup (via the GUI). The recovery process seemed to work fine, and the container appeared to start up as expected.
However, the permissions of several folders in the recovered container have been set to nobody:nogroup, and...
...and I see from https://forum.proxmox.com/threads/container-w-mount-point-snapshots.36086/ that it's on the list to do.
...and a workaround by temporarily editing the config file and removing the mount points...
...and now I've taken a snapshot on that VM, the snapshot button is now active (and working) for one of the containers (I can't be sure it wasn't before but I thought I checked them all several times) - interestingly, this is the only one without mountpoints (the sole VM also doesn't have mount...
Here's a container I use for plex that I can't snapshot in the GUI:
arch: amd64
cores: 4
hostname: plex
memory: 12448
mp0: /mnt/pve/remote-stagnum-media/private,mp=/media
mp1: /var/lib/plexmediaserver/logs,mp=/var/lib/plexmediaserver/Library/Application Support/Plex/Logs
net0...
Looking in the GUI, the only difference I see between the local storage, and this one that I added, is that the local has 'thin provision' enabled? Is that necessary for snapshots?
Hi!
I'm not sure - what would that involve? Apart from creating the pool and then adding it to proxmox I don't recall doing anything else.
Is that what's listed on the ZFS tips and tricks page (which I've just found):
zfs create -o mountpoint=/mnt/vztmp rpool/vztmp
zfs set acltype=posixacl...
My option to take a snapshot of any of my containers in the GUI is greyed out. They are all hosted on a local ZFS drive (but not the proxmox boot drive) which I believe means they should be suitable for snapshots?
Incidentally, snapshots run as scheduled backups fine.
Is there something I've...
I have mostly resolved this now. I did a fresh install and went more slowly through setting up and configuring. There was an error in my openswitch configuration, which I believe was causing the shutdown problems. Shutdown is now quick and seamless.
For the startup problems, it was a timing...
I have read that the startup issue could be a timing problem, with the network not up and running when the container is trying to start. I am using an OVS bond, and virtual LANs, both of which I assume take more time to initiate etc - could that be the problem here?
I've tried adding startup...
what I continue to find most baffling, is that the containers start up and shutdown seamlessly from the GUI. And I can run the command that the log says is problematic when shutting down the container from the CLI and it works instantly ("lxc-stop -n 221 --kill").
Thanks for the reference!
It looks like they're trying to mount the nfs share directly in the containers though? I'm mounting it on the host, and creating mount points in the containers - which I believe, from other posts on here, is the preferred approach and doesn't involve app armour...
Thanks for the reply!
I can access the shares fine - I think I would get a stale file handler error when I try to list the contents, for example, if that was the issue? I'll keep your script handy though, in case I hit that later!
I'm a bit confused how the containers start up and shutdown...
Syslog is giving some more details with the startup issue
Oct 28 20:55:08 pve systemd[1]: Starting PVE LXC Container: 221...
Oct 28 20:55:08 pve lxc-start[3351]: lxc-start: 221: lxccontainer.c: wait_on_daemonized_start: 751 No such file or directory - Failed to receive the container state
Oct...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.