Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

SSH fails to start on boot after update to 6.12

Featured Replies

After updating to Unraid 6.12 sshd fails to come up on boot. From the syslog I can see it's started and killed a few times during boot:

 

cat syslog | grep sshd
Jun 25 17:36:03 narvi sshd[1468]: Server listening on 192.168.1.10 port 22.
Jun 25 17:36:13 narvi sshd[1468]: Received signal 15; terminating.
Jun 25 17:36:14 narvi sshd[4203]: Server listening on 192.168.1.10 port 22.
Jun 25 17:36:38 narvi sshd[4203]: Received signal 15; terminating.
Jun 25 17:36:38 narvi sshd[8148]: error: Bind to port 22 on 192.168.1.10 failed: Cannot assign requested address.
Jun 25 17:36:38 narvi sshd[8148]: fatal: Cannot bind any address.

 

Things I've checked: 

 

  • SSH is enabled in Settings -> Management Access
  • Changing the SSH port number does not fix the issue
  • Blowing away /boot/config/ssh and /boot/config/ssl does not fix the issue
  • Starting SSH manually with either "/etc/rc.d/rc.sshd start" or toggling SSH in the interface starts SSH just fine
  • I have no SSH related plugins installed, nor have I ever had any

 

I'm running out of ideas as to how I might fix this. I suspect that sshd stopping and starting in quick succession may cause the port to be temporarily unavailable on the third start of the service during boot up. I'm not familiar enough with Unraid to know why the service is started multiple times during boot though.

syslog.log

Solved by bonienl

  • Solution

ssh is restarted because your system looses network connection halfway.

 

Jun 25 17:36:33 narvi kernel: bond0: (slave eth0): link status definitely down, disabling slave
Jun 25 17:36:33 narvi kernel: device eth0 left promiscuous mode
Jun 25 17:36:33 narvi kernel: bond0: now running without any active interface!
Jun 25 17:36:33 narvi kernel: br0: port 1(bond0) entered disabled state
Jun 25 17:36:33 narvi dhcpcd[1345]: br0: carrier lost
Jun 25 17:36:33 narvi dhcpcd[1345]: br0: deleting route to 192.168.1.0/24
Jun 25 17:36:33 narvi dhcpcd[1345]: br0: deleting default route via 192.168.1.1

 

Disable bonding in the network configuration and see if that solves the issue.

It might also be that the plugin "tips and tweaks" interferes. Uninstall this plugin and retest.

 

  • Author

Thanks a lot @bonienl, uninstalling tips and tweaks solved it!

  • 1 year later...

Same here in 2024 on 6.12.14 - uninstalling Tips and Tweaks is the solution

Edited by kek_tigra
added version

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.