X-Original-To: alpine-user@lists.alpinelinux.org Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) by lists.alpinelinux.org (Postfix) with ESMTP id 2F857F859E4 for ; Thu, 17 Jan 2019 14:01:57 +0000 (UTC) Received: by sdaoden.eu (Postfix, from userid 1000) id EEB711604A; Thu, 17 Jan 2019 15:01:56 +0100 (CET) Date: Thu, 17 Jan 2019 15:02:07 +0100 From: Steffen Nurpmeso To: alpine-user@lists.alpinelinux.org Subject: [alpine-user] Startup hangs (aports: sshd?) Message-ID: <20190117140207.lqzvY%steffen@sdaoden.eu> Mail-Followup-To: alpine-user@lists.alpinelinux.org User-Agent: s-nail v14.9.11-149-g00aa3097 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Hello. After upgrading to [edge] i see a possibly endless hang upon startup, which seems to be caused by PRNG init. I have seen the AlpineLinux bug report from two years ago. I have seen hangs of about one to two minutes on the VM since, hmm, not too long, maybe two or three months?, and on the bare metal we do hang also about a minute. I presumed it was about PRNG seeding, and, whereas i totally dislike that the precious entropy pool i save in between boots does not count at all, geeh, what can i do about that... Anyway. So after upgrading [edge] today i get a possible endless hang, it was about eleven minutes before my "homebrew watchdog" caused starting of other services, which then overcame the seeding: [ 10.386116] random: dnsmasq: uninitialized urandom read (128 bytes read) [ 673.619579] random: crng init done And this: Jan 17 14:04:14 init: starting pid 1997, tty '': '/sbin/openrc default' ... Jan 17 14:15:09 /etc/init.d/lighttpd[2355]: lighttpd: waiting for sshd (50 seconds) Jan 17 14:15:18 /etc/init.d/lighttpd[2355]: lighttpd: waiting for sshd (41 seconds) Jan 17 14:15:20 lighttpd[2406]: (server.c.1457) server started (lighttpd/1.4.52) Eleven minutes! Maybe longer if left alone! So if it is like that, (why does lighttpd wait for sshd via init.d, btw.??), and if people are about to install haveged or whatever, wouldn't it make sense to ensure that jitterentropy_rng is loaded during boot, and rmmoded later on, unless it is also in /etc/modules? --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---