Search results

I believe I've just run into this on a machine where the uplink is 2x 1G in a LACP. Something not playing nice in openvswitch? Edit: Interestingly one of my machines has the problem, the other one doesn't seem to, trying Linux Bridge instead of OVS on the one with the issue.

Seems not to have gotten overwritten so hopefully that's done it Whilst I can't say 100% I didn't put a static IP in that file, (Container was setup a while ago) it would be strange for me do so given 18.04 usually uses a Yaml file in /etc/netplan.d/ for a static config.

root@lenovo:~# pct config 119 arch: amd64 cores: 2 hostname: pihole1 memory: 1024 nameserver: 8.8.8.8 8.8.4.4 net0: name=eth0,bridge=vmbr0,gw=10.0.232.1,hwaddr=8E:66:CF:26:74:4A,ip=10.0.232.99/24,tag=101,type=veth onboot: 1 ostype: ubuntu rootfs: SSD2:vm-119-disk-0,size=20G swap: 512...

I have a Ubuntu 18.04 LXC container running on Proxmox 5.3-11 that likes to pickup the wrong gateway, essentially the container won't be able to access the internet and I'll find it's default route is pointing at 10.xxx.xxx.254 instead of 10.xxx.xxx.1 However in the networking config for the...

Need some recommendations for backing up an Unprivileged LXC container that's on an Iscsi LVM and managed by HA manager to an target that's an NFS share. Snapshot fails because of permissions issues, Stop doesn't want to work either because vzdump won't auto stop a VM managed by HA. The common...

If I have 2 proxmox servers on the same network but one is AMD and the other is INTEL can I still cluster them? Not interested in HA but it would be nice to be able to manage them both from the same WebUI session.

But why is it even looking to delete them?

Now to me trying to delete /usr/local or /usr/local/share seems like a really bad idea!

As per topic title really, if you try to create a large (I.e Several 100's of GB) mount point for an LXC container on a slow storage (Such as HDD) the job can timeout because the image is still being created. Ideally this should be backgrounded similar to the vm/container creation jobs Edit...

Made it privileged and it backed up ok. Only data in it is a config file for a RA proxy it's running.

I guess I should just make it privileged now then?

Any ideas, I'm guessing it's probably because I toggled it privileged (in the config file) to do an update in the container and then set it back to unprivileged and now some files have the wrong ownership or something like that

I set unprivileged 0 in the containers conf file, did the update and then set it back to 1 but I'm not sure if that's really a good idea or not.

[root@smokepong ~]# yum install httpd Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: centos.serverspace.co.uk * epel: mirrors.coreix.net * extras: mirror.sov.uk.goscomb.net * updates: centos.serverspace.co.uk Resolving Dependencies --> Running transaction check...

4.4-1/eb2d6f1e Resolving Dependencies --> Running transaction check ---> Package epel-release.noarch 0:7-6 will be updated ---> Package epel-release.noarch 0:7-8 will be an update ---> Package filesystem.x86_64 0:3.2-20.el7 will be updated ---> Package filesystem.x86_64 0:3.2-21.el7 will be an...

Or if you DO want everything tagged load the 802.1Q module and create a vlan subinterface and put the management IP for proxmox on that.

Proxmox's own traffic is usually untagged, unless you specifically put the IP interface on a Vlan with a 802.1Q kernel module loaded. You probably want the Switch port (Or LACP/Bonding/Trunk/Portchannel/Whatever HP want to call it this week) in hybrid mode so that any untagged frames are put...

4.4-1/eb2d6f1e 127.0.0.1 localhost.localdomain localhost 109.xx.xx.xxx pve-rs1.mydomain.net pve-rs1 pvelocalhost # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2...

Hmm UEFI is the latest, however I changed some settings to do an EFI boot and disable the CSM and proxmox was then able to reboot the machine. I'll give it a few mins and then try again incase that was a one off. Edit: Looks like it's possibly a problem with the Legacy/Bios mode on that board.

No poweroff hangs as well I'm not sure on the UEFI version i'll hookup a screen and see if it needs an update