My shares were still up and running fine. I could not access the GUI. I am on 6.10. I tried restarting NGIX but it wouldn't come back. So I just issued the reboot command via command line. Here are the last entries in my log. Could that SDH error have taken down the GUI? You also can see where I tried to restart the GUI on the last two lines with no sucess.

 

May 19 06:00:09 SUN kernel: sd 8:0:1:0: [sdh] tag#429 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
May 19 06:00:09 SUN kernel: sd 8:0:1:0: [sdh] tag#429 Sense Key : 0x5 [current] 
May 19 06:00:09 SUN kernel: sd 8:0:1:0: [sdh] tag#429 ASC=0x21 ASCQ=0x0 
May 19 06:00:09 SUN kernel: sd 8:0:1:0: [sdh] tag#429 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00
May 19 06:00:09 SUN kernel: blk_update_request: critical target error, dev sdh, sector 975952682 op 0x3:(DISCARD) flags 0x0 phys_seg 1 prio class 0
May 19 06:00:09 SUN root: /var/lib/docker: 35.9 GiB (38518304768 bytes) trimmed on /dev/loop2
May 19 06:00:14 SUN sSMTP[21555]: Creating SSL connection to host
May 19 06:00:14 SUN sSMTP[21555]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384
May 19 06:00:16 SUN sSMTP[21555]: Sent mail for [email protected] (221 host.diggsnet.com closing connection) uid=0 username=root outbytes=478
May 19 21:12:58 SUN nginx: 2022/05/19 21:12:58 [error] 7633#7633: *829549 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"
May 19 21:13:02 SUN nginx: 2022/05/19 21:13:02 [error] 7633#7633: *829549 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"
May 19 21:30:06 SUN nginx: 2022/05/19 21:30:06 [error] 20873#20873: *839083 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"
May 19 21:30:43 SUN nginx: 2022/05/19 21:30:43 [error] 20873#20873: *839434 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"
May 19 21:31:55 SUN unraid-api[7899]: 👋 Farewell. UNRAID API shutting down!
May 19 21:31:56 SUN root: Starting [email protected]
May 19 21:31:58 SUN unraid-api[27401]: ✔️ UNRAID API started successfully!
May 19 21:32:18 SUN nginx: 2022/05/19 21:32:18 [error] 28330#28330: *223 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"
May 19 21:33:41 SUN nginx: 2022/05/19 21:33:41 [error] 28330#28330: *992 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"

 

Diagnostics?

10 hours ago, trurl said:

Diagnostics?

Here ya go. I hope you see something.  I browsed it over, but didn't see anything except the info in my original post. I also cannot access the webgui more than one instance. That may have been a security update on the 6.10. This is the first time my array's GUI never stopped operating.

sun-diagnostics-20220520-0820.zip

Edited May 20, 20224 yr by opentoe

Well,  here is another webgui. Seems this new version is taking down the webgui from reading the threads all around here. These are my diags BEFORE I restarted. Trying to restart the WEBGUI by the command line does not work. Could this be considered a bug or put on the punchlist?

 

sun-diagnostics-20220520-2100.zip

 

Definately going to need help on this one and what is taking down the GUI everyday. Still accessible via shares, still accessible SSH. What is killing 

"404 Not Found"

nginx

 

Now, what is the proper procedure to kill nginx, then another line to start her all back up again.

sun-diagnostics-20220520-2100.zip

Edited May 21, 20224 yr by opentoe

This is the output when I try to restart nginx from the command line. The WEBGUI never came back up.

 

 

root@SUN:/mnt# cd  ..
root@SUN:/# /etc/rc.d/rc.nginx restart
Checking configuration for correct syntax and
then trying to open files referenced in configuration...
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Shutdown Nginx gracefully...
Stopping unraid-api process...
Process stopped!
Starting Nginx server daemon...
root@SUN:/# /etc/rc.d/rc.nginx reload
Checking configuration for correct syntax and
then trying to open files referenced in configuration...
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Reloading Nginx configuration...
root@SUN:/#
 

It is acting like the webserver files have disappeared?

May 20 08:15:14 SUN nginx: 2022/05/20 08:15:14 [error] 7603#7603: *458574 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: , request: "GET /main HTTP/1.1", host: "192.168.1.200"

While the problem is happening, SSH in and run these commands to see if the files still exist:

ls -al /usr/local/emhttp/webGui
ls -al /usr/local/emhttp/webGui/Main.page 

 

Here is the output for my system:

root@Tower:~# ls -al /usr/local/emhttp/webGui
lrwxrwxrwx 1 root root 15 Jun 18  2016 /usr/local/emhttp/webGui -> plugins/dynamix/
root@Tower:~# ls -al /usr/local/emhttp/webGui/Main.page 
-rw-r--r-- 1 root root 49 Aug  4  2021 /usr/local/emhttp/webGui/Main.page

 

I tried listing both folder you asked and both came back ok.

root@SUN:/# ls -al /usr/local/emhttp/webGui
lrwxrwxrwx 1 root root 15 Jun 19  2016 /usr/local/emhttp/webGui -> plugins/dynamix/

 

ls -al /usr/local/emhttp/webGui/Main.page

-rw-r--r-- 1 root root 49 Aug  4  2021 /usr/local/emhttp/webGui/Main.page
 

 

OK the files exist. I could be completely off base, but I'm wondering if permissions to get to them got borked somehow.

 

While the problem is happening, please run these commands:

ls -al / | grep "usr"
ls -al /usr/ | grep "local"
ls -al /usr/local/ | grep "emhttp"

 

On my system the result look like this:

root@Tower:~# ls -al / | grep "usr"
drwxr-xr-x  12 root root    300 Nov 28 10:03 usr/
root@Tower:~# ls -al /usr/ | grep "local"
drwxr-xr-x  9 root root   180 Nov 28 10:03 local/
root@Tower:~# ls -al /usr/local/ | grep "emhttp"
drwxr-xr-x  4 root root 340 May 21 15:28 emhttp/

 

What I'm trying to do is confirm that each level of the directory hierarchy is owned by root and is executable.

 

root@SUN:/var/log# ls -al / | grep "usr"
drwxr-xr-x  14 root root   340 Apr 21  2021 usr/
root@SUN:/var/log# ls -al /usr/ | grep "local"
drwxr-xr-x  9 root root   180 Apr 21  2021 local/
root@SUN:/var/log# ls -al /usr/local/ | grep "emhttp"
drwxr-xr-x  4 root root 320 Apr 21  2021 emhttp/
root@SUN:/var/log#

 

I'm afraid I am out of ideas. I do not know why nginx is refusing to serve the files.

 

Anyone else have any ideas?

First thing you'd want to do is try this in safe mode.  Assuming that works, delete NerdPack.plg from /config/plugins on the flash drive and then see what happens.

3 hours ago, Squid said:

First thing you'd want to do is try this in safe mode.  Assuming that works, delete NerdPack.plg from /config/plugins on the flash drive and then see what happens.

 

Agreed, this is almost certainly a plugin issue.  Are they all up-to-date?  For example:

 

May 20 08:15:14 SUN nginx: 2022/05/20 08:15:14 [error] 7603#7603: *458574 open() "/usr/local/emhttp/main" failed (2: No such file or directory) while sending to client, client: 192.168.1.122, server: ,

request: "GET /main HTTP/1.1", host: "192.168.1.200"

 

 

The file "/usr/local/emhttp/main" correctly does not exist.  The endpoint "/usr/local/emhttp/Main" does exist.