X-Original-To: alpine-user@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 0BCF5F85A1A for ; Sat, 19 Jan 2019 00:47:35 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 68D4D9E23D8; Sat, 19 Jan 2019 00:47:35 +0000 (GMT) Received: from ncopa-macbook.copa.dup.pw (187-40-231-119.user.veloxzone.com.br [187.40.231.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id 85EBE9E0EFC; Sat, 19 Jan 2019 00:47:33 +0000 (GMT) Date: Sat, 19 Jan 2019 00:47:24 +0000 From: Natanael Copa To: Steffen Nurpmeso Cc: alpine-user@lists.alpinelinux.org Subject: Re: [alpine-user] Startup hangs (aports: sshd?) Message-ID: <20190119004724.78b1b0c9@ncopa-macbook.copa.dup.pw> In-Reply-To: <20190117140207.lqzvY%steffen@sdaoden.eu> References: <20190117140207.lqzvY%steffen@sdaoden.eu> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Thu, 17 Jan 2019 15:02:07 +0100 Steffen Nurpmeso wrote: > Hello. > > After upgrading to [edge] i see a possibly endless hang upon > startup, which seems to be caused by PRNG init. Try add random.trust_cpu=1 as boot option. See: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=39a8883a2b989d1d21bd8dd99f5557f0c5e89694 and: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y&id=9b25436662d5fb4c66eb527ead53cab15f596ee0 -nc > 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 > --- > --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---