dropbear doesn't start after changing the password

[pyther@…]

After flashing my router with 10.03 RC2 I telnet'd in and issued passwd to change the root password. Then I attempted to login via ssh using the command ssh root@192.168.1.1 without any luck. Restarting the dropbear service via /etc/rc.d/dropbear seemed to resolve the issue.

However, if you do not restart the dropbear service upon reboot ssh is still disabled. This results in not being able to login since telnet is disabled and ssh appears to also be disabled. The web interface crashes whenever I attempt to login (this might be a separate issue).

Router: WZR-HP-G300NH

[Matthew <pyther@…>]

ps aux shows the following process

/bin/sh /etc/rc.common /etc/rc.d/S50dropbear start

It appears that this process is taking a while to exit, at least 30 seconds if not more. I also believe that the command that adds dropbear to the startup also takes a little while.

[nico]

See #7046

[pyther@…]

This issue is still present with 10.03 (final).
Ticket #7046 is different and as noted on that ticket, it does not seem to be a problem anymore.

[nico]

Can you confirm this issue is still present in 10.03.1-rc1 ?

[anonymous]

i'm not sure if this is the same result, but using trunk i installed dropbear via opkg (self-built, no other modification though). i set my root password and "/etc/init.d/dropbear start" to test my ssh setup. i ssh'd in without any issue, so i restarted the router. telnet attempts fail as expected, but ssh connection attempts are refused. i can only assume dropbear isn't running. this is an otherwise virgin/vanilla installation.

[cshore]

You may not have enough flash space left after flashing the image for
jffs2 partition, so you may be running only off ramdisk, and thus have
not permanent settings. do df to see how much space on /overlay.

[nbd]

If you install dropbear into an image that doesn't have it already, you need to run /etc/init.d/dropbear enable