Search results

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...

Well, as another data point for you, I have a Ryzen 3900x in an MSI X570-A PRO mainboard, and 64Gb (4 x CMK64GX4M4B3200C16) DDR4 RAM at work, currently running Xen. With the X570 architecture and the 3000 series Ryzen, this RAM runs at 3200Mhz @ 1.2v simply by just setting the XMP profile in...

That'd do it as well... Just make sure you keep them in pairs and keep the timing / speeds matched to the slowest ones in the group. I have a Ryzen 2700x that I use for my desktop - that has 32Gb of 3200Mhz RAM and seems to have issues if I set it to 3200Mhz. Setting it to 3133Mhz seems to be...

Maybe I'm mistaken, maybe it is 125Hz.... It's been many years since I looked at the USB spec...

So, I worked with the AMD guys a while ago when this was a new issue with a newly released AGESA version... The big thing that can cause instability is if your ATX power supply goes flakey when there is a small load on one of the supply rails. The BIOS option for "Power Supply Idle control" is...

It emulates a USB tablet as a mouse - as that's more accurate for VNC tracking of the cursor. As its a USB device, it gets polled at ~1000hz. That's the CPU usage you see.

Here's another good example of BAYES catching stuff that other rules did not: X-SPAM-LEVEL: Spam detection results: 7 BAYES_99 3.5 Bayes spam probability is 99 to 100% BAYES_999 0.2 Bayes spam probability is 99.9 to 100% HTML_MESSAGE...

Correct: [63241.054338] i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 2.8.20-k [63241.054340] i40e: Copyright (c) 2013 - 2019 Intel Corporation. I'd guess you'll have to rebuild the newer module, or wait until it gets shipped into the upstream kernel as a newer version.

I'm guessing the UTC time you have set is correct as the local time - so when the timezone conversion happens, you end up getting the timezone correction twice... Make sure your BIOS time is in UTC and try that...

On a similar topic, are there any plans to add support via Prometheus?

That'd be why.