Bug 2361203 - rkhunter reports Warning: The 'systemd-journald' daemon is running, but no configuration file can be found.
Summary: rkhunter reports Warning: The 'systemd-journald' daemon is running, but no co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rkhunter
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2386541 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-20 04:19 UTC by Frank Crawford
Modified: 2026-01-12 01:08 UTC (History)
5 users (show)

Fixed In Version: rkhunter-1.4.6-31.fc44 rkhunter-1.4.6-31.fc43 rkhunter-1.4.6-31.fc42
Clone Of:
Environment:
Last Closed: 2026-01-03 18:53:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Quick patch to change status from WARNING to INFO (1013 bytes, patch)
2025-04-20 05:03 UTC, Frank Crawford
no flags Details | Diff

Description Frank Crawford 2025-04-20 04:19:39 UTC
During scanning rkhunter generates an email, with the following warning in the report

Warning: The 'systemd-journald' daemon is running, but no configuration file can be found.

However, in a standard setup there is no requirement for systemd-journald to have a configuration file.

Reproducible: Always

Steps to Reproduce:
1.Install rkhunter and run sudo rkhunter --propupd to set up.
2.Run sudo rkhunter --cronjob --nocolors --report-warnings-only (as per cronjob)
3.Note warning output message, and exit status is set to error.
Actual Results:
The warning message of:
Warning: The 'systemd-journald' daemon is running, but no configuration file can be found.
is generated and exit status is set to 1.

Expected Results:
No warning is generated and exit status should be 0.

Additional Information:
I suspect this should now just be an informational message rather than a warning.

Comment 1 Frank Crawford 2025-04-20 05:03:44 UTC
Created attachment 2085959 [details]
Quick patch to change status from WARNING to INFO

Comment 2 Frank Crawford 2025-04-21 05:02:24 UTC
Of course, simpler still is just to add /usr/lib/systemd/journald.conf to the list of files to search!

Comment 3 Kevin Fenzi 2026-01-03 18:25:59 UTC
*** Bug 2386541 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2026-01-03 18:49:05 UTC
FEDORA-2026-c04329af9d (rkhunter-1.4.6-31.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-c04329af9d

Comment 5 Fedora Update System 2026-01-03 18:51:49 UTC
FEDORA-2026-be612e6586 (rkhunter-1.4.6-31.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-be612e6586

Comment 6 Fedora Update System 2026-01-03 18:51:50 UTC
FEDORA-2026-db3bff8bbe (rkhunter-1.4.6-31.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-db3bff8bbe

Comment 7 Fedora Update System 2026-01-03 18:53:24 UTC
FEDORA-2026-c04329af9d (rkhunter-1.4.6-31.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-01-04 01:19:52 UTC
FEDORA-2026-db3bff8bbe has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-db3bff8bbe`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-db3bff8bbe

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2026-01-04 01:54:58 UTC
FEDORA-2026-be612e6586 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-be612e6586`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-be612e6586

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2026-01-12 00:56:05 UTC
FEDORA-2026-db3bff8bbe (rkhunter-1.4.6-31.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2026-01-12 01:08:46 UTC
FEDORA-2026-be612e6586 (rkhunter-1.4.6-31.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.