Strange behaviour of Unraid

[wallis]

I added extra RAM this morning so I shut down Unraid, powered off, reset RAM speeds in the MB Boot record and powered up and restarted Unraid.

 

Now I find that I cannot connect to the server for certain programmes . My server is on 192.168.2.19 - and I can't get  to the Main, Dashboard or Plex pages.

 

However, the strange behaviour is that I CAN connect to Unmanic, SAB, Radarr, Sonar using the same server credentials.

 

So 192.168.2.19/Main doesn't work, whereas http://192.168.2.19:8080 (SAB) does.

 

Can anybody throw any light on what is happening?

 

Thanks

 

Wallis

[trurl]

attach diagnostics to your NEXT post in this thread

[wallis]

Sorry, I’m a newcomer to all this. Where can I find the diagnostics and how do I run them?

[trurl]

The word diagnostics in my post and your post and in this post is a link explaining how to get your diagnostics.

[wallis]

To get to Tools:Diagnostics, I think I'd have to access the Main screen and then select Tools from there.

 

But I can't access the main screen - it simply says it can't connect to 192.168.2.19 - although it does access that IP if I go to Radarr, Sonarr, SAb, Deluge etc - i.e. it opens Radarr with http://192.168.2.19:7878

 

Wallis

[JonathanM]

7 minutes ago, wallis said:

I think I'd have to access the Main screen and then select Tools from there.

Direct quote from the link.

Quote

If the GUI cannot be accessed for any reason then using the diagnostics command from the Linux level will generate the same information and put the resulting zip file into the logs folder on the flash drive.

Can you attach a screen and keyboard to the server? Can you ssh in to the server's IP?

[wallis]

To get to Tools:Diagnostics, I think I'd have to access the Main screen and then select Tools from there.

 

So I've managed to SSH into the Server and run the Diagnostics using the following command:

root@wd:~# diagnostics

Starting diagnostics collection... done.

ZIP file '/boot/logs/wd-diagnostics-20220729-1821.zip

 

So we have a diagnostics zip file but my next problem is - how do I get to the directory to get the zip file?  I'm not used to Linux so I don't really know the terminal commands

 

Wallis

[JonathanM]

58 minutes ago, wallis said:

how do I get to the directory to get the zip file?

At the SSH prompt, type powerdown

When the server shuts down, remove the flash drive and put it in your computer and open the logs folder on the flash drive. Attach the zip file as it is to your NEXT post in THIS thread.

[wallis]

Jonathon - Thanks so much - your help has been fantastic. I've enclosed the diagnostics log file - I had no idea it was on the USB boot drive!  I hope this will help you sort out what is wrong - I love UnRaid but have a very superficial knowledge of Linux - I'm 76 so I never bothered to read the manual - hell, I don't even buy green bananas these days!

 

Wallis

wd-diagnostics-20220729-1821.zip

[trurl]

7 hours ago, wallis said:

My server is on 192.168.2.19

What is the IP address of the computer you are trying to use to access the Unraid webUI?

[wallis]

The MBP is on 192.168.2.10 and the Router is 192.168.2.1

 

[trurl]

8 minutes ago, wallis said:

The MBP is on 192.168.2.10 and the Router is 192.168.2.1

 

Jul 29 13:31:04 wd dhcpcd[1122]: br0: soliciting a DHCP lease

Jul 29 13:31:16 wd dhcpcd[1122]: br0: offered 192.168.2.19 from 192.168.2.1
Jul 29 13:31:16 wd dhcpcd[1122]: br0: probing address 192.168.2.19/24
Jul 29 13:31:20 wd dhcpcd[1122]: br0: leased 192.168.2.19 for 259200 seconds

Jul 29 13:36:26 wd kernel: r8169 0000:22:00.0 eth0: Link is Down

Jul 29 13:36:27 wd avahi-daemon[8867]: Withdrawing address record for 192.168.2.19 on br0.

Jul 29 13:36:31 wd kernel: r8169 0000:22:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx

Jul 29 13:36:31 wd dhcpcd[1122]: br0: rebinding lease of 192.168.2.19
Jul 29 13:36:32 wd dhcpcd[1122]: br0: NAK: requested address not available from 10.0.4.1
Jul 29 13:36:32 wd dhcpcd[1122]: br0: message: requested address not available
Jul 29 13:36:32 wd dhcpcd[1122]: br0: soliciting a DHCP lease
Jul 29 13:36:32 wd dhcpcd[1122]: br0: offered 10.0.4.30 from 10.0.4.1
Jul 29 13:36:32 wd dhcpcd[1122]: br0: probing address 10.0.4.30/22
Jul 29 13:36:36 wd dhcpcd[1122]: br0: leased 10.0.4.30 for 14400 seconds

 

Any idea what 10.0.4.1 is?

[wallis]

You're not going to believe this - 10.0.4.1 is the modem for the home security system!  When I powered down to install the extra RAM, it was the first time the computer had been shut off for 2 years - shows how reliable UnRaid is!.  On restart, it seems to have locked onto the wrong network. So this morning, I temporarily shut off the HomeSec Modem and when I rebooted the UnRaid server, it linked straight in to 192.168.2.19. So we're back online thanks to your, and Jonathan's great help.

 

Is there a way I can "lock in" the correct start IP - would that be a Static IP? - in UnRaid. That would avoid this question in the future.

 

Thanks again

Wallis

[JorgeB]

26 minutes ago, wallis said:

Is there a way I can "lock in" the correct start IP - would that be a Static IP?

Yes, Settings -> Network Settings -> IPv4 address assignment -> Static then set the IP

[JonathanM]

1 hour ago, wallis said:

On restart, it seems to have locked onto the wrong network.

This is going to be an issue for any device on the network, as both routers are advertising their services and any device looking for a DHCP address is going to find whichever router responds first, and when the DHCP renewal period expires it may well switch to the other network.

 

Do you have multiple full time WAN connections available? Or is the security modem supposed to run off the main internet and fall back to a cell provider if the main WAN is out? If that's the case, then only the security system itself should be connected to the LAN side of the security modem, and the WAN side should go to the LAN connection of the main internet.

 

Bottom line, you need to get this working properly or it will be an ongoing issue, and depending on how things are configured you may get a nastygram from your security company about the use of the backup network for things other than the security system.

[wallis]

I checked with the Security Co - it turns out this is a residual device installed by the previous company who ran the security system off copper and used the modem as a backup. I switched companies a year ago ass the new system is fiber which uses a cellular backup. So the modem is surplus and not in use - I asked why they left it there when they put the new system in and they said they were not allowed to touch another company's equipment, so just left it.  So its now disconnected and on its way to their local store for return, and I'm down to 1 network.

 

Thanks again for your help - I'm back up and running "on all cylinders"

 

Wallis