Search results

I had a ZFS event occur overnight, but never received the associated notification email. In the system log, I see the following: pvemailforward[3873]: mail forward failed: Insecure $ENV{IFS} while running with -T switch at /usr/bin/pvemailforward.pl line 36, <DATA> line 755. I am able to...

This is probably it - you need to add a rule in pfSense on vlan interface allowing outbound traffic.

For migrating linked clones, I found replication + manual move of the config files was easiest: https://forum.proxmox.com/threads/how-to-move-linked-clone-with-base-to-another-node.34455/post-343747

I found it much easier to setup replication jobs for the base & linked clones, then just move the lxc/qemu conf file from one node to the other. Goes without saying this would have to be an offline migration, and has to be done from shell instead of web GUI. For example: mv...

I was able to get this working, thanks to the corrections provided by @dcsapak and @MoxProxxer. Using your example, it would be: qm set 104 -args "-fsdev local,security_model=passthrough,id=fsdev0,path=/tmp/share -device virtio-9p-pci,id=fs0,fsdev=fsdev0,mount_tag=hostshare" This produces the...

Do you read an installation guide every time you install an OS? After I got the error, I actually did look up the min install criteria, and came here to note the issue with the incorrect defaults. Which have since been updated, so the point is moot. Thanks. Updating to 6.2-x changed the...

I am using proxmox-ve/6.1-2 and pve-manager/6.1-8, and it fills in 512MB as the default. I'll try updating to the latest (pve 6.2-1, pve-m 6.2-11). Sounds like it was fixed somewhere along the way. Thanks!

Same problem for me with an Ubuntu 20.04 server ISO. I used all defaults for VM creation, except for 2 CPU cores instead of 1. Bumping memory up to 1GB solved the issue for me. I think the default amount of ram for Proxmox VM creation needs to be bumped up to 1024 MB.

I have a related issue where i have decommissioned an old SSH key and would like to update authorized keys on each of my containers. I approached this by creating a 'foreach' loop for each container and using the 'pct push' command to copy the new auth key file. However, this only works for...

Reporting back - using a privileged container did the trick for me.

I am having the same issue! Please post your solution @fieraf

I don't see an answer here, but couldn't you just backup the whole LVM thin partition to a bulk drive, delete it, resize the system LVM, then recreate the LVM thin and restore the data? 240GB isn't that much to backup/restore these days. Unless you're trying to do all of this with the LVM thin...

I just encountered this symptom, then realized one of my LXC containers had 100% disk space usage (ZFS subvol). I was able to resize the disk in the web GUI, then the node & all running containers/VMs were restored to the normal green "play" indicator. No reboot was necessary. Edit: I'm...

Will do. I just upgraded BIOS on my other identical machine, so for now I'll move the Plex container over there. I'll report back if I see this again on the new BIOS rev. Thanks!

I just got this again (hasn't happened since my initial post on Oct 7, 2018). I've updated the PVE kernel since the initial post, but looks like there is another update waiting for me. I'm on 4.15.18-11-pve as listed in the trace entry here: Mar 20 04:24:51 pve1 kernel: BUG: unable to handle...

Thanks for the reminder; I frequently forget to stay updated unless something breaks or I'm looking to implement something new. I'll re-post if I see this again.

Hi, I've started using Proxmox about 6 months ago and have been loving it. Last night, I found that my Plex container was not responding. All other VMs and containers were fine (only 2 others on the machine). I was able to login via SSH and found the following in the journal: Jan 13 01:24:13...

For anyone that's interested, here's an archived thread that discusses the drawbacks to the pve-patches tool (with admission by the author that it's not ideal for integration into Proxmox): https://pve.proxmox.com/pipermail/pve-devel/2014-September/012771.html