Bug 1383484 - abrt-watch-log request for change in behavior and documentation
Summary: abrt-watch-log request for change in behavior and documentation
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 34
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 18:37 UTC by David Mathog
Modified: 2022-06-07 19:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-07 19:54:22 UTC
Type: Bug


Attachments (Terms of Use)

Description David Mathog 2016-10-10 18:37:02 UTC
Description of problem:
Request for change in behavior and documentation for abrt-watch-log.

abrt-watch-log parameters are exposed in 'ps -ef' and similar.  Unless the operator knows how abrt-watch-log works and what it does the process listed appears to be indicating some sort of problem rather than normal operation LOOKING for a problem.  Additionally, the man page documentation is so sparse as to be essentially useless, for instance, it does not describe "--".  

Specifically, in "ps -ef" this appears:

/usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD

There are problems with this .  It looks like something dreadful has happened, with an assortment of (sometimes corrupted) warning strings appearing.  It reveals what appears to be a primitive pattern matching system (that is, to match "kernel" or "Kernel" the string "ernel" is entered in -F).  The "--" which appears is not documented in the man page.

Suggested changes are:

1.  Man page: document the "--", describe what the program does with greater specificity ("watch" is ambiguous), reference other parts of abrt, eliminate the double negative in the -F description.  A naive reading of the current documentation is that every time the file expands the command will run no matter where in the file the -F string occurs.  Presumably what it actually does is only run the command once, when the string appears in the newly expanded portion of the file.

2.  put all abrt-watch-log parameters in a configuration file, so that the "-F" parameters are hidden, and all one sees with "ps" is:  abrt-watch-log -c /etc/sysconfig/abrt-watch-log.conf /var/log/messages -- /usr/bin/abrt-dump-oops -xtD, or something similar.

3.  Allow regular expressions in the configuration file.




Version-Release number of selected component (if applicable):


How reproducible:
always


Steps to Reproduce:
1. boot system
2. login
3. ps -ef | grep abrt

Actual results:


Expected results:


Additional info:

Comment 2 Miroslav Suchý 2020-02-12 15:53:05 UTC
We will very likely have no resources to fix this bug during Red Hat Enterprise Linux 7 time life. Moving to upstream. If you insisted on fixing in Red Hat Enterprise Linux 7 please open a support ticket.

Comment 3 Ben Cotton 2020-08-11 13:03:16 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 4 Ben Cotton 2021-02-09 16:22:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 5 Ben Cotton 2022-05-12 14:50:21 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Ben Cotton 2022-06-07 19:54:22 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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