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 2043154 - smb.service: Got notification message from PID [pid1], but reception only permitted for main PID [pid2]
Summary: smb.service: Got notification message from PID [pid1], but reception only per...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: samba
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Filipensky
QA Contact: Denis Karpelevich
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-20 17:53 UTC by Paul Stauffer
Modified: 2022-05-10 16:50 UTC (History)
7 users (show)

Fixed In Version: samba-4.15.5-0.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2049485 (view as bug list)
Environment:
Last Closed: 2022-05-10 15:27:46 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 RHELPLAN-109019 0 None None None 2022-01-20 17:55:16 UTC
Red Hat Issue Tracker SSSD-4305 0 None None None 2022-02-02 13:20:08 UTC
Red Hat Product Errata RHSA-2022:2074 0 None None None 2022-05-10 15:28:17 UTC
Samba Project 14947 0 None None None 2022-02-02 10:33:30 UTC

Description Paul Stauffer 2022-01-20 17:53:46 UTC
Description of problem:

The "[Service]" section of /usr/lib/systemd/system/smb.service included with samba-4.15.3-0.el8.x86_64 has "Type=notify".  When the service is started, one of more instances of the following message are produced: "smb.service: Got notification message from PID [pid of child process], but reception only permitted for main PID [pid of the main smbd process]".  The Service section should be amended to include "NotifyAccess=all" to allow systemd to accept notifications from all members of the service's control group.  See the systemd.service(5) man page for more information.  This extra line is already present in the RHEL7 version of this package, which does not exhibit this behavior.

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

samba-4.15.3-0.el8.x86_64

How reproducible:

100%

Steps to Reproduce:
1. dnf install samba
2. systemctl start smb.service

Actual results:

systemctl status smb.service | grep notification
Jan 19 15:10:38 hostname.example.com systemd[1]: smb.service: Got notification message from PID 3694238, but reception only permitted for main PID 3694231

Expected results:

Error should not occur.

Additional info:

Comment 5 errata-xmlrpc 2022-05-10 15:27:46 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 (Moderate: samba security, bug fix, and enhancement update), 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/RHSA-2022:2074


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