Bug 1427526 - sshd.service: Got notification message from PID [x], but reception only permitted for main PID [y]
Summary: sshd.service: Got notification message from PID [x], but reception only permi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openssh
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-28 13:47 UTC by Paul Stauffer
Modified: 2017-03-06 02:51 UTC (History)
8 users (show)

Fixed In Version: openssh-7.4p1-4.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-06 02:51:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Stauffer 2017-02-28 13:47:03 UTC
Immediately following the openssh-server-7.4p1-3.fc25.x86_64 update, systemd began spewing hundreds of notifications like the following:

Feb 28 08:39:59 wildwest systemd: sshd.service: Got notification message from PID 2959, but reception only permitted for main PID 1438

On several of my F25 systems these messages seem to appear roughly every 3 minutes, but this may be site- or configuration-dependent.  Restarting the service or rebooting the system has no effect on the behavior.

This appears to be the same issue as Debian bug 809035 from a year ago:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809035

In that case, the spawned child sshd processes were incorrectly calling sd_notify(), when only the main parent should do so.  The Debian bug reports that this was fixed in openssh 1:7.1p1-6, so the current manifestation may be a regression in Fedora or upstream.

Comment 1 Jakub Jelen 2017-02-28 14:08:50 UTC
Thank you for the elaborated report and sorry for trouble.
I gave it brief testing, results looked good so I moved on. I missed that the current Debian patch is a bit different then the one discussed in the original bug report which made me to apply this change.

Using this debian patch should solve the problems:

https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=0fd4134

Change itself in
https://anonscm.debian.org/cgit/pkg-ssh/openssh.git/commit/?id=f9c35cb

Can you try with this scratch build, it if will resolve the problems for you:
https://koji.fedoraproject.org/koji/taskinfo?taskID=18107849

It looks good to me so I will submit new builds soon.

Comment 2 Paul Stauffer 2017-02-28 16:37:11 UTC
Confirmed that your 7.4p1-3.1.fc25 build in Koji appears to resolve the problem.

Comment 3 Michal Jaegermann 2017-02-28 23:50:00 UTC
(In reply to Paul Stauffer from comment #0)

> On several of my F25 systems these messages seem to appear roughly every 3
> minutes, but this may be site- or configuration-dependent.

"Got notification message" appears to show up on every attempt to connect to an updated sshd - regardless if accepted or rejected.  Apparently something is doing that on your systems in regular intervals.

Hopefuly this will get resolved "officially" pretty soon.  On a system exposed to numerous bogus login tries this is getting truly annoying.

Comment 4 Fedora Update System 2017-03-03 17:52:56 UTC
openssh-7.4p1-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc8582d738

Comment 5 Paul Stauffer 2017-03-03 18:20:10 UTC
Tested and left positive karma in Bodhi.

Comment 6 Fedora Update System 2017-03-05 04:23:12 UTC
openssh-7.4p1-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc8582d738

Comment 7 Fedora Update System 2017-03-06 02:51:39 UTC
openssh-7.4p1-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.


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