Search results

I switched to NIST time servers in boulder (not far from where I live), restarted/updated my time sync service on all nodes one after the next. All my clock skew issues went away after that. I also see the timesync updates in syslog on node reboots now, which also likely helps a lot. Good change!

There's nothing wrong with a 4 node cluster. You have a "perfect" cluster for 1-node failure without loss of quorum. Having a 4 node cluster with all 4 nodes hot to step in for a node failure is better than a 3hot+1cold cluster any day. If the 4th is cold, and you loose a node, then you loose...

I don't understand your point. If the internet connection goes down, there's not going to be any way to remote in to fix it regardless. Being virtualized doesn't change this. If you're making changes to your firewall configuration "remotely" to a site with a single internet connection that's...

I suspect more people do this than you think. Some of us like to live on the wild side ;) proxmox doesn't just stop working without a gateway, it just looses access to updates and time servers. It can go awhile without either in most cases. You could just boot the last backup of pfense? I...

Few tips for what you're trying to accomplish: 1. I see nothing wrong with virtualization your router, especially if you're already inside another private network anyway. if you bork up your pfsense VM and need internet for proxmox, you can always give proxmox an IP on the "WAN" (private school...

It produces thousands of these heartbeat: no reply logs in the 30 minutes before forced shutdown. It's like, ceph didn't get the "we're shutting down" message or something.

Syslog from a shutdown sequence:

Hello! I've been running proxmox on my 4-node homelab cluster of X9 generation supermicro fat-twins for a couple months now. All has been pretty well until recently, the nodes don't want to reboot/shut-down anymore. Not sure what triggered this, might be latest updates? I get these "A stop job...

I'm having the same problem across all VM's on a newly created proxmox 6.1 cluster. A soft-reset triggers use of the set resolution, but any "cold" boot of any OVMF-UEFI VM gets 800X600 resolution, ignoring the settings in OVMF.

I'm having a similar (likely the same) problem. I can adjust the resolution in OVMF settings, but this resolution will ONLY work when a reset is issued from this UEFI config interface or after a reboot of the VM. Any "cold" boot of the VM (non-restart/reset/reboot) results in 800x600 resolution...

Gentle bumperoo?

Hey there, ------------------------ Context: Final planning phase for storage configuration on a proxmox+ceph cluster. I've ordered 4 X SuperMicro 2113S-WTRT, 7402P, 256GB RAM, 64GB SATADOM for boot, X710-T4 for 10G ethernets. I'll be adding 1-2 more nodes when we move to a new facility...

Just an FYI: I had the same problem in both a BIOS and UEFI configuration of pfsense. The screenshot gerby posted looks familiar. Yep.

Hi Kubicz, You probably know more about this than I, but in my brief experience virtualizing pfsense, the only way to get AES instructions exposed to pfsense is to run it this way. Similarly, I seem to recall enabling "nested" capabilities in virtualbox to provide the same functionality to...

Had the same problem today on my beginnings of a homelab... I had just put the no-subscription apt source in /apt/sources.list and ran updates/upgrades/dist-upgrade. According to apt logs, Kernel 5.0.21-10 was installed as part of those updates. After rebooting the host, Pfsense refused to...

I think we're on the same page here ;) Though, I have a hunch almost any modern non-QLC 2TB drive would still be far better than putting the DB on the spinners. We're not going to have small files on the spinners anyway, so might not matter much. The spinning pool is for archive of large files...

Thanks WolfGang!! Excellent information. Thanks for the link. I probably skimmed over that ~4% of block size detail a few times reading about this but missed it every time. I see the SAMSUNG 983 DCT and Micron 7300 Pro as possibilities bearing the "enterprise" marketing wank, but notice the...

I suspect that the memory "usage" from Proxmox's perspective and pfsense's perspective are different because those "bars" are counting "used" memory in different ways. If you give a modern OS a bunch of free RAM, it will use RAM as "cache" space. Pfsense is no exception to this. Some pfsense...

Curious.. does this difference show up both in snapshot mode and stop mode backup operations? Or only in snapshot mode backup?