CSS style problem with Status->System Logs->System->General
-
After update to 24.11, there's some problem here making the log text not show up. The timestamp and process name are showing up fine. This is reproducible in both Safari and Chrome. Chrome has no extensions installed. Logs of other styles (Firewall, DHCP) render correctly.
The log text is showing up in the relevant HTML <td> tags, so this seems like a CSS issue of some kind.
-
@ohmantics I am not seeing that here using Brave (chrome based) browser.
-
@WN1X I assume it's not 100% reproducible or they wouldn't have shipped the release.
-
It also reproduces in Brave and Firefox.
If it's not CSS, then perhaps it's something in the log text that is throwing off the HTML parsing?
-
@ohmantics You should ssh into your firewall and check the logs directly to see if anything "funny" is present that breaks displaying the entries correctly.
-
Found it. From early boot, that "root@freebsd:/var/jenkins..." line is what's breaking rendering. It needs at least the "white-space: normal" style attribute added to render properly, but it looks like it's trying to put that text in the Process column.
<tr class="text-nowrap"> <td> Dec 14 13:45:04 </td> <td> FreeBSD </td> <td> </td> <td style="word-wrap:break-word; word-break:break-all; white-space:normal"> clang version 18.1.6 (https://github.com/llvm/llvm-project.git llvmorg-18.1.6-0-g1118c2e05e67) </td> </tr> <tr class="text-nowrap"> <td> Dec 14 13:45:04 </td> <td> root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_11-main/obj/amd64/AKWlAIiM/var/jenkins/workspace/pfSense-Plus-snapshots-24_11-main/sources/FreeBSD-src-plus-RELENG_24_11/amd64.amd64/sys/pfSense </td> <td> </td> <td style="word-wrap:break-word; word-break:break-all; white-space:normal"> amd64 </td> </tr> <tr class="text-nowrap"> <td> Dec 14 13:45:04 </td> <td> FreeBSD </td> <td> </td> <td style="word-wrap:break-word; word-break:break-all; white-space:normal"> 15.0-CURRENT #0 plus-RELENG_24_11-n256407-1bbb3194162: Fri Nov 22 05:08:46 UTC 2024 </td> </tr>
-
Now that I look closer, the first several lines of the boot are parsed into columns incorrectly.
-
And the reason it's not reproducing for others is likely that they booted more than 500 entries ago. I've just updated from 24.03 to 24.11.
-
It's this: https://redmine.pfsense.org/issues/15411