[[SOLVED] Server No Longer Connects to LAN After 6.10.x OS Upgrade (TIFU)]

13 hours ago, JorgeB said:

Was just going to post that if the NIC was being blacklisted the driver won't appear, if you don't mind please post the diagnostics just to check your hardware.

 

Certainly- 

dellt3500-diagnostics-20220529-0029.zip

[[SOLVED] Server No Longer Connects to LAN After 6.10.x OS Upgrade (TIFU)]

After reading this thread, I solved my issue by disabling VT-d in the BIOS. I assumed that I wasn't affected based on on the fact I could not find any tg3 drivers. Sorry for making yet another post on this issue!

 

[[SOLVED] Server No Longer Connects to LAN After 6.10.x OS Upgrade (TIFU)]

I'm pulling my friggin hair out over here after blue balling myself. I've searched everywhere and just can't find a solution.

 

Earlier this week I upgrade my ole Dell Precision T3500 from 6.9 to OS version 6.10.1. Upon reboot I immediately began facing connectivity issues.

 

Servers ran headless since 2018. Where I'd usually interface with it all through the web GUI, this time around I was completely unable to connect to it at through a local 192.168.1.x address. Pings to the unraid address from my main workstation and other computers on my local network would return "destination host unreachable"

 

So I plugged in a monitor, keyboard and mouse and booted in GUI mode to diagnose the issue.

 

Before I continue, I want to give everyone more background info on my network. The setup between the server and my router that had previously been working up until the upgrade to 6.10.x:

• Unraid had a static ip set to a 192.168.1.x address
• Bonding enabled "active backup(1)"
• Bridging enabled
• Default gateway and DNS servers pointing to my router (NETGEAR Router R8000P)
• There's an address reservation on my router for my server address

 

From unraid I could not ping my router or any other computers on my network. I would get the same error "destination host unreachable".

 

I tried switching to DHCP with no luck. Unraid could not resolve an IP address. 

 

Digging into the issue, I had read somewhere that people with similar issues (not specifically with 6.10.x) resolved it by disabling bonding. From what I can recall, bonding had always been enabled as an "active backup (1)" on my server, despite only having 1 NIC.

 

Disabled bonding and boom! Even when I had unraid set to DHCP it immediately set itself up with its old local ip 192.168.1.x address.

 

Swapped unraid back to its old static IP 

 

Now here's the FU on my part. I'll admit I have a problem when it comes to updates.

If I see a new stable build on an OS/Application I'm running I'll update it.

 

And as many of you know unraid 6.10.2 released yesterday.

 

My dumbass decided at the end of my troubleshooting mess, to update the OS again. 😭

 

Now I'm facing the same issue- except this time bonding had been disabled from before and it wasn't getting me out of jail.

 

Swapping from static to DHCP resolves a 169.x.x.x address. Which I think means unraid is unable to resolve it's own address on my network.

 

Pining to and from the server, I receive the same error "destination host unreachable".

 

I thought maybe my NIC was being blacklisted because it was maybe running broadcom tg3 drivers. However,

lsmod | grep tg3

shows no results.

 

I've tested the LAN cable with a laptop, assuming a bad cable. It works fine.

 

I've ordered a replacement NIC ($10 on ebay) in case that's the issue and the hardware's gone bad.

 

I've deleted the address reservation on my router for the 192.168.1.x address my server had reserved. No luck

 

Aside from what I've tried above- can anyone think of any other fixes or tests I should try?

 

Also- I'd like to be able to upload my config/diag dump file for everyone to take a look at, but I'm not sure how. The OS USB is seemingly unreadable on my windows machine, even with 3rd party data recovery and disk reader tools like Diskinternal's Linux Reader and UFS Explorer. And Without the ability to connect to my network, I can't SSH into the machine to grab them.

 

Any guidance on what I can try next to troubleshoot the issue or info on how I can get my diag files would be greatly appreciated

[[Support] sgraaf - obfs4-bridge]

Thanks for the awesome template. Quick question; I keep getting a warning in my logs that says...

 

Sep 01 04:49:30.000 [notice] Unable to find IPv6 address for ORPort 9393. You might want to specify IPv4Only to it or set an explicit address or set Address. [59 similar message(s) suppressed in last 3540 seconds]

I went back to edit the container because I remembered seeing a config to disable IPv6. Key value: OBFS4V_AddressDisableIPv6. The default is set to 0 which I assumed meant false.

 

Anyway I set the value to 1 and I'm still receiving the warning. I figure its probably not a big deal, but do you know what value I need to set to disable IPv6 routing?

 

Thanks

EDIT:

I figured out my issue after viewing the dockerhub project:
 

Quote

 

4. Advanced usage

You may set additional torrc variables in your .env file by setting OBFS4_ENABLE_ADDITIONAL_VARIABLES to 1 and prefixing the desired torrc options with OBFS4V_. For example, to set the AddressDisableIPv6 option, include the following lines in your .env:

OBFS4_ENABLE_ADDITIONAL_VARIABLES=1 OBFS4V_AddressDisableIPv6=1

 

 

 

