Search results

I had this issue with a previous version and was able to get it running with the following. This is copied from my previous post here: This is what I did to get around the issue: 1.) cd /tmp 2.) Download the link from above (also here) 3.) tar -xvpf ixgbe-5.7.1.tar.gz 4.) cd ixgbe-5.7.1/src...

OK. I'm not totally sure. Once you compile it and if it all goes fine, then you should be good. Try a reboot again and see if it registers on your system.

I'm not sure, but you might need different firmware that what I used for my 10GB Cards. The firmware that I pointed to was for a RJ-45 10GB Intel card. The supported cards are: The driver is compatible with devices based on the following: * Intel(R) Ethernet Controller 82598 * Intel(R)...

Did you try and run a apt dist-upgrade to see if that helps you?

Did you install install this: You might need to reboot your host once you have done this in order for it to see them

Yes. See post #9 in this thread for the resolution.

Hi all, I am all of a sudden having an issue with backing up LXC containers on my nodes. I have a couple of servers in LXC format and since a couple of days ago they are all displaying issues when running a backup. Haven't run any updates in a bit, but the nodes also show that there are no...

Hi all, I'm trying to figure out how to have my virtual hard drives run efficiently on thin provision volumes. I have a 4 node setup with all 10GB Backend for VM's and Containers mounted on each node. The storage is mounted via NFS The backend storage (Various QNAPs) are all created as thin...

With all the spam going on in the world right now, I am seeing more companies that I email into prepend their messages in the body with something such as: CAUTION: This email originated outside of SOME COMPANIES email system. DO NOT click links or attachments unless you recognize the sender and...

Thanks. I don't see anything pertaining to anything stopping in the logs. I don't believe that it ran out of memory, but I've up the RAM on each server so we'll see if it tailspins after that. I'm actively monitoring it now.

Hi all, This morning I had an issue with my PMG server where it went deaf and stopped delivering emails to end email addresses. I use it as a smart host. Its built off of the Proxmox LXC container and its running on a Proxmox Server in a cluster. The server in the syslog went from working to no...

Wonderful! Thank you for the clarification!

From the help section: When I am setting this up inside of a firewall thats has multiple VLANS attached to it, do I need to add this on each vlan? So for instance, do I need to do the following: ethtool -L eth0 combined 8 But then do I also need to add this to all the VLANS as well: ethtool...

This has done the trick for me by doing this on each node. Its seems my ghost node is now gone (seemingly). So thats amazing. Thank you for the awesome help. systemctl stop pve-ha-crm.service rm -f /etc/pve/ha/manager_status systemctl start pve-ha-crm.service I just have one last question...

I'm not sure what happened. The node died and then I pulled it out of the rack and then I ran the pvecm delnode, and removed it. It never gave an error. Am I able to edit that file or do I have to run the 3 commands below to clear this issue up...

I might also add in my logs that I am seeing this error on each node: pveproxy[2464]: unable to read file '/etc/pve/nodes//lrm_status'

Thanks I've tried both those options except stopping it on all nodes. so I just run this on each node then: systemctl stop pve-ha-crm.service rm -f /etc/pve/ha/manager_status systemctl start pve-ha-crm.service What are the implications in doing this on my nodes while its live? Will any of the...

So, I can take it from this: totem { cluster_name: vdc-cluster config_version: 6 interface { bindnetaddr: 172.16.1.2 ringnumber: 0 } ip_version: ipv4 secauth: on version: 2 } and change it to this: totem { cluster_name: vdc-cluster config_version: 7 interface { ringnumber: 0 } ip_version: ipv4...

Never mind, I found the solution to my issue. After running an update to the hosts, I needed to reboot the hosts to see all the new header information. Sometimes I'm amazed that I have the brain capacity to tie my own shoes given how stupid I am.

I'm not seeing this issue pop up again since running an update to my node. I now have pveversion pve-manager/6.1-7/13e58d5e (running kernel: 5.3.13-2-pve) This error is now popping up on my 2 nodes: ixgbe 0000:03:00.0: Warning firmware error detected FWSM: 0x00000000 Trying to run the make...