Bug #15411
openHostname missing from logs in certain cases can cause the system log to display in an unexpected manner
0%
Description
With the system log set to show ~500 lines the system log tab will also show most if not all of the kernel boot messages (dmesg
output).
Some lines in this output are not parsed as expected, making the log output table extremely wide and with unexpected wrapping/lack of wrapping.
See the attached images which are how parts of the following text log are being displayed by the System / General tab:
Apr 16 08:52:23 kernel: ---<<BOOT>>--- Apr 16 08:52:23 kernel: Copyright (c) 1992-2024 The FreeBSD Project. Apr 16 08:52:23 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Apr 16 08:52:23 kernel: The Regents of the University of California. All rights reserved. Apr 16 08:52:23 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Apr 16 08:52:23 kernel: FreeBSD 15.0-CURRENT #0 plus-RELENG_24_03-n256311-e71f834dd81: Tue Apr 16 00:38:18 UTC 2024 Apr 16 08:52:23 kernel: root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/obj/amd64/dyNDzqbt/var/jenkins/workspace/pfSense-Plus-snapshots-24_03-main/sources/FreeBSD-src-plus-RELENG_24_03/amd64.amd64/sys/pfSense amd64 Apr 16 08:52:23 kernel: FreeBSD clang version 17.0.6 (https://github.com/llvm/llvm-project.git llvmorg-17.0.6-0-g6009708b4367) Apr 16 08:52:23 kernel: VT(vga): resolution 640x480
Once that line scrolls off the visible portion of the log it returns to normal.
Files
Updated by Jim Pingle 8 months ago
- File log-wrap-odd-1.png log-wrap-odd-1.png added
- File log-wrap-odd-2.png log-wrap-odd-2.png added
Updated by Jim Pingle 8 months ago
- Subject changed from Certain lines in kernel boot output can cause the default system log table to display in an unexpected manner to Hostname missing from logs in certain cases can cause the system log to display in an unexpected manner
Dug more into this and the problem is that somehow at boot the hostname was not being printed in the system logs on just that one installation during the early part of the boot sequence. Later in the boot sequence syslogd
was restarted and after that point the logs contained the hostname.
I can't reproduce it on any other system in my lab nor can I replicate it on the same system when rebooting now that it's on the latest snapshot. It's possible it's something we already fixed but worth keeping an eye on for the next release just in case there is still a (rare) problem.
Updated by dylan mendez 7 months ago
Had a customer encounter this, restarting firewall and syslogd didn't do it. Changing the lines from 2000 to 500 seems to have fixed it.
Updated by Jim Pingle 7 months ago
- Plus Target Version changed from 24.07 to 24.08
Updated by Jim Pingle 2 months ago
- Plus Target Version changed from 24.08 to 24.11
Updated by Jim Pingle 2 months ago
- Plus Target Version changed from 24.11 to 25.01
Updated by Jim Pingle 13 days ago
- Plus Target Version changed from 25.01 to 25.03