Search results

you probably want to do an apt dist-upgrade instead of an apt upgrade. it's never let me down and it's also what folks more knowledgeable than me will tell you to do. :) Upgrade ensures that packages aren't removed or if they cause the upgrade of another package won't be upgraded...

IIRC, the host you're trying to join to the cluster cannot have any VMs. I've read that people backup and restore their VMs once the server has joined the cluster.

I went ahead and compiled the driver from source and the errors went away. Have you thought about installing DKMS to keep the driver current with each new kernel release?

I get these errors as well. Though, for me, they don't appear to be causing any issues. I just filter them out so they don't make it to my logfiles and just put up with the syslog spam.

I pushed through the upgrades and so far everything is working well. Still have the error spamming the kernel ring buffer. I did change rsyslogd to not log those lines in /var/log/kern.log at least so those aren't filling up. My guess is that I'll have to see if there's firmware for the x520...

Anyone else using Intel X520 10Gbit cards? I'm in the middle of upgrading my three nodes to v6 and while everything appears to be going very, very well, checking kernel logs reveals: ixgbe 0000:03:00.0: Warning firmware error detected FWSW: 0x00000000 It doesn't appear to cause any issues...

While we don't use Proxmox, we do disable c-states on all of our AMD servers (Opterons and EPYC) Hopefully it's what's causing your grief. Good luck!

I'd edit root's crontab (crontab -e) and add them via: @reboot /path/to/script I do the same for scripts to let me know if a host reboots, I get a page via Pushover

Try the command from your other node. That's what I need to do when I get that error.