Hi Ulrich,<div id="yMail_cursorElementTracker_1613564532940"><br></div><div id="yMail_cursorElementTracker_1613564533127"><br></div><div id="yMail_cursorElementTracker_1613564533277">actually you can suppress them.</div><div id="yMail_cursorElementTracker_1613564547210"><br></div><div id="yMail_cursorElementTracker_1613564547337">Best Regards,</div><div id="yMail_cursorElementTracker_1613564552019">Strahil Nikolov<br> <br> <blockquote style="margin: 0 0 20px 0;"> <div style="font-family:Roboto, sans-serif; color:#6D00F6;"> <div>On Wed, Feb 17, 2021 at 13:04, Ulrich Windl</div><div><Ulrich.Windl@rz.uni-regensburg.de> wrote:</div> </div> <div style="padding: 10px 0 0 20px; margin: 10px 0 0 0; border-left: 1px solid #6D00F6;"> Hi Ken,<br clear="none"><br clear="none">personally I think systemd is already logging too much, and I don't think that<br clear="none">adding instructions to many log messages is actually helpful (It could be done<br clear="none">as separate log message (maybe at severity info) already).<br clear="none">In Windows I see the problem that it's very hard to find real problems as the<br clear="none">logs are flooded with all kinds of stuff.<br clear="none"><br clear="none">Example (being rather useless):<br clear="none">Feb 17 12:01:01 h03 systemd[1]: Started Session 41667 of user root.<br clear="none">-- Subject: Unit session-41667.scope has finished start-up<br clear="none">-- Defined-By: systemd<br clear="none">-- Support: <a shape="rect" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel " target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel </a><br clear="none">--<br clear="none">-- Unit session-41667.scope has finished starting up.<br clear="none">--<br clear="none">-- The start-up result is done.<br clear="none"><br clear="none">So is there any useful info in those extra lines?<br clear="none"><br clear="none">Regards,<br clear="none">Ulrich<br clear="none"><br clear="none"><br clear="none"><br clear="none">>>> Ken Gaillot <<a shape="rect" ymailto="mailto:kgaillot@redhat.com" href="mailto:kgaillot@redhat.com">kgaillot@redhat.com</a>> schrieb am 16.02.2021 um 20:47 in<br clear="none">Nachricht<br clear="none"><<a shape="rect" ymailto="mailto:8a2c91037be49816055a717583c6c505c996f5e7.camel@redhat.com" href="mailto:8a2c91037be49816055a717583c6c505c996f5e7.camel@redhat.com">8a2c91037be49816055a717583c6c505c996f5e7.camel@redhat.com</a>>:<br clear="none">> Hi all,<br clear="none">> <br clear="none">> The systemd journal has a feature called the message catalog, which<br clear="none">> allows "journalctl ‑x" to show extended troubleshooting hints along<br clear="none">> with log messages. Apparently a similar feature is familiar to many<br clear="none">> Windows administrators.<br clear="none">> <br clear="none">> So far, I've only found systemd itself that uses the feature. As an<br clear="none">> example, if the usual log message is a one‑liner about httpd dumping<br clear="none">> core, with journalctl ‑x it would look like:<br clear="none">> <br clear="none">>  ‑‑ fc2e22bc6ee647b6b90729ab34a250b1<br clear="none">>  Subject: Process 1234 (httpd) dumped core<br clear="none">>  Defined‑By: systemd<br clear="none">>  Support: <a shape="rect" href="http://lists.freedesktop.org/mailman/listinfo/systemd‑devel " target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd‑devel </a><br clear="none">>  Documentation: man:core(5)<br clear="none">>  Documentation: <br clear="none">><br clear="none"><a shape="rect" href="http://www.freedesktop.org/wiki/Software/systemd/catalog/fc2e22bc6ee647b6b907" target="_blank">http://www.freedesktop.org/wiki/Software/systemd/catalog/fc2e22bc6ee647b6b907</a><br clear="none"><br clear="none">> 29ab34a250b1<br clear="none">> <br clear="none">>  Process 1234 (httpd) crashed and dumped core.<br clear="none">> <br clear="none">>  This usually indicates a programming error in the crashing program and<br clear="none">>  should be reported to its vendor as a bug.<br clear="none">> <br clear="none">> There is currently a proposed pull request ( <br clear="none">> <a shape="rect" href="https://github.com/ClusterLabs/libqb/pull/433 " target="_blank">https://github.com/ClusterLabs/libqb/pull/433 </a>) to add support for this<br clear="none">> to libqb's logging API, which the rest of the cluster software could<br clear="none">> use.<br clear="none">> <br clear="none">> As an example, if someone forcibly uploads a CIB with syntax errors,<br clear="none">> Pacemaker will currently log "The cluster is mis‑configured ‑ shutting<br clear="none">> down and staying down" and exit. We could make it so that the<br clear="none">> journalctl ‑x entry tells the user how to use crm_verify to figure out<br clear="none">> what's wrong, how to use cibadmin to correct any errors, and a link to<br clear="none">> Pacemaker Explained as a configuration reference.<br clear="none">> <br clear="none">> This would involve considerable work for developers, so I'm curious how<br clear="none">> many users would find this useful and would use it. Especially if most<br clear="none">> of the time you used journalctl ‑x, there was no extended information,<br clear="none">> but occasionally there was.<br clear="none">> ‑‑ <br clear="none">> Ken Gaillot <<a shape="rect" ymailto="mailto:kgaillot@redhat.com" href="mailto:kgaillot@redhat.com">kgaillot@redhat.com</a>><br clear="none">> <br clear="none">> _______________________________________________<br clear="none">> Manage your subscription:<br clear="none">> <a shape="rect" href="https://lists.clusterlabs.org/mailman/listinfo/users " target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users </a><br clear="none">> <br clear="none">> ClusterLabs home: <a shape="rect" href="https://www.clusterlabs.org/ " target="_blank">https://www.clusterlabs.org/ </a><div class="yqt5338557756" id="yqtfd05698"><br clear="none"><br clear="none"><br clear="none"><br clear="none">_______________________________________________<br clear="none">Manage your subscription:<br clear="none"><a shape="rect" href="https://lists.clusterlabs.org/mailman/listinfo/users" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br clear="none"><br clear="none">ClusterLabs home: <a shape="rect" href="https://www.clusterlabs.org/" target="_blank">https://www.clusterlabs.org/</a><br clear="none"></div> </div> </blockquote></div>