I left the default variable "enable additional variables" set to 0. Both needed to be 1. 👍

 

 

 

[[Plugin] Nvidia-Driver]

On 3/31/2021 at 12:37 AM, ich777 said:

For what? You can't use your cards in Docker containers with the old driver. As said the container tools that are necessary only support Kepler and newer.

Do you know if its possible to pass them thru to a VM if I can't use docker?

[[Plugin] Nvidia-Driver]

3 hours ago, ich777 said:

To use the card in Docker containers you have to be at least on Kepler and your card is Fermi based so to speak you can't use this card in Docker containers because it's simply too old and not supported by the driver.

 

Visit the link that you have linked in your post (this is also the link in the first post to the supported cards) and you see a list of cards when you click on the corresponding driver (I know currently the driver version 465.19.01 isn't listed there but you can click on the latest that is available version 460.67 - this is actually the same list and applies to newer drivers as well).

 

Am I out of luck for both of the cards then? Is it possible to use the NVIDIA 340.xx Legacy drivers as mentioned in the logs?

[[Plugin] Nvidia-Driver]

Following the installation I ran into the dreaded "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver."

 

I do not believe there is an issue with the hardware, and I've made sure that neither of the two GPUs are bound to VFIO (they do appear in the PCI Devices and IOMMU Groups under System Devices in Unraid.)

 

Another odd thing I found while following along SpaceInvader One's setup video (utilizes this plugin) was that after I added the "GPU Statistics" plugin none of my GPUs appeared on the dropdown list:

 

 

While debugging this issue I made sure that the settings in my BIOs we're OK and during a reboot I decided to check the system logs and saw this:

 

Which reads 

Quote

 

Unregistered the Nvlink Core, major device number 246

Nvlink Core is being initialized, major device number 246

The NVIDIA Quadro 4000 GPU installed in this system is supported through the NVIDIA 390.xx Legacy drivers. Please visit http://www.nvidia.com/object/unix.html for more information. The 465.19.01 NVIDIA driver will ignore this GPU. Continuing probe...

 

 

Could this be a part of my issue?

 

Thanks for all your help 😃

[[Support] ich777 - Gameserver Dockers]

12 hours ago, ich777 said:

If your Router/Firewall doesn't support NAT Reflection then you can't connect from your local network with your PUBLICIP:2457, I would first try to connect to with your LOCALIP:2457

 

If you forwarded the ports correctly in your Router/Firewall 2456-2458 UDP (and only UDP) then you should be able to connect to the server from outside with PUBLICIP:2457

 

 

Was the server running before because I see you are using a old template, version of the Container, if it was running before eventually you are affected by the world destroy bug (I built in a backup function in the Container so that you can restore the world if needed - see the second recommended post in this thread on the top for more information).

 

I had downloaded the old template before but could never get the server working.

After seeing you say I had an old version I just removed the container / files completely and re-downloaded from the community app store. Used all of my old settings and it instantly started up 😃

Thanks so much again!

[[Support] ich777 - Gameserver Dockers]

Hi and thank you so much for the container! I'm having an issue connecting to my Valheim server.

 

I have forwarded UDP ports 2456-2458 to my unraid server

 

Here's the log 10-15mins after starting the container:

 

---Checking if UID: 99 matches user---
---Checking if GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation
-- type 'quit' to exit --
Loading Steam API...OK.

Connecting anonymously to Steam Public...Logged in OK
Waiting for user info...OK
Success! App '896660' already up to date.
---Prepare Server---
---Server ready---
---Starting Backup daemon---
---Start Server---
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 2 milliseconds to initialize
CApplicationManagerPopulateThread took 0 milliseconds to initialize (will have waited on CAppInfoCacheReadFromDiskThread)
RecordSteamInterfaceCreation (PID 68): SteamGameServer013 /
RecordSteamInterfaceCreation (PID 68): SteamUtils009 /
Setting breakpad minidump AppID = 892970
RecordSteamInterfaceCreation (PID 68): SteamGameServer013 / GameServer
RecordSteamInterfaceCreation (PID 68): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 68): SteamNetworking006 / Networking
RecordSteamInterfaceCreation (PID 68): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 68): STEAMHTTP_INTERFACE_VERSION003 / HTTP
RecordSteamInterfaceCreation (PID 68): STEAMINVENTORY_INTERFACE_V003 / Inventory
RecordSteamInterfaceCreation (PID 68): STEAMUGC_INTERFACE_VERSION014 / UGC
RecordSteamInterfaceCreation (PID 68): STEAMAPPS_INTERFACE_VERSION008 / Apps
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.
RecordSteamInterfaceCreation (PID 68): SteamNetworkingUtils003 /
RecordSteamInterfaceCreation (PID 68): SteamNetworkingSockets008 /

 

Here's a picture of my docker setup:

 

Any suggestions? I tried connecting to the server through the steam server viewer with <PUBLICIP>:2457 and <PUBLICIP>:2458