I've been battling this issue for the last several weeks and I have been unable to pinpoint what exactly is causing my unraid machine to become totally unresponsive. Here are my symptoms:

- Unresponsive via SSH, putty terminal just sits trying to authenticate forever. It never times out.

- Unresponsive via webgui, same as above. Web browser just sits trying to connect forever, never times out.

- Cannot login using local terminal. See attached screenshot. The box is alive, so I can enter in my username and password, however, after hitting enter the system just hangs forever trying to authenticate (I'm assuming). Even control+c doesn't do anything. At this point I am forced to shutdown uncleanly.

 

Since this behaviour has happened repeatably, I had the fix common problems troubleshooting mode running during the last lock-up. Attached is the most recent diagnostics zip file. I cannot provide a tail file, since there wasn't one captured when I forced the box to shutdown. I am hoping the experts here can glean some meaning from the logs.

 

One of my big concerns here is when the last diagnostics file was captured: 6:50 AM local time here, however, by my judgement the box became unresponsive around 8:30 AM. I am not certain on exactly when, but there definitely should have been more logs file captured after 6:50 and before I shut it down (since prior to 6:50, a zip file was being captured every half hour). Does that mean that whatever caused my system to lock-up also crippled the fix common problems plugin's ability to capture log files?

 

Any and all help is very much appreciated!

 

 

 

 

Edited February 24, 20179 yr by SRB

Does your server really have a public IP? If so, that's probably at least part of the issue.

No, however the server is on quite a large LAN (university network) so I took it out just to be on the safe side.

Did you remove the ifconfig.txt file from your diagnostics deliberately? If you're trying to hide your IP address I should tell you that it's still present in your syslog and it is indeed a public IP address - not a good idea at all. I can tell you that your university is located in Ontario. You ought to put it on its own LAN behind a firewall.

Hmmm thanks for pointing this out, I agree this is not good. I guess never realized because I'm most always on my school network.

I will get my IT department to reassign the box so unraid is not exposed. If this locking up problem persists after I get this resolved I will post back.

Thanks johnathanm and John_M


Sent from my SM-G920W8 using Tapatalk