Date: Thu, 21 Sep 2023 07:48:42 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273418] [panic] Repeating kernel panic on open(/dev/console) Message-ID: <bug-273418-227-2jbfkLhfrh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273418-227@https.bugs.freebsd.org/bugzilla/> References: <bug-273418-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273418 --- Comment #30 from Eugene Grosbein <eugen@freebsd.org> --- /etc/newsyslog.conf contains a line: /var/log/openvpn.log 640 30 * @T00 J /var/run/openvpn.pid So, newsyslogd sends SIGHUP to the openvpn daemon at midnight. Its logs bef= ore panic are lost, but I have its logs for previous midnight when there was no panic: Sep 20 00:00:02 slh openvpn[2314]: SIGHUP[hard,] received, process restarti= ng Sep 20 00:00:02 slh openvpn[2314]: OpenVPN 2.6.5 amd64-portbld-freebsd13.2 = [SSL (OpenSSL)] [LZO] [LZ4] [MH/RECVDA] [AEAD] Sep 20 00:00:02 slh openvpn[2314]: library versions: OpenSSL 1.1.1u-freebsd= 30 May 2023, LZO 2.10 Sep 20 00:00:02 slh openvpn[2314]: Restart pause, 1 second(s) Sep 20 00:00:03 slh openvpn[2314]: Diffie-Hellman initialized with 2048 bit= key ... Sep 20 00:00:03 slh openvpn[2314]: TUN/TAP device /dev/tun0 opened Crashdump information points to some kind of entanglement between openvpn/t= un0 and syslogd/console but it is beyond my comprehension. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273418-227-2jbfkLhfrh>