Search results

It's worse than that. I documented getting it working here https://forum.proxmox.com/threads/issue-proxmox-crashing-randomly.101660/post-448261 Turns out even with the workaround, apt update fails with kdump-tools installed (and ZFS on /). :( So I tried to uninstall kdump-tools. I've now...

Sorry, I do not know what "kernel headers" are, nor for what version of what I need them ;) I'd love to do this the "right" way before attempting the alternative...

BLEAH. NOT fully solved: With kdump-tools installed, apt update (and autoremove and more) fails 100% of the time apt remove kdump-tools / apt purge kdump-tools fails to fully uninstall kdump-tools I have edited my kdump-tools info above. I don't consider this fully resolved. My system now...

Thanks. Yep, everything appears to be fixed now. That was quite the outage!

na.cdn.proxmox.com I get a different response - denied - with af...co and eu...co Any other alternatives? Still dead this AM from MOST of the USA https://lookingglass.centurylink.com/ - Eastern seaboard (MA, MD, GA) are ok - Everything else in the USA is not working

download.proxmox.com is dead right now. I have set up a worldwide ping monitor, in case staff are interested... * From OH, DE, TX all appears well * From Melbourne, slow but working * From my phone ISP - yes * From my local (Century Link) ISP - no connection Perhaps an internet backbone outage...

Tried apt autoclean - ok apt autoremove - BAD A guess: updates don't support kdump-tools? I'll try removing that next...

On the LAN side, each accessible LAN interface requires both: * A shared CARP IP, that switches back and forth (I use *.1) * A unique IP for that interface (I use *.2 for primary and *.3 for secondary) Since pfSense supplies DHCP and local DNS, that's pretty easy. On the WAN side, a) it's...

Follow the pfSense CARP cookbook carefully. The MOST important thing by far: all network devices must be in the exact same order internally to pfSense, as that is the assumption for sync. If that's a problem, there's a workaround using LAGGs. If you end up having to reconfigure network...

I provided the update log above. From that log, it looks like the autoupdate (initiated in the GUI) *tries* to remove old versions... but it didn't do anything? ALSO: I find no documented way to examine nor discover the status of the /EFI partition? Here's my proxmox-boot-tool info:

I just attempted an update, which failed pretty miserably. I note that a LOT of old versions are still hanging around... is that an issue? End of errors: Below: - pveversion -v Attached: - captured live errors - mount - cat /proc/mounts Anything else? pveversion -v [See attached for...

I'm using HA CARP which is built into pfSense... in my case on 2 proxmox VM's. This has some advantages over vm migration. Most particularly: CARP maintains a live backup of all connections. Rather nice when a cutover maintains all connections. Do you have 2+ WAN connections? If so, it's...

I have a functioning ProxMox cluster, including: * Two hosts plus a QDevice * pfSense routers on each (synced CARP primary and backup/mirror) * plus some VM's on each Each box has a dedicated port for the host, using my primary subnet. To date, the hosts know nothing about VLANs. Each box has...

I've got a 2-node Proxmox cluster + QDevice (on a tiny raspberri pi ;) ) All is working well. pvecm status correctly shows everything I can't find anything in the GUI to hint that a QDevice exists or is present Am I missing something, or is this simply missing from the GUI? I'm thinking it...

Oops. I'm not the OP on this thread. I apologize!

SOLVED.... what a relief! I had already run memtest, and the RAM had passed. Yet... memtest86 has been radically strengthened since I last made my bootable copy. Using the latest version? Bad RAM. Pull that RAM (still have 8GB, enough for now) and all is wonderfully well. H/T @kalasnikov for...

Will do. FWIW, there are a number of new distracting error messages-on-boot-or-crash that appear to be just that: distractions not worth focus... ...no irq handler for vector ...BIOS has corrupted hw-PMU resources (MSR 38d... ...DMA failed to allocate 128 KiB GFP_KERNEL [GFP_DMA pool for atomic...

Unfortunately, fixing my filesystem did not fix the original crash-on-backup issue. Not only that, I saw on the console some disturbing messages fly by, about kdump not supporting the current kernel, so the dump wasn't complete... (...and another error saying something about a BIOS bug...

@oguz, The good news: fixing zfs filesystem error took care of crash-on-gzip. (There is bad news in another message :confused:) The following info is not currently listed in Proxmox documentation that I can see... So I wrote it up :) Current HowTo: Managing filesystem issues with ZFS on Proxmox...

Thanks! (I updated the instructions with a more general crashkernel param, and a link to some documentation. Have not found ubuntu-specific info, nor any details of what actually affects the reserved RAM size. This works for me...) I know how to handle disk issues; not used to reading Oops...