Bmalone Posted March 23 Share Posted March 23 I had a weird issue today where I suddenly couldn't access my Unraid server from any device. Ended up having to log into IPMI and restart the server manually. So, I decided to configure SSH. However, I can connect fine, but Unraid is disabling my keyboard inputs so I cannot enter a password. Same behavior and syslog entry on both servers. SSH is enabled, but is there something else I have to do in order to enable it? Doesn't work from Putty on Windows or a Mac. Postponed keyboard-interactive for root from 192.168.30.252 port 58839 ssh2 [preauth] Quote Link to comment
Bmalone Posted March 30 Author Share Posted March 30 Doe anyone have anything I can try to unlock the SSH capability? I assume that it is blocked and something needs to be done to unblock it, rather than it being a bug, but I don't know. Seems like a pretty fundamental feature to not work out of the box (albeit disables in the GUI which makes sense). Quote Link to comment
itimpi Posted March 30 Share Posted March 30 Have you tried enabling it under Settings->Management Access. Quote Link to comment
Bmalone Posted March 31 Author Share Posted March 31 51 minutes ago, itimpi said: Have you tried enabling it under Settings->Management Access. Yes of course. Quote Link to comment
Bmalone Posted April 3 Author Share Posted April 3 So I've left SSH off for a few days. Today, I turned it on again to try and test it again. What I noticed is as soon as I turned it on, performance was significantly impacted and the server hung, and the dashboard wouldn't render. When I looked in the syslog I can see that my server was absolutely flooded with Nginx events non-stop right after I turned it on. I tried to include the diagnostics, but there are so many events it won't complete. It won't even retrieve my folder directory in my media folder it's so busy. Does anyone know what might be causing this? Thousands upon thousands of these events... Apr 3 16:30:52 Goathead nginx: 2024/04/03 16:30:52 [alert] 6493#6493: worker process 31293 exited on signal 6 Apr 3 16:30:54 Goathead nginx: 2024/04/03 16:30:54 [alert] 6493#6493: worker process 31462 exited on signal 6 Apr 3 16:30:56 Goathead nginx: 2024/04/03 16:30:56 [alert] 6493#6493: worker process 31563 exited on signal 6 Apr 3 16:30:58 Goathead nginx: 2024/04/03 16:30:58 [alert] 6493#6493: worker process 31757 exited on signal 6 Apr 3 16:31:00 Goathead nginx: 2024/04/03 16:31:00 [alert] 6493#6493: worker process 31852 exited on signal 6 Apr 3 16:31:02 Goathead nginx: 2024/04/03 16:31:02 [alert] 6493#6493: worker process 32112 exited on signal 6 Apr 3 16:31:04 Goathead nginx: 2024/04/03 16:31:04 [alert] 6493#6493: worker process 32252 exited on signal 6 Apr 3 16:31:06 Goathead nginx: 2024/04/03 16:31:06 [alert] 6493#6493: worker process 32353 exited on signal 6 Apr 3 16:31:08 Goathead nginx: 2024/04/03 16:31:08 [alert] 6493#6493: worker process 32694 exited on signal 6 Apr 3 16:31:10 Goathead nginx: 2024/04/03 16:31:10 [alert] 6493#6493: worker process 32777 exited on signal 6 Apr 3 16:31:12 Goathead nginx: 2024/04/03 16:31:12 [alert] 6493#6493: worker process 32906 exited on signal 6 Apr 3 16:31:14 Goathead nginx: 2024/04/03 16:31:14 [alert] 6493#6493: worker process 33093 exited on signal 6 Apr 3 16:31:16 Goathead nginx: 2024/04/03 16:31:16 [alert] 6493#6493: worker process 33204 exited on signal 6 Apr 3 16:31:18 Goathead nginx: 2024/04/03 16:31:18 [alert] 6493#6493: worker process 33300 exited on signal 6 Apr 3 16:31:20 Goathead nginx: 2024/04/03 16:31:20 [alert] 6493#6493: worker process 33403 exited on signal 6 Apr 3 16:31:22 Goathead nginx: 2024/04/03 16:31:22 [alert] 6493#6493: worker process 33521 exited on signal 6 Apr 3 16:31:24 Goathead nginx: 2024/04/03 16:31:24 [alert] 6493#6493: worker process 33712 exited on signal 6 Apr 3 16:31:26 Goathead nginx: 2024/04/03 16:31:26 [alert] 6493#6493: worker process 33773 exited on signal 6 Apr 3 16:31:28 Goathead nginx: 2024/04/03 16:31:28 [alert] 6493#6493: worker process 34002 exited on signal 6 Apr 3 16:31:30 Goathead nginx: 2024/04/03 16:31:30 [alert] 6493#6493: worker process 34150 exited on signal 6 Apr 3 16:31:32 Goathead nginx: 2024/04/03 16:31:32 [alert] 6493#6493: worker process 34307 exited on signal 6 Apr 3 16:31:34 Goathead nginx: 2024/04/03 16:31:34 [alert] 6493#6493: worker process 34464 exited on signal 6 Apr 3 16:31:36 Goathead nginx: 2024/04/03 16:31:36 [alert] 6493#6493: worker process 34516 exited on signal 6 Apr 3 16:31:38 Goathead nginx: 2024/04/03 16:31:38 [alert] 6493#6493: worker process 34647 exited on signal 6 Apr 3 16:31:40 Goathead nginx: 2024/04/03 16:31:40 [alert] 6493#6493: worker process 34835 exited on signal 6 Apr 3 16:31:42 Goathead nginx: 2024/04/03 16:31:42 [alert] 6493#6493: worker process 34947 exited on signal 6 Apr 3 16:31:44 Goathead nginx: 2024/04/03 16:31:44 [alert] 6493#6493: worker process 35210 exited on signal 6 Apr 3 16:31:46 Goathead nginx: 2024/04/03 16:31:46 [alert] 6493#6493: worker process 35349 exited on signal 6 Apr 3 16:31:48 Goathead nginx: 2024/04/03 16:31:48 [alert] 6493#6493: worker process 35492 exited on signal 6 Apr 3 16:31:50 Goathead nginx: 2024/04/03 16:31:50 [alert] 6493#6493: worker process 35676 exited on signal 6 Apr 3 16:31:52 Goathead nginx: 2024/04/03 16:31:52 [alert] 6493#6493: worker process 35776 exited on signal 6 Apr 3 16:31:54 Goathead nginx: 2024/04/03 16:31:54 [alert] 6493#6493: worker process 35853 exited on signal 6 Apr 3 16:31:56 Goathead nginx: 2024/04/03 16:31:56 [alert] 6493#6493: worker process 36259 exited on signal 6 Apr 3 16:31:58 Goathead nginx: 2024/04/03 16:31:58 [alert] 6493#6493: worker process 36347 exited on signal 6 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.