Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
## Description of problem:
- Setting LogLevelMax as either the name or the number does not appear to influence what is logged.
## Version-Release number of selected component (if applicable):
- Name : systems
- Version : 239
- Release : 51.el8_5.3
- Architecture : i686
## How reproducible:
- Always
## Steps to Reproduce:
1. Configure a test harness to generate logs by both logger and systemd-cat at various levels, with messages that reflect the levels.
2. Create a systemd oneshot that has LogLevelMax set, and run the test harness
3. Review the logs. Note how changing the value for LogLevelMax makes no difference to what is logged.
## Actual results:
- LogLevelMax value has zero impact on what is logged to messages.
## Expected results:
- LogLevelMax value to have an impact on what is logged to messages.
Using the test service from the case we can see that none of the messages have been attributed to the service:
# systemctl start testing.service
# journalctl -u testing.service
-- Logs begin at Thu 2022-03-10 15:13:55 CET, end at Thu 2022-03-10 15:18:08 CET. --
Mar 10 15:18:08 localhost.localdomain systemd[1]: Starting I am an example...
Mar 10 15:18:08 localhost.localdomain systemd[1]: testing.service: Succeeded.
Mar 10 15:18:08 localhost.localdomain systemd[1]: Started I am an example.
IOW, this is bug 1677370 again. If, at the time journald is processing a message, the logger process has already terminated, it is not possible to determine the service the process belonged to. Thus, if journald doesn't know the service, it cannot apply service-specific overrides for the message either.
*** This bug has been marked as a duplicate of bug 1677370 ***