This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2193337 - should have relative paths in default config and should make sensible use of absolute paths
Summary: should have relative paths in default config and should make sensible use of ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: logwatch
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-05 09:40 UTC by Karel Volný
Modified: 2023-09-20 23:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 23:35:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5725 0 None Migrated None 2023-09-20 23:35:43 UTC
Red Hat Issue Tracker RHELPLAN-156494 0 None None None 2023-05-05 09:41:27 UTC

Description Karel Volný 2023-05-05 09:40:15 UTC
This bug was initially created as a copy of Bug #205096

I am copying this bug because: 
The testcase /CoreOS/logwatch/bz_tests fails for this part.
Looks like this is a regression from the previous release (it doesn't fail in RHEL8).
The current behaviour corresponds to what is described in man

--logdir directory
              Look in directory for log subdirectories or log files first before looking in the default directories.

however, in RHEL8 and older, the real behaviour was _not_ to search "default" directories if logdir was specified.
As this was the point of the previous fix, I believe the way to go here is to examine where the fix has gone, restore it, and to correct the manpage.

BTW, trying to test another problem, I had already hit this issue that I cannot simply tell logwatch which file to process but rather I have to ensure that the system logs contain what I need them to contain. This is really annoying and I vote with all my hands and legs to change logwatch behaviour to something more sane, to obey what the user wants it to do and do not try to apply some internal magic that cannot be bypassed.


-------

/etc/log.d/conf/logfiles/exim.conf has the logfile of /var/log/exim/main.log,
this should be exim/main.log.

/etc/log.d/conf/logfiles/pureftp.conf has the logfile of
/var/log/pureftp/syslog.log, this should be pureftp/syslog.log.

Below is the strace output showing what the logwatch scripts try to open. 
/u3f2/log is where I am storing my logs.  Log files that are under /var/log
should have relative paths.  For the case of log files such as
/var/spool/autorpm/install.log the correct thing to do would be to not pre-pend
directories to absolute paths.

Finally /var/log and /var/adm should not be searched unconditionally.  There
should be a config variable containing an array of directories to be searched in
order, "/var/log" would be the default for such an array, but the sys-admin
should be free to add others as necessary.

/root/str.29762:stat64("/u3f2/log//var/log/pureftp/syslog.log", 0x81ac0c8) = -1
ENOENT (No such file or directory)
/root/str.29762:stat64("/var/adm//var/log/pureftp/syslog.log", 0x81ac0c8) = -1
ENOENT (No such file or directory)
/root/str.29762:stat64("/var/log//var/log/pureftp/syslog.log", 0x81ac0c8) = -1
ENOENT (No such file or directory)
/root/str.29811:execve("/bin/sh", ["sh", "-c", "/bin/cat
/var/log/pureftp/syslog"...], [/* 28 vars */]) = 0
/root/str.29812:execve("/bin/cat", ["/bin/cat", "/var/log/pureftp/syslog.log"],
[/* 28 vars */])                                = 0
/root/str.29812:open("/var/log/pureftp/syslog.log", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
/root/str.29812:write(2, "/var/log/pureftp/syslog.log", 27) = 27

Comment 1 RHEL Program Management 2023-09-20 23:34:23 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-20 23:35:51 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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