Unknown issue during booting with sshd service

Message

madurani · Post by **madurani** » Fri Oct 04, 2019 11:03 am

Hello Guys,

Could You please advise me about sshd service starting issue? I installed new Gentoo server and I have problem with this mentioned service. When server booting and services start in order, so after a netmount service is start process interrupted and stays wait to infinity. When I press some random keys on keyboard, process begins to continue with sshd service and all finish successfully with a login screen.

When I turn off sshd from openrc, starting finishes successfully without interruption to login screen. That is why I think, that problem is with sshd.

After starting sshd, service works properly. I got no idea why sshd waits for an interaction via keyboards.

Code: Select all

pc-rasto /var/log # tail -10 rc.log
 [ ok ]
 * Mounting network filesystems ...
 [ ok ]

#Starting stops there and after pressing some keys on keyboard, process continues with sshd

 * Starting sshd ...
 [ ok ]
 * Starting local ...
 [ ok ]

bunder · Post by **bunder** » Fri Oct 04, 2019 11:43 am

if you are using systemd, you might be having a lack of entropy on boot. i think the typical fix is to install haveged.

cheers

edit: but that doesn't look like systemd, weird.

madurani · Post by **madurani** » Fri Oct 04, 2019 11:54 am

No I use OpenRC.

bunder · Post by **bunder** » Fri Oct 04, 2019 12:02 pm

yeah, i thought so... i also thought it was a systemd only thing... no worries, i'd still give haveged a try though.

Jaglover · Post by **Jaglover** » Fri Oct 04, 2019 12:08 pm

Interesting, one of my computers does the same thing. It noticed it about a month ago, but since it is always on I forgot about this issue. Are you running ~arch or stable? Mine is ~amd64.

madurani · Post by **madurani** » Fri Oct 04, 2019 12:43 pm

Code: Select all

pc-rasto /var/log # cat /etc/portage/make.conf | grep ACCEPT_KEYWORDS
ACCEPT_KEYWORDS="~amd64"

madurani · Post by **madurani** » Fri Oct 04, 2019 1:25 pm

bunder wrote:if you are using systemd, you might be having a lack of entropy on boot. i think the typical fix is to install haveged.

cheers

edit: but that doesn't look like systemd, weird.

It look, that package "haveged" was good idea, server now start as is expected

...

Thanks

Jaglover · Post by **Jaglover** » Fri Oct 04, 2019 2:07 pm

madurani,

thank you for letting us know, and thanks to bunder for providing solution. :)

DigitalCorpus · Post by **DigitalCorpus** » Thu Nov 07, 2019 5:02 am

I have the same problem. I’ll install that utility when I get home to see if that’s the problem/solution.

Update: Yep, entropy was the problem here too.