Hello everyone. New user here, but I have been using Unraid for a little over a year now.

 

I recently was trying to setup a game server, and started noticing some odd behavior from my Unraid setup. I am using a Dell R630 blade server and have 3 drives.

 

When I booted up the game server using Docker, it would boot, download Windows, and allow me about 20-30 minutes to install the server files for the game, however at some point Unraid would just lock/freeze up. I could not get the UI to load if I tried to select VM or dashboard. Trying to close the tab and open a new one going to the IP address would result in a timeout. I would have to do a hard reset on my dell via iDrac.

 

I stopped the Docker container, and tried to load up a VM of Windows. Same issue.

 

I also have openwebUI for ollama AI chat. After these issues, the browser for openwebUI does not see that ollama is there. What is going on with this? Any help would be GREATLY appreciated!

r630-diagnostics-20250508-1725.zip

Run Fix Common Problems scan and post new diagnostics

Thank you for the quick reply!

 

Fix common problems only showed a few docker containers that need updating, but I do not use them right at this moment. Ran it, and attached new diagnostics below.

r630-diagnostics-20250508-1755.zip

Setup syslog server

Just now, trurl said:

Setup syslog server

And post a screenshot of those settings

My server has started crashing as well over the last couple weeks. This is what syslog says before it supposedly becomes unresponsive. There is nothing I can see for days prior to that would indicate a crash.

 

May  8 14:13:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 14:14:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 14:15:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 14:16:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 14:17:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 14:18:01 Server crond[2419]: exit status 255 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
May  8 18:53:55 Server rc.rsyslogd: Syslog server daemon...  Started.
May  8 18:53:55 Server root: Delaying execution of fix common problems scan for 10 minutes
May  8 18:53:55 Server unassigned.devices: Mounting 'Auto Mount' Devices...
May  8 18:53:55 Server emhttpd: /usr/local/emhttp/plugins/user.scripts/backgroundScript.sh "/tmp/user.scripts/tmpScripts/elasticsearch/script" >/dev/null 2>&1
May  8 18:53:55 Server emhttpd: Starting services...
May  8 18:53:55 Server emhttpd: shcmd (87): /etc/rc.d/rc.samba reload

 

2 minutes ago, lJakel said:

My server

Start your own thread with your diagnostics

Syslog Server enabled.

 

Syslog server can receive syslogs from other servers. You have to fill in the Remote syslog server field to tell it which server to receive them from. It can be localhost.

12 minutes ago, trurl said:

Syslog server can receive syslogs from other servers. You have to fill in the Remote syslog server field to tell it which server to receive them from. It can be localhost.

Adjusted to now show localhost as the remote field.

After crash, get it from Downloads, zip it, and post it.

You can check that folder to see that it is writing syslog there now.

Just had a crash when trying to restart OpenwebUI. It was not a hard crash like before.

syslog-127.0.0.1.zip

Edited May 9, 20251 yr by Exikutioner

Nothing useful there. Does it crash if you don't try to run those things?

Ok I had to restart the server again, as the UI was unable to load. Please see the attached log and let me know if there is anything showing up now.

syslog-127.0.0.1 (2).zip

log full of these:

May 25 08:23:11 R630 emhttpd: *** bug: 57 /mnt/user/appdata cache
May 25 08:23:11 R630 emhttpd: *** bug: 57 /mnt/user/system cache

Never seen these before and don't know what they might be about. Did you change anything since your previous posts?

Post new diagnostics.

IRC those happen if the share cannot be allocated, reboot and post new diags after array start.

I have not changed anything.

Restarted the server and attached diag and syslog files below.

r630-diagnostics-20250526-1602.zip syslog-127.0.0.1 (3).zip

Looks OK for now, post new diags if it those errors start again.