Dpkg-reconfigure openssh-server fails on boot
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
When I boot the linux, dpkg-reconfigure openssh-server fails and the booting gets stopped there. But when i press ctrl+c it resumes the booting with dpkg-reconfigure failed.
ssh boot arm serial-port serial-console
edited Nov 27 at 9:13
telcoM
14.9k12143
asked Nov 26 at 10:09
Rebel
1
add a comment |
up vote
0
down vote
favorite
When I boot the linux, dpkg-reconfigure openssh-server fails and the booting gets stopped there. But when i press ctrl+c it resumes the booting with dpkg-reconfigure failed.
ssh boot arm serial-port serial-console
edited Nov 27 at 9:13
telcoM
14.9k12143
asked Nov 26 at 10:09
Rebel
1
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I boot the linux, dpkg-reconfigure openssh-server fails and the booting gets stopped there. But when i press ctrl+c it resumes the booting with dpkg-reconfigure failed.
ssh boot arm serial-port serial-console
edited Nov 27 at 9:13
telcoM
14.9k12143
asked Nov 26 at 10:09
Rebel
1
When I boot the linux, dpkg-reconfigure openssh-server fails and the booting gets stopped there. But when i press ctrl+c it resumes the booting with dpkg-reconfigure failed.
ssh boot arm serial-port serial-console
ssh boot arm serial-port serial-console
edited Nov 27 at 9:13
telcoM
14.9k12143
asked Nov 26 at 10:09
Rebel
1
edited Nov 27 at 9:13
telcoM
14.9k12143
asked Nov 26 at 10:09
Rebel
1
edited Nov 27 at 9:13
telcoM
14.9k12143
edited Nov 27 at 9:13
telcoM
14.9k12143
edited Nov 27 at 9:13
telcoM
14.9k12143
14.9k12143
asked Nov 26 at 10:09
Rebel
1
asked Nov 26 at 10:09
Rebel
1
asked Nov 26 at 10:09
Rebel
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
dpkg-reconfigure openssh-server should not routinely run at every boot. It probably runs because some update procedure was interrupted. Verify that your system disk is not 100% full.
You should then run sudo dpkg-reconfigure openssh-server or equivalent manually, and allow it to run to completion. If it produces any error messages, troubleshoot those errors.
When the command completes successfully, it should automatically make a record in the package management database that the openssh-server package is now fully configured, and so it should no longer attempt to reconfigure it at every boot.
answered Nov 26 at 10:34
telcoM
14.9k12143
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.servicecould be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?
– telcoM
Nov 27 at 9:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
dpkg-reconfigure openssh-server should not routinely run at every boot. It probably runs because some update procedure was interrupted. Verify that your system disk is not 100% full.
You should then run sudo dpkg-reconfigure openssh-server or equivalent manually, and allow it to run to completion. If it produces any error messages, troubleshoot those errors.
When the command completes successfully, it should automatically make a record in the package management database that the openssh-server package is now fully configured, and so it should no longer attempt to reconfigure it at every boot.
answered Nov 26 at 10:34
telcoM
14.9k12143
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.servicecould be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?
– telcoM
Nov 27 at 9:10
add a comment |
up vote
1
down vote
dpkg-reconfigure openssh-server should not routinely run at every boot. It probably runs because some update procedure was interrupted. Verify that your system disk is not 100% full.
You should then run sudo dpkg-reconfigure openssh-server or equivalent manually, and allow it to run to completion. If it produces any error messages, troubleshoot those errors.
When the command completes successfully, it should automatically make a record in the package management database that the openssh-server package is now fully configured, and so it should no longer attempt to reconfigure it at every boot.
answered Nov 26 at 10:34
telcoM
14.9k12143
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.servicecould be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?
– telcoM
Nov 27 at 9:10
add a comment |
up vote
1
down vote
up vote
1
down vote
dpkg-reconfigure openssh-server should not routinely run at every boot. It probably runs because some update procedure was interrupted. Verify that your system disk is not 100% full.
You should then run sudo dpkg-reconfigure openssh-server or equivalent manually, and allow it to run to completion. If it produces any error messages, troubleshoot those errors.
When the command completes successfully, it should automatically make a record in the package management database that the openssh-server package is now fully configured, and so it should no longer attempt to reconfigure it at every boot.
answered Nov 26 at 10:34
telcoM
14.9k12143
dpkg-reconfigure openssh-server should not routinely run at every boot. It probably runs because some update procedure was interrupted. Verify that your system disk is not 100% full.
You should then run sudo dpkg-reconfigure openssh-server or equivalent manually, and allow it to run to completion. If it produces any error messages, troubleshoot those errors.
When the command completes successfully, it should automatically make a record in the package management database that the openssh-server package is now fully configured, and so it should no longer attempt to reconfigure it at every boot.
answered Nov 26 at 10:34
telcoM
14.9k12143
answered Nov 26 at 10:34
telcoM
14.9k12143
answered Nov 26 at 10:34
telcoM
14.9k12143
answered Nov 26 at 10:34
telcoM
14.9k12143
14.9k12143
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.servicecould be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?
– telcoM
Nov 27 at 9:10
add a comment |
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.servicecould be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?
– telcoM
Nov 27 at 9:10
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
Its showing Creating SSH2 RSA key; this may take some time and after sometime it leaves the error message "Timedout waiting for dev-ttyMSM0 device. Dependency failed for serial getty on ttyMSM0'
– Rebel
Nov 27 at 3:57
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
OK, so the hardware is not a regular PC, but a Dragonboard or something similar - and it's trying (and failing) to do something with the first serial port, that is probably being used as the serial console. Probably attempting to gather some true randomness for key generation, I guess... I'd need to investigate further, but I'll need to do my day job first, so it may take a while.
– telcoM
Nov 27 at 8:32
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
Ok. For more info when i deleted the line "exec start=dpkg-reconfigure openssh-server " from ssh-keys.service , the system booted. But i want the system to be booted with that service.
– Rebel
Nov 27 at 8:53
ssh-keys.service could be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?– telcoM
Nov 27 at 9:10
ssh-keys.service could be something that is supposed to run only once, the first time the system is booted after installation, to initialize the SSH host keys. Or it might be something specific to your Linux distribution: it does not appear in any release of Debian I know of, not even the current unstable. What is the name of the distribution, by the way?– telcoM
Nov 27 at 9:10
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484157%2fdpkg-reconfigure-openssh-server-fails-on-boot%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
