noonamer Posted March 23 Share Posted March 23 (edited) Hey guys, I recently started to notice that I can't access my Unraid. Basically I can't neither ssh nor access WebUI. Maybe someone can suggest something, attaching diagnostics Usually, it becomes accessible within 15mins or so. I also can access containers UI and it is responsive. tnas-diagnostics-20240323-2011.zip tnas-diagnostics-20240322-1714.zip Edited March 23 by noonamer Added more info Quote Link to comment
JorgeB Posted March 23 Share Posted March 23 Out of memory: Killed process 3151 (qbittorrent-nox) This was using a lot of RAM, try limiting it or leaving that container off and retest. Quote Link to comment
noonamer Posted March 23 Author Share Posted March 23 25 minutes ago, JorgeB said: Out of memory: Killed process 3151 (qbittorrent-nox) This was using a lot of RAM, try limiting it or leaving that container off and retest. is it from 1714 log? I limited these to 4GB after reading it. So in 2011 log should be already limited Quote Link to comment
noonamer Posted March 23 Author Share Posted March 23 adding another one, started around ~23:15 tnas-diagnostics-20240323-2322.zip Quote Link to comment
JorgeB Posted March 24 Share Posted March 24 10 hours ago, noonamer said: is it from 1714 log? Nope, the other one, and is still happening in the latest diags: Mar 22 18:10:13 tnas kernel: Memory cgroup out of memory: Killed process 21150 (qbittorrent-nox) Quote Link to comment
noonamer Posted March 24 Author Share Posted March 24 39 minutes ago, JorgeB said: Nope, the other one, and is still happening in the latest diags: Mar 22 18:10:13 tnas kernel: Memory cgroup out of memory: Killed process 21150 (qbittorrent-nox) I haven't rebooted server after freezes, so 22 MAR can be in all 3 logs, but more freezes were happening on 23 MAR (around/close to ~20:00, and ~23:15) as 22 MAR I added `--memory=4G` to these containers Quote Link to comment
JorgeB Posted March 24 Share Posted March 24 Then suggest rebooting to clear the logs and post new diags if it still happens. Quote Link to comment
noonamer Posted March 24 Author Share Posted March 24 2 hours ago, JorgeB said: Then suggest rebooting to clear the logs and post new diags if it still happens. thanks for suggesting, will do Quote Link to comment
noonamer Posted March 24 Author Share Posted March 24 7 hours ago, JorgeB said: Then suggest rebooting to clear the logs and post new diags if it still happens. okay new diagnostics after reboot with freeze tnas-diagnostics-20240324-1859.zip Quote Link to comment
JorgeB Posted March 24 Share Posted March 24 Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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. Quote Link to comment
noonamer Posted March 24 Author Share Posted March 24 19 minutes ago, JorgeB said: Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/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 I noticed, that last time it happened CPU was under pretty heavy load, like close to 100% for some time Quote Link to comment
noonamer Posted March 25 Author Share Posted March 25 I can see a lot of messages like: Mar 25 17:31:12 tnas rpc.mountd[11258]: v4.2 client detached: 0x953c6d1666017fcb from "10.10.179.111:810" Mar 25 17:31:37 tnas rpc.mountd[11258]: v4.2 client attached: 0x953c6d1866017fcb from "10.10.179.111:810" Mar 25 17:31:37 tnas rpc.mountd[11258]: v4.2 client detached: 0x953c6d1766017fcb from "10.10.179.101:972" Mar 25 17:32:13 tnas rpc.mountd[11258]: v4.2 client attached: 0x953c6d1966017fcb from "10.10.179.101:972" Mar 25 17:32:13 tnas rpc.mountd[11258]: v4.2 client detached: 0x953c6d1866017fcb from "10.10.179.111:810" Mar 25 17:32:23 tnas nginx: 2024/03/25 17:32:23 [error] 21340#21340: *66812 open() "/usr/local/emhttp/sm/67dbe90480f98dbadab5f76f93197118b03ce65a6932fed6c64b024935f736b4.map" failed (2: No such file or directory) while sending to client, client: 10.10.179.173, server: , request: "GET /sm/67dbe90480f98dbadab5f76f93197118b03ce65a6932fed6c64b024935f736b4.map HTTP/1.1", host: "tnas.local:81" tnas-diagnostics-20240325-1732.zip Quote Link to comment
JorgeB Posted March 25 Share Posted March 25 25 minutes ago, noonamer said: Mar 25 17:31:12 tnas rpc.mountd[11258]: v4.2 client detached: 0x953c6d1666017fcb from "10.10.179.111:810" Mar 25 17:31:37 tnas rpc.mountd[11258]: v4.2 client attached: 0x953c6d1866017fcb from "10.10.179.111:810" These are NFS related, if you're not using it disable NFS, but probably normal messages. Quote Link to comment
noonamer Posted March 25 Author Share Posted March 25 I use NFS to backup my RPI, so probably that is fine. Oh, another thing I noticed from time to time WebUI graphs are just dead (basically non-responsive, nothing is updating, I can’t see stats or drives). Can it be just lag with Unraid UI/API. as while I can’t access UI or SSH I can access all running containers UIs easily. This makes me thing that something else is going on… Quote Link to comment
noonamer Posted March 26 Author Share Posted March 26 even more interesting observation. while it is inaccessible from my laptop I can access from my mobile phone through the same lan network. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.