Hi everyone

 

I have three unraid server that always got this issue.

I want to know why it happen 

 

thanks

Your diagnostics zip (Tools -> Diagnostics) might give a clue as to why it's happening.

these diagnostics after reboot

 

thanks 

sh-diagnostics-20190614-2238.zip st-diagnostics-20190614-2231.zip no-diagnostics-20190614-2247.zip

sh and no: Diagnostics need to be grabbed when the "fault condition" is present to be of any use. There are no gateway timeouts logged.

 

st: Lots of call traces caused by CPU stalls:

Jun 14 20:30:41 STiLL kernel: rcu: INFO: rcu_sched self-detected stall on CPU
Jun 14 20:30:41 STiLL kernel: rcu: 	4-....: (59999 ticks this GP) idle=8ca/1/0x4000000000000002 softirq=22290380/22290380 fqs=13683 
Jun 14 20:30:41 STiLL kernel: rcu: 	 (t=60001 jiffies g=38409161 q=2336951)
Jun 14 20:30:41 STiLL kernel: NMI backtrace for cpu 4
Jun 14 20:30:41 STiLL kernel: CPU: 4 PID: 6520 Comm: unraidd Tainted: G           O      4.19.41-Unraid #1
Jun 14 20:30:41 STiLL kernel: Hardware name: ZTSYSTEM CONGAREE12      /A9DRPF-10D, BIOS 1.08 07/06/2012
Jun 14 20:30:41 STiLL kernel: Call Trace:
...

 

thanks for help, so you think  cpu is leading for it??

 

the issue that this issue happen regularly in three of them and this happen after I update to 6.7 and move to ssl, may it the cause ?

 

everything is working except GUI

 

thanks 

Edited June 15, 20197 yr by Sherk

I don't think the CPU stalls are related to your original question. I just noticed them when reading your diagnostics. I don't know what is causing them but I would look for a newer BIOS or try a different kernel, which means a different version of Unraid.

Is there a way to restart ngnix service by command? Without rebooting server 

5 hours ago, Sherk said:

Is there a way to restart ngnix service by command? Without rebooting server 

/etc/rc.d/rc.nginx restart

This just happening on my unraid 6.70 a few days ago, before that it was fine. Any fix for this?

On 6/17/2019 at 11:24 PM, Squid said:

/etc/rc.d/rc.nginx restart

thanks for the command, but when I use this command the problem stay showing that "This site can’t be reached"

On 6/27/2019 at 1:57 AM, Sherk said:

thanks for the command, but when I use this command the problem stay showing that "This site can’t be reached"

So for me the issue is only with Organizr docker. If I restart Organzr the issue goes away temporarily. Any idea what the long-term fix might be?

 

The Organizr docker log in unraid UI shows no issues. But the log in the Organizr webUI shows:

"OMBI Connect Function - Error: cURL error 7: Failed to connect to 172.16.1.5 port 3579: Connection refused [Execution Time: 01.30s | 1308ms]"

 

UPDATE: after restarting Organizr docker all seems fine for a few days now.

Edited July 1, 20197 yr by guruleenyc