From nobody Wed Sep 20 19:59:08 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RrTrN3C91z4v5vK for ; Wed, 20 Sep 2023 19:59:16 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Received: from mail.worldserver.net (mail.worldserver.net [217.13.200.36]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits)) (Client CN "*.worldserver.net", Issuer "EuropeanSSL Server CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RrTrM1b6qz3gYv for ; Wed, 20 Sep 2023 19:59:15 +0000 (UTC) (envelope-from listac@nebelschwaden.de) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nebelschwaden.de header.s=1687803001 header.b=LAeIZP03; spf=pass (mx1.freebsd.org: domain of listac@nebelschwaden.de designates 217.13.200.36 as permitted sender) smtp.mailfrom=listac@nebelschwaden.de; dmarc=none Received: from postpony.nebelschwaden.de (v22018114346177759.hotsrv.de [194.55.14.20]) (Authenticated sender: sendmail@nebelschwaden.de) by mail.worldserver.net (Postfix) with ESMTPSA id B83271E0B38 for ; Wed, 20 Sep 2023 21:59:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nebelschwaden.de; s=1687803001; t=1695239949; bh=F8UMpf0QbQJPOUIImwkBRTEU50eor/t6Eo3R3mn4/Lw=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To:From; b=LAeIZP030GzJJH1xKsNFmFQ+VdW4fMq/FngIaywXKyrnwr/+qTjw/W2WtrPYjgbUb vUarECBr2lZOLnp7E4oKYTiTMb8gBP8qXpTQ+EeID2P8zVL+HVApu5e167l7jpcoMl 6ZBWanALOPmRFkTShMJahoA3OC252icohwF+XFxBMjg7bV9MtB7GQrTWWm0+pGa6k4 HfCpfj1XZR10Imxe5HxJHFepjgF9A4fKark/pATM04F7es/0jhOKbLongsKX1GsU3S aydznykhY2AN9teB0zhaAN3zZAYh2Q6fulC2dzkMXaFHlylXkJqId8ce0EJ9Y70DIh PB/+m/zrklxIw== Received: from [172.16.37.5] (kaperfahrt.nebelschwaden.de [172.16.37.5]) by postpony.nebelschwaden.de (Postfix) with ESMTP id E4EC7113386 for ; Wed, 20 Sep 2023 21:59:08 +0200 (CEST) Message-ID: <24e16c1d-520d-47eb-912c-923514d8a4ed@nebelschwaden.de> Date: Wed, 20 Sep 2023 21:59:08 +0200 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: listac@nebelschwaden.de Subject: Re: Capturing Boot Messages? Content-Language: en-US To: Freebsd-questions@freebsd.org References: <26de1d95-abff-465d-b25c-1b2465e80342@nebelschwaden.de> <48DF5481-1F7C-4BF6-89D8-F19388449423@prime.gushi.org> From: Ede Wolf In-Reply-To: <48DF5481-1F7C-4BF6-89D8-F19388449423@prime.gushi.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.58 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.99)[-0.991]; R_DKIM_ALLOW(-0.20)[nebelschwaden.de:s=1687803001]; R_SPF_ALLOW(-0.20)[+ip4:217.13.200.0/24]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[217.13.200.36:from]; XM_UA_NO_VERSION(0.01)[]; DMARC_NA(0.00)[nebelschwaden.de]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; BLOCKLISTDE_FAIL(0.00)[217.13.200.36:server fail,194.55.14.20:server fail]; RCVD_TLS_LAST(0.00)[]; HAS_REPLYTO(0.00)[listac@nebelschwaden.de]; MLMMJ_DEST(0.00)[Freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[nebelschwaden.de:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:15657, ipnet:217.13.192.0/20, country:DE]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4RrTrM1b6qz3gYv Am 20.09.23 um 20:40 schrieb Dan Mahoney: > > >> On Sep 20, 2023, at 10:53 AM, Ede Wolf wrote: >> >> Hello, >> >> I am seeing boot messages on screen, errors from rc.conf, that I have yet to find in any log. Neither dmesg, nor /var/run/dmesg.boot nor in /var/log/messages. >> >> Any chance to reread the full boot process somewhere or to set up full boot logging? > > So anything that came from the kernel before init started would get stuck into /var/run/dmesg.boot… > > Anything that came from init, and the rc subsystem, you could enable using the hints in /etc/syslog.conf > > # uncomment this to log all writes to /dev/console to /var/log/console.log > # touch /var/log/console.log and chmod it to mode 600 before it will work > #console.info /var/log/console.log > > Noting from a run of rcorder /etc/rc.d/* that there are some things that start before syslogd, so it might not catch those. > > -Dan Thanks, that is another good way, in addition to dmesg -a, that also solved my issue. As this is generally a very useful thing to do, I've enabled it. It does shows the error messages I have been looking for, as they came up quite late in the boot process.