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.

Bug 1747494

Summary:	suspicious logs on service start
Product:	Red Hat Enterprise Linux 8	Reporter:	Dalibor Pospíšil <dapospis>
Component:	fapolicyd	Assignee:	Radovan Sroka <rsroka>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	rsroka
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.2	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	fapolicyd-0.9.1-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:58:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dalibor Pospíšil 2019-08-30 15:24:25 UTC

Description of problem:
following messages look scary:
Data miscompare for /usr/bin/pip-3:0 16 0000000000000000000000000000000000000000000000000000000000000000 vs 0 0 0000000000000000000000000000000000000000000000000000000000000000
Found 1 problems

This should be in debug level, while in info or higher it should be rephrased to something more conservative.

Version-Release number of selected component (if applicable):
fapolicyd-0.8.10-3.el8

How reproducible:
100%

Steps to Reproduce:
1. # systemctl start fapolicyd
2. # systemctl status fapolicyd
● fapolicyd.service - File Access Policy Daemon
   Loaded: loaded (/usr/lib/systemd/system/fapolicyd.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2019-08-30 16:57:54 CEST; 4s ago
  Process: 3365 ExecStart=/usr/sbin/fapolicyd (code=exited, status=0/SUCCESS)
 Main PID: 3366 (fapolicyd)
    Tasks: 1 (limit: 4931)
   Memory: 33.8M
   CGroup: /system.slice/fapolicyd.service
           └─3366 /usr/sbin/fapolicyd

Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com systemd[1]: Starting File Access Policy Daemon...
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com systemd[1]: fapolicyd.service: Can't open PID file /run/fapolicyd.pid (yet?) after start: No such file or directory
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Initialization of the database
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Checking database
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com systemd[1]: Started File Access Policy Daemon.
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Data miscompare for /usr/bin/pip-3:0 16 0000000000000000000000000000000000000000000000000000000000000000 vs 0 0 0000000000000000000000000000000000000000000000000000000000>
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Found 1 problems
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Updating database
Aug 30 16:57:54 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Reading RPMDB into memory
Aug 30 16:57:56 sopos-rhel8-brq.usersys.redhat.com fapolicyd[3366]: Creating database

Comment 1 Marek Tamaskovic 2019-11-04 11:46:53 UTC

Created PR on upstream: https://github.com/linux-application-whitelisting/fapolicyd/pull/51

Comment 14 errata-xmlrpc 2020-04-28 15:58:54 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/RHEA-2020:1687