February 2Feb 2 I have an issue that the ssh server crashes every few weeks, it's always this same error, Is there anyway to avoid this? Jan 24 03:10:50 Tower rc.sshd: Updating SSH server daemon... Jan 24 03:10:50 Tower sshd[1688101]: Received signal 15; terminating. Jan 24 03:10:50 Tower sshd[1688958]: error: Bind to port 22 on 169.254.55.139 failed: Cannot assign requested address. Jan 24 03:10:50 Tower sshd[1688958]: fatal: Cannot bind any address.Currently i have out of band management so i can manually restart it an the UI when it crashes, but it's a bit annoying, is there a work around to resolve this so the ssd and nginex doesn't have this issue ?Another small thing is that these logs are under login not error/warning Jan 24 03:10:50 Tower sshd[1688958]: error: Bind to port 22 on 169.254.55.139 failed: Cannot assign requested address. Jan 24 03:10:50 Tower sshd[1688958]: fatal: Cannot bind any address. Feb 2 15:28:55 Tower sshd[2022557]: Server listening on 192.168.1.173 port 22.And logs like this are under errorJan 21 22:24:30 Tower sshd-session[2401656]: Read error from remote host 188.177.1.52 port 54664: Connection reset by peerI might be a nit thing about the log grouping but.. still thought i'd mention it here,
February 3Feb 3 Community Expert The NIC link is going down:Jan 24 03:11:38 Tower kernel: e1000e 0000:00:1f.6 eth0: NIC Link is DownI've seen similar issues before when this happens with DHCP, looks like there's a racing condition starting the services, possibly when the DHCP is not quick enough.My suggestion would be to use a static IP for Unraid, that should resolve the issue.
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.