Recent content by TheMaskedCrusader

Ok, I've flashed my bios and updated proxmox on both my servers in the cluster. Now we wait to see if the problem goes away. I recently rebuilt this server, and in so I replaced the ram with Kingston sticks (4x8GB). The "Server" is a repurposed desktop system with dated hardware (4th Gen I7...

Well, I have updated both my servers to the latest version using distupgrade and everything was running swimmingly for 1.6 million seconds. Then the second node crashed again! I'm currently looking for alternatives to proxmox, since I can't figure out this problem, and crashing every two weeks...

So, this is a strange thing, It starts fine, and the pvestatd service will continue to run for about 3 days. But around the 225000 second mark, something crashes that kills the pvestatd service. I'll check dmesg when it crashes again to try to determine what the failure is. I really don't want...

It's a problem with pvestatd, not zfs. I'm not running ZFS. Here's what I get when I check the status of pvestatd: root@node02:/var# systemctl status pvestatd ● pvestatd.service - PVE Status Daemon Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)...

This results on a gray questionmark on the node in the ProxMox user interface.

I used to be getting kernel panics for the e1000e network card, so I replaced my network card with a Broadcom from amazon. I thought that fixed it, but I am continually getting kernel crashes. I ran an `apt-get update && apt-get upgrade` today to try to get rid of them, but they're still coming...

Mine is doing that too, for some reason pvestatd is crashing, causing the issue. I'm still researching the cause. I wrote the following script to keep the daemon alive and slapped it in crontab. kinda like a watchdog, but without having to configure that beast. #!/bin/bash # Keep the PVE...