Bug 1683711 - init script does not tell errors via correct syslog level
Summary: init script does not tell errors via correct syslog level
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipset
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: Stefano Brivio
QA Contact: Tomas Dolezal
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 1682315
Blocks: 1701002 1689408
TreeView+ depends on / blocked
 
Reported: 2019-02-27 15:53 UTC by Stefano Brivio
Modified: 2019-11-05 22:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
.Error logging in the `ipset` service has been improved Previously, the `ipset` service did not report configuration errors with a meaningful severity in the `systemd` logs. The severity level for invalid configuration entries was only `informational`, and the service did not report errors for an unusable configuration. As a consequence, it was difficult for administrators to identify and troubleshoot issues in the `ipset` service's configuration. With this update, `ipset` reports configuration issues as `warnings` in `systemd` logs and, if the service fails to start, it logs an entry with the `error` severity including further details. As a result, it is now easier to troubleshoot issues in the configuration of the `ipset` service.
Clone Of: 1649877
Environment:
Last Closed: 2019-11-05 22:25:10 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3593 None None None 2019-11-05 22:25:20 UTC

Comment 5 errata-xmlrpc 2019-11-05 22:25:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3593


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