April 1, 20242 yr Unable to connect to the panel. Connection error. The docker containers and VMs that I have loaded still work and everything. However the panel itself fails to work. Inside of safe mode it still has this issue. Although I notice it seems to be varying exactly how long it takes. When this happens I have tried to simply restart nginx but I am unable to log into the console on the machine itself. I type in root and it doesnt prompt me for the password it just asks for the username again. After a power cycle I'm able to get it back up, only for it to go down again. I had changed a few things regarding this system and then it started occuring. My previous flash drive died so I replaced it, and I thought this issue was due to the RAM so I put in confirmed working memory. I have not tried new ram but I have tried replacing the bzimages as well. Unraid connect shows the server as offline but I can access my jellyfin server just fine, along with a few other containers. Please help. EDIT: I finally noticed crond[1305]: exit status 1 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null I have the same 3 plugins (Community apps, clean up plugin and unraid connect) installed on two other unraid machines at the same latest update so I dont think it's that) bismuth-diagnostics-20240401-0133.zip Edited April 1, 20242 yr by entropyofdesire
April 2, 20242 yr Author According to Uptime Kuma (running on another machine) 2024-04-01 20:48:48 was when it lost connection. I have another one from this morning since I had reset it and it went back down again. 2024-04-02 06:28:22 for this one. I don't see anything for then though. it just goes out. The only thing I haven't tried is not running any of my containers and replacing the USB (since I would have to contact unraid support for that). Or completely resetting the image. syslog-192.168.4.101.log
April 2, 20242 yr Community Expert 55 minutes ago, entropyofdesire said: According to Uptime Kuma (running on another machine) 2024-04-01 20:48:48 The last entry from the 1st syslog is from 16:01, and the new one only shows info after that from 20:27, looks like the server restarted, without anything logged difficult to say what the problem could be, 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.
April 3, 20242 yr Author It appears as though it's 100% one of the docker containers. I have been slowly turning them back on and I've narrowed it down to a few. Would I just have to use a different one for that program or would the logs for that container show errors that could cause this?
April 3, 20242 yr Author 3 minutes ago, entropyofdesire said: It appears as though it's 100% one of the docker containers. I have been slowly turning them back on and I've narrowed it down to a few. Would I just have to use a different one for that program or would the logs for that container show errors that could cause this? Throw that out the window. This could be related. Unable to access syslog. syslog server doesnt show anything in particular for this error. Edited April 3, 20242 yr by entropyofdesire
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.