Apologies, I missed those. I'll test and report back, though I can't see the mkdir one helping as the directory exists, it's whether it's mounted by merger in time before
--is_mountpoint looks likely though, thank you
An intermittent problem where sometimes, but not always, the creation of the folders (dump, images etc) from a backup dir will occur before the share is mounted on boot, which then prevents the share from mounting as the mountpoint now isn't empty.
Is there a way to choose the order of this...
Thanks, that's what I did in the end but, just to check, how did you so that copy from tmp to nodes? With ansible.builtin.copy? or with a shell sudo command?
Thanks but doesn't work for me I'm getting two different errors (some info obsfucated)
Don't want to waste anyone's time as it works the shell way works - but interested to understand this
In both cases I'm running these as sudo ansible-playbook
(not to self: is there a better way to get...
I've got as far as working out that /etc/pve is a fuse mount and that I should use the gui to replace the certs (although it would be nice to automate this)
So, more for my leaning, is there a better way to copy these into place through ansible that I'm missing please?
Or what am I missing here...
Think I'm being stupid with syntax here, fresh install with Serial drivers and qm guest agents installed
I'm having trouble getting powershell commands working
e.g.
oot@pve:~# qm guest exec 108 -- "C:\WINDOWS\system32\cmd.exe" "/c" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"...
I'm not sure it's right to blame proxmox here. For me it's my lack of understanding.
Have you tried a priviledges container with nfs and nesting features turned on?
As for disabling that's in the docs
https://pve.proxmox.com/wiki/Linux_Container
as per https://forum.proxmox.com/threads/advice-for-file-sharing-between-containers.25704/#post-129006
I've tried adding (with no results - i.e. still read only)
root@server2:~# cat /etc/apparmor.d/lxc/lxc-default-with-nfs
# Do not load this file. Rather, load /etc/apparmor.d/lxc-containers...
I have something, sort-of-working but have permissions issues and it feels like I'm doing this the wrong way (?)
on server2 I've mounted the nfs share (through GUI server view add NFS)
and then created a bind mount on the container
I can:
*rw to the share ok on server2
*can only read from the...
I'm trying to mount a zfs nfs share from another proxmox server (server1) onto an container (on server2)
server1 - pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-27-pve)
server2 -pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-3-pve)
Are you able to make a bind mount in a container to...
Hi,
This isn't a problem unique to proxmox but I wanted to check if the SMART info in the 'Disks' view was coming from smartctl?
Reason being, with this controller, you need to use another method to get proper smartctl information.
Is there any way to get the correct information into the GUI...
Looking here I should be able to able to change the prefix https://forum.proxmox.com/threads/mark-solved.18843/
But couldn't seen advanced options, is that now 'more options'?
Did me editing the tag mark it as solved or was that you?
Having a 'slow' day clearly!
Equal apologies for the delay, life got in the way.
I'll redo at some point and update this with what I find but nothing more for you to answer. Thanks for all the help!
PS You're absolutely right about bumping the config version!
I don't mind starting again and will probably do that. I think the answer is ignore the GUI and do it by CLI as the GUI does it incorrectly?
If it's the latter I thought you guys should know.
I don't know, It seems strange to me that the nodes are using two seperate networks 172. for proxmox...
Hmm, and the corosync.confs seems out of line as well, in that they mix the 172 and 192 addresses in ring0. But as least they both look the same
proxrml
proxplay
Thanks for sticking with me here Chris, know it must be painful but it really is hugely appreciated.
I think it all comes back to the first node being wrong doesn't it? Look for cat /etc/pve/.members under 'proxmox.rml pvecm status output' in my first post, where only proxrml was in the...
I think that
pvecm updatecerts
Has got rid of the errors
but if anyone is kind enough to confirm whether corosync.conf and
pvecm status
look ok now?
Is it ok to keep the quorum at 1 in a 2 node cluster? it looks like it may have been set back to 2 anyway (?)
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.