6.12.4 - Gets unresponsive (Have to Cut power & hard reboot)

Enable the syslog server and post that after a crash.

So I waited and it just happened again total freeze of the Unraid server, not even a SSH connection was possible.

 

Cut the power and retrieved the syslog from the usb boot stick.

(For some reason the setting to save the syslog to the cache drive didn't seem to work?).

 

Please let me know if you need any more information that I can retrieve for you
 

syslog

Edited September 10, 2023 by casperse

Sep 10 10:17:40 PLEXZONE sshd[22102]: Connection closed by authenticating user root 192.168.0.92 port 57804 [preauth]
Sep 10 10:20:17 PLEXZONE kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15

Was the crash at this time?

According to the uptimerobot the alarm I got was received at:
2023-09-10 05:20:06 and 2023-09-10 06:04:02 after that it was unresponsive.

Edited September 10, 2023 by casperse

Could be related to this issue many of us are seeing on 6.12.3:

 

17 hours ago, fateful-inbound8133 said:

Could be related to this issue many of us are seeing on 6.12.3:

 

But I am running 6.12.4 and I think its resolved in this release

I'm not seeing anything relevant logged, one thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

What about this:


I did a:

/etc/rc.d/rc.nginx restart
/etc/rc.d/rc.nginx reload

And my services is still running but my UI is gone! (No way to login)
Any idea on what command to write to get it back?

Edited September 12, 2023 by casperse

Ended up doing a telnet/SSH and a reboot command.

Could this be related to the "connect.myunraid" I have this setup with custom ports and are using it everyday!
Only change I can think of?

Maybe trying to run Unraid without and se if the problems disappear? 

So the long errors above:

"nchan: Out of shared memory while allocating message of size"

 

Crashed again this morning.

So this could be related to a docker? (I have now stopped everything except a few, to see if this makes a difference....

16 minutes ago, casperse said:

So the long errors above:

"nchan: Out of shared memory while allocating message of size"

Difficult to say what's causing those, and possibly there's more than a reason, for some users it's leaving a browser window opened to the GUI, especially if it's going to sleep.

Its happening again? closing Unraid connect window to see if it stops in the log.

Attached diagnostic file.....

 

diagnostics-20230913-1835.zip

I have a VM on the server that have a chrome browser with a open session to the Unraid UI
Closing that stopped the log from giving more errors 🙂

Quite a few of the browsers have introduced the idea of sleeping idle tabs so I think if this option is active it can cause problems if tabs are left open to the Unraid GUI.

Update: Closing all active browsers to Unraid and always closing active windows helped.

Also I did a stop of all dockers and have slowly started them over the last days.

And I think "Nextcloud + DB" dockers might be part of the problem?

 

5x24H days uptime new record!

Changed Status to Closed

I keep searching for answers to the 6.12 issues and this is a new one. I have yet to get 6.12 run longer than a day on any version, including 6.12.4. I do tend to leave a browser open on some device or another conencted to my server. 

 

If leaving a browser open causes a server to lock up, the problem is the OS, not the browser, lol. 

 

I guess I'll stick to 6.11.5 where I don't have to worry about my server crashing if I forget to close a browser tab (which I do all the time).

On 9/27/2023 at 7:17 AM, shaunvis said:

I keep searching for answers to the 6.12 issues and this is a new one. I have yet to get 6.12 run longer than a day on any version, including 6.12.4. I do tend to leave a browser open on some device or another conencted to my server. 

 

If leaving a browser open causes a server to lock up, the problem is the OS, not the browser, lol. 

 

I guess I'll stick to 6.11.5 where I don't have to worry about my server crashing if I forget to close a browser tab (which I do all the time).

I had the same problem. There is something going on with .12 that causes hangs. I reverted back to 11.5 and uptime has been great. You'll notice the same problem said over and over again, but will hold of until something forces me to upgrade.

On 9/13/2023 at 11:38 AM, casperse said:

Its happening again? closing Unraid connect window to see if it stops in the log.

Attached diagnostic file.....

 

diagnostics-20230913-1835.zip

This is the same issue that others and I are having, in this thread:

 

I have been counting the errors with this one-liner:

grep -o 'Increase nchan_max_reserved_memory' /var/log/syslog | wc -l

 

My server will crash if I leave a tab open for 18hrs on accident. 

 

Please reopen this issue. 

Diags upon request, but I will have to recreate as I have been nuking the logs and staying logged out. 

 

The problem is not resolved I am now doing reboots every week - sometimes I am lucky and can do it by a telnet command but mostly the only way is to cut the power. 😞
(Syslog server is now enabled again)

 

Edited October 29, 2023 by casperse

Changed Status to Open

Does an auto logout plugin exist? Not sure if the server will crash with just the login screen though. 

I am having the same issue. Please fix this.

im getting this issue every few days on my AMD EPYC 7401P system and my other half gets theses every so often on her dell server

I am having this issue as well; I am currently monitoring my server. I downgraded it all the way back down to 6.10.3 and will see if the server crashes again.

 

Here's all the troubleshooting that I have done before getting to this ridiculous point!

 

Troubleshooting:

 

• I have replaced SATA cables
• Power Supply
• CMOS
• Ran repair on USB flash
• New Configs applied as well.
• Memory is down clocked
• Replaced Hard drives and Unraid server continues to crash after Parity-Sync

 

Not hopeful at this point at all.