Weird issue tonight login page was fine once i logged in just had a generic chrome page not available (tried incognito to rule out cookies)

tried restarting/reloading, stopping and starting on nginx no change. connect said my server was offline. found a handy command to stop the array since i new my docker container were still running. this saved me from having to do a parity check on reboot.

 

CSRF=$(cat /var/local/emhttp/var.ini | grep -oP 'csrf_token="\K[^"]+')

curl -k --data "startState=STARTED&file=&csrf_token=${CSRF}&cmdStop=Stop" http://localhost/update.htm

diagnostics attached any insight is greatly appreciated

thor-diagnostics-20240422-2016.zip

just happened again this time however it recovered on its own after about 5 min

 

thor-diagnostics-20240424-1214.zip

are unraid shares still accessible?
ssh still accessible?
website error # ?
500 / 404 ?

 

reviewing current diagnostic.

That's all very odd...i am aware of the Disk 9 Write caching and I am adding and replacing drives very frequently lately

the go file has been like that for years without issues. almost all of it is commented out

the docker-shell is just a small script that lets me via via CLI press a number to access any running docker containers cli it was introduced by spaceInvader1 some years ago.

the log file was set set larger to accommodate some issues i had a long time ago.

I do not have IPv6 enabled on my network or unRAID so that's very odd. I am using IPvlan as MacVLAN had issues a version or two back. eth0 is my 10gbps NIC and eth1 is the on board 1gbps NIC i would think nothing is wrong there since its been working for just over a year in this configuration.

either way its something that recently happening and hasn't since the last recovery....very odd

you may need to ssh / termainl in and kill the nginx service:
 

 

So lets kill it via terminal command:

lsof -i :80
lsof -i :443
 

example of my output of above command.:

root@BMM-Unraid:~# lsof -i :80
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nginx   12275 root    8u  IPv4  14264      0t0  TCP localhost:http (LISTEN)
nginx   12275 root    9u  IPv4  14265      0t0  TCP BMM-Unraid:http (LISTEN)

Then kill all and any apps in the list to do this look at PID #

Command:
I forget the command...
https://docs.oracle.com/cd/E19253-01/817-0403/eoizf/index.html

This should work example:
kill -9 12275

or

kill -SIGKILL 12275

you can also use htop in terminal....

Then try to start nginx:
/etc/rc.d/rc.nginx start
/etc/rc.d/rc.nginx restart

16 hours ago, bmartino1 said:

you may need to ssh / termainl in and kill the nginx service:
 

 

So lets kill it via terminal command:

lsof -i :80
lsof -i :443
 

example of my output of above command.:

root@BMM-Unraid:~# lsof -i :80
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
nginx   12275 root    8u  IPv4  14264      0t0  TCP localhost:http (LISTEN)
nginx   12275 root    9u  IPv4  14265      0t0  TCP BMM-Unraid:http (LISTEN)

Then kill all and any apps in the list to do this look at PID #

Command:
I forget the command...
https://docs.oracle.com/cd/E19253-01/817-0403/eoizf/index.html

This should work example:
kill -9 12275

or

kill -SIGKILL 12275

you can also use htop in terminal....

Then try to start nginx:
/etc/rc.d/rc.nginx start
/etc/rc.d/rc.nginx restart

thank you never thought to kill the process first i did run:

/etc/rc.d/rc.nginx stop
got the successly stopped message

 

then ran:
/etc/rc.d/rc.nginx start

it started fine.

its only happened twice so far so really not sure what caused it and why first time required a full reboot to get it back while second time it self recovered in 5min

I have set port down on the on board ethernet eth1 and that should hopefully prevent those spamming messages.. i do run syslog too so could look at those logs when time permits


thank you for the suggestions i will try and see if they work if i see this happen again