Unraid UI unaccessible

[Gothan]

Hi there,
 
I have had a problem since this morning with my NAS: no longer possible to access the Unraid web interface.
The NAS is still functional, I still have access to shared folders, Plex and I can also query my NAS in SSH but I can no longer log into the user interface so I can no longer manage Unraid.
If a charitable soul could help me understand the problem and solve it, I'm interested.
 
Thanks in advance for your help.

[JorgeB]

Get the diagnostics over ssh.

[Gothan]

Thanks for your reply.

As I'm a newbie, can you explain me how to do that please ?

[itimpi]

8 minutes ago, Gothan said:

Thanks for your reply.

As I'm a newbie, can you explain me how to do that please ?

The word diagnostics when used in the forum is a link to the instructions

[Gothan]

Hi,

 

I've launched the diagnostic through the SSH client and I was expecting to retrieve a zip file.

Nothing happens, only the message "Starting diagnostic collection..."

If I have a look to the NAS through the SSH client, I can see this (diagnostic launched 3 times) :

 

Is it what you need ?

[JorgeB]

It may take a few minutes, if it doesn't finish after 15 min or so reboot.

[Gothan]

In order to relaunch the diagnostics, I've rebooted once again the NAS... and miracle, everything is back !

The web UI is OK and I'm now able to access to my server.

In order to understand what happened, I joined 2 diagnostics files.

- The file named Tower (the initial name of the server when created some months ago) was generated before the reboot of my NAS (the UI was not yet OK)

- The file named Node (the name of my Unraid server) was generated after the reboot (the UI was back)

Thanks in advance for your feedback.

node-diagnostics-20221118-1124.zip tower-diagnostics-20221118-1019.zip

[JorgeB]

18 minutes ago, Gothan said:

The file named Tower (the initial name of the server when created some months ago) was generated before the reboot of my NAS (the UI was not yet OK)

Those diags are also just after a reboot.

[Gothan]

as mentionned, the last reboot was not the first one (it was the second one). But after the first reboot, nothing changed and the UI was still not available.

Edited November 18, 2022 by Gothan

[JorgeB]

Ahh, sorry, misunderstood, in the first diags the go scrip was not executed, no idea why, if it happens again try booting in safe mode.

 

 

[Gothan]

And regarding the second diags, is there any information that can help me to understand what happened, why the UI was not available before the reboots ?

[JorgeB]

Not really since the log starts over, all looks OK in the second ones, if you continue to have issues enable the syslog server.

[Gothan]

Got it.

Thanks for your time and have a good day.

[Gothan]

Hi,

 

Back to this topic as I have the same issue than previously : once again, no access to the web UI of UNRAID but everything is still working (access to the shared directories, container are running).

I've tried to connect to the NAS via SSH to launch the diagnostics before rebooting in order for you to check the problem but no file generated and the process is still running :

When I have a look in the NAS directory where the previous drags files were stored (/boot/logs), the directory is empty.

I can only see this directory created by the diagnostic process but no zip file.

 

Do you have some recommendations to retrieve the diagnostic files to understand the problem ?

 

[JorgeB]

get at least the syslog:

cp /var/log/syslog /boot/syslog.txt

 

[Gothan]

it seems I don't the right to copy the syslog.txt file to my computer... even if I try to copy the file to one of my shared folder

Edited November 25, 2022 by Gothan

[Gothan]

Hi,

 

Finally I've rebooted the NAS and now I've lost every access : no web UI, no access to shared directory, no container running.... What a nightmare since some days

And after a few minutes and a third reboot, everything is back... but I don't understand what is going on and I'm starting to have doubts about the reliability of Unraid in the long term. 

Edited November 26, 2022 by Gothan

[JorgeB]

Do you have a monitor connected or IPMI? Do you see that Unraid finished booting? If yes grabs diags or the syslog from the console.

[Gothan]

Now that the system is back, I can copy the syslog file generated previously.

Hope it will help you to understand the problem.

syslog.txt

If it can help, before the first instance of the problem (last week), I had an issue message regarding Docker and now, each time a container need to be updated, the access to the Unraid web UI seems to be slow.

Edited November 26, 2022 by Gothan

[JorgeB]

Lots of errors like these:

 

Nov 21 17:47:08 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE has not responded in 180 seconds. Reconnecting...
Nov 21 17:47:25 NODE kernel: CIFS: VFS: \\NZXT\Laurent error -11 on ioctl to get interface list
Nov 21 17:50:06 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE\lecoutre error -11 on ioctl to get interface list
Nov 21 17:57:47 NODE kernel: CIFS: VFS: \\NZXT\Laurent error -11 on ioctl to get interface list
Nov 21 18:00:28 NODE kernel: CIFS: VFS: \\GC02DF65ZMD6TE\lecoutre error -11 on ioctl to get interface list

 

Are these UD mounts?

[Gothan]

Both mentioned computer are mounted but not always powered on.

Do i have to unmount them before they're shut down ?

But it's been working like this for several months and I've only had problems for a few days

Edited November 26, 2022 by Gothan

[JorgeB]

9 minutes ago, Gothan said:

Do i have to unmount them before they're shut down ?

You should, if nothing else to avoid spamming the log.