Search results

the fun thing here is: the webGUI reports the start "ok", yet in syslog we get something like this: pvestatd[1924]: command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5 proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a)...

just learned the rough way - snippets are not backed up for containers. is this by design (and why)?

btw. anyone fluent in LXD knowing how they do this?

thank you for your reply; so basically - if I want replication - I need zfs; if I want certain I/O-limits, I need LVM/anything else; I guess ceph is somewhere inbetween here :) I don't know how openvz did it, but there were iolimits on containers (sorry). I guess we'll have to be creative.

well, if anyone read this thread in the future - we did the following: generate a hook script in /var/lib/vz/snippets/ and put a perl script like this there: #!/usr/bin/perl use strict; use warnings; print "GUEST HOOK: " . join(' ', @ARGV). "\n"; # First argument is the vmid my $vmid = shift...

Hi is there a sane way within PVE to limit lxc-guests to use 100% io-bandwidth? regards hk

well, I mis-wrote, a simple STP on switch would be fine :) (though RSTP support in proxmox would be fine too)

well redundancy on relatively cheap switches: one LACP bond is the primary uplink for a bridge connecting the VEs/VMs to their network. another bond is the secondary uplink provided via a different switch in order to prevent a loop we obviously need STP. and this works well - only a RSTP "on"...

Hi is there any way to get "bridge-stp on" set using the proxmox-networking-config? it seems default is off and I found no way to change this. thx hk

Hi again, well in the meantime the hookscript magic has been created. But - we are still looking for some way to get the VE netconfig parameters (bridge, IP) in a correct way during the hookscript-execution. any hint would be appreciated.

Hi the way I see it /var/log/mail.log and mail.info are quite the same. Could we remove one or the other without breaking things on PMG? thx hk

I stand corrected - we tried https://forum.proxmox.com/threads/advancing-proxmox-mail-gateway-especially-spam-and-virus-detection.44152/ and obviously we got templates and were not aware of the consequences... sorry and thank you again.

thanks for your clarification, I swear we never copied anything to /etc/pmg/templates/ yet there are a lot of files dated March 25th 2019 :) will try removal of those files during the nighshift.

thx for the quick reply. fact is - we never changed any templates - so I guess changing the template during the inplace upgrade should be mentioned. we did follow the upgrade-guide to the best of our knowledge, somehow the pg_dropcluster and pg_upgradecluster worked fine, but todays reboot...

So, here we have a testsystem that we do also use for some regular mails (how should we test it otherwise :)). it was created as PMG 5.x, then in-place-upgraded to 6.0, afterwards to 6.1. (following https://pmg.proxmox.com/wiki/index.php/Upgrade_from_5.x_to_6.0#In-place_Upgrade of course)...

hit this problem today on one pve-host running PVE-5.4-13. on a newer PVE-6.0-9 host the limit is set to 65536 anyone able to clarify on this issue?

well, we believe we could finally use these hookscripts, the issue at hand would be the question how to get the VE IPv4 and IPv6 config in a portable way while this hookscript is being called. any hint is appreciated.

well well - stupid security :) after removing the bios protection (aka secure boot) - it boots fine on the other box too...

pve5to6 upgrade here - one worked and pretty similar box after reboot simply reports "error: attempt to read or write outside of disk 'hd0'" grub rescue mode starts but unable to recover from there.

we are going for a) all nodes are routers and no layer2 broadcast-domains for containers are wanted. we already do run routing-protocols on the hardware-nodes, thx for the suggestion. in order to get things really automated the node still needs to setup the routes for its containers, this is...