I upgraded my hosts and removed all SWAP's from the LXC clients and this is the result.
Now I wonder if the problem was the code or the SWAP. I'm betting LXC don't like ZFS with SWAP.
Actually I'm using Proxmox FireWall's rather than "Enterprise Firewall" for many reasons.
Most importantant is the cluster and the flexibility it provides. It's really simple and scalable. It's client friendly (LXC's are managed by clients themselves.) No need to write a ticket and wait a few...
I was trying to clone new Standalone Proxmox installation on KVM by doing a backup to PBS server then restoring that backup as a new virtual machine.
Worked quite well.
Then I updated
/etc/hostname
/etc/hosts
/etc/network/interfaces
and regenerated ssh keys with
ssh-keygen -A
After reboot I...
I'm thinking this maybe the cause:
root@vm2404:~# cat /var/log/syslog |grep block
Oct 29 14:42:33 vm2404.ic4.eu kernel: [681424.800987] vmbr1: port 9(fwpr700p0) entered blocking state
Oct 29 14:42:33 vm2404.ic4.eu kernel: [681424.808510] fwbr700i0: port 1(fwln700i0) entered blocking state...
After upgrade this message started occasionally flash on LXC terminals.
channel 3: open failed: administratively prohibited: open failed
Then after a few seconds it disappears and says something about forwarding but too quickly to see.
Remote port forwarding failed to listen on port XXX
Oddly...
I can't seem to get remote logging to work on Debian12 LXC containers.
FQDN works on Qemu servers but the same rsyslog.conf file does not give full name from LXC container.
Any idea what's going on here..?
If Debian 12 has been installed with minimal network boot CD/ISO/USB then it probably does not include bridge-utils which is mandatory component to get vmbr bridges to work.
Make sure you install it with apt install bridge-utils first then fix these files /etc/hosts and /etc/network/interfaces...
hmm. I don't understand why root@pam always asks password when I do this:
/usr/bin/proxmox-backup-client backup etc.pxar:/etc var.pxar:/var --repository backup.ic4.eu:store1
The backup-client is Proxmox host and should have proper keys to backup server.
I have always felt journalctl was a step in wrong direction.
"KISS. Keep It Simple Stupid." Those are words to live by. Other as good is...
"If it's not broken don't try to fix it."
I have been testing PMG for a while now and I have to say I'm impressed.
I like how simple it is to use.
There is one thing that it's missing though.
You can have finer grained control (than domain level) by putting me@example.com in transport_maps by using virtual_alias_maps.
# transport...
Sometimes LXC kills (random) services if it's running out of memory. Usually it kills ClamAV because it uses most memory but sometimes it's something else. Clam is really annoying because when it loads new DataBase it doubles the memory it needs momentarely before it unloads the old database...
I currently have this command running in cron:
echo "ConcurrentDatabaseReload no" >> /etc/clamav/clamd.conf && systemctl restart clam*
I would like to disable all Clam related services in our PMGW.
Any suggestions on how to do that?
For those of you who will experience ZFS fun when import hang's or crashes... this might help you.
zpool import -o readonly=on -f POOLNAME
After trying dosens of different commands - that was the only command that worked for me... and I had to give that from live (kali) ISO image with latest...
zpool import -o readonly=on -f POOLNAME
That was only command that worked for me... and I had to give that from live ISO image.
After that I could read the pool and copy images to safety.
Interesting thread. I was hoping for some better news.
Encrypted disk backup's are working allready but are basically in RAW format, so maybe thats not such a bad idea for migration. (My 2 cents worth.)
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.