Search results

So, I just had to go through this - but AFTER the image had been taken - so I could only boot into recovery mode... 1) You can remove the Xen drivers via Recovery mode using something like: X:\> dism /Image:D:\ /Get-Drivers Then look for the Xen drivers - they'll be listed as something like...

Ahhhh awesome - I did finally run across this - I just didn't quite understand what format I needed to pass the token in... I've got this configured properly now and allows us to use our deployment scripting for images from https://vorteil.io Now we can also do our normal shell scripts for...

Do you have any details on this? I've been hunting for documentation with no success... I'd like to pass an API token instead of a username / password etc...

I also note that when I change the MTU via 'ip' on the console, I get the following logs from Corosync: Oct 06 17:09:28 cbd-pm-2 corosync[9158]: [KNET ] rx: host: 1 link: 0 is up Oct 06 17:09:28 cbd-pm-2 corosync[9158]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1) Oct 06...

Thanks - I've proved that there's an issue and our networks guy is looking into it now - the following debug on hosts with 1500 byte MTUs seems to show an issue one way, but not the other: Going from 192.168.51.x -> 192.168.133.x with: ping -M do -s 1411 192.168.133.1 gives me: PING...

Hi all, This ones got me kinda stumped... I'm trying to build a total of 5 nodes in a cluster - but am getting stuck at three with issues I can't really explain. So far, I have 3 machines with the following IPs: 192.168.51.1 192.168.133.2 192.168.133.4 If I leave these all set to...

I just want to say - that I found myself in the same problem after relocating a node today into a different part of the network and having to change IPs etc etc... One correction to the above: killall $(pidof pmxcfs) should be: kill $(pidof pmxcfs) killall requires a name - not a pid -...

Heh, yeah - that's my site :)

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=3030

@fabian To me, this seems like it might be a proxmox bug - as the LV does become inactive when the CT is shut down. This means that the /dev/vm-storage/vm-100-disk-0 symlink disappears - which could well explain why blockdev can't examine it to get the size. Interestingly, I've noticed this...

Ok - stopped CT 100 on Node ID 1: root@cly-pm-tmp:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root pve -wi-ao---- 34.62g swap pve -wi-ao----...

Node ID: 1 root@cly-pm-tmp:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root pve -wi-ao---- 34.62g swap pve -wi-ao---- <4.88g...

As best I can tell, everything seems fine: root@cly-pm-1:~# pvecm status Cluster information ------------------- Name: proxmoxcluster Config Version: 2 Transport: knet Secure auth: on Quorum information ------------------ Date: Wed Sep 23...

Hi all, I've just created a new Cluster with 2 nodes, and am trying to migrate running CT's from one system to the other. Upon trying the migration, I get: 2020-09-23 15:11:52 shutdown CT 100 2020-09-23 15:11:55 starting migration of CT 100 to node 'cly-pm-1' (192.168.51.1) 2020-09-23...

Still good news: # uptime 05:17:47 up 16 days, 12:04, 4 users, load average: 0.25, 0.24, 0.48 # cat /proc/version Linux version 5.4.41-1-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.4.41-1 (Fri, 15 May 2020 15:06:08 +0200)

I just thought that I'd give some feedback since my last post. # uptime 02:43:41 up 7 days, 9:29, 2 users, load average: 3.86, 4.37, 11.04 This is a good thing. A question for the Proxmox folk if any happen to be watching - I noticed kernel.org is at 5.4.44 - but the latest proxmox kernel...

Annoyingly, I got another lock up today when on kernel: Linux proxmox 5.4.41-1-pve #1 SMP PVE 5.4.41-1 (Fri, 15 May 2020 15:06:08 +0200) x86_64 Text extracted from the photo: Welcome to the Proxmox Virtual Environment. Please use your web browser to configure this server - connect to...

You would need to adapt the mail server side script (not the PMG side) to reflect the correct paths / formats of your message store - whatever that may be... The concept itself should still work however...

Rejected means just that - rejected. There is no copy of this message ever stored on your mail server, or PMG.

I note that you don't need any tweaks above for normal proxmox operation. Having stability issues would cause me to check RAM, as you have and found errors, or set `Power Supply Idle control: Typical idle current` (or similar phrasing in your BIOS). You don't have to change anything further...