Bug 1161003

Summary: rpcbind service stopped disturbs systemd
Product: Red Hat Enterprise Linux 7 Reporter: XuWang <xuw>
Component: systemdAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: Branislav Blaškovič <bblaskov>
Severity: low Docs Contact:
Priority: low    
Version: 7.1CC: bblaskov, eguan, jscotka, lnykryn, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: systemd-219-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 15:02:03 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:
Attachments:
Description Flags
create 8000 entries to export
none
Test srpm package none

Description XuWang 2014-11-06 06:06:34 UTC
Description of problem:

Stop rpcbind service using "service rpcbind stop" and watch the status of firewall using "service firewall status", which will halt quit a while and output the error like "Failed to get D-Bus connection: Failed to authenticate in time."
I first find it in ppc64, and reproduce it in x86_64 of RHEL7.1.

Version-Release number of selected component (if applicable):
distro: RHEL-7.1-20141028.n.0
systemd-208-15.el7.ppc64
rpcbind-0.2.0-25.el7.ppc64

How reproducible:
always

Steps to Reproduce:
1.service rpcbind stop
2.serivce firewall status

Actual results:

service firewall status
long waiting.......(2~3 minutes)
Redirecting to /bin/systemctl status  firewall.service
Failed to get D-Bus connection: Failed to authenticate in time.

Expected results:

rpcbind service should not affect the behavior of other services operation

Additional info:

Comment 2 XuWang 2014-11-06 07:22:12 UTC
Created attachment 954327 [details]
create 8000 entries to export

Comment 3 XuWang 2014-11-06 07:35:32 UTC
Sorry for missing detail description.
I am just running the heavy stress test case for NFS.
Attachment 954327 [details] above is the script I create the export entries. And the bug occured after I starting the nfs service.
I first stop the rpcbind by "service rpcbind stop", and then key in the "serivce firewall status" to check the fireware status. And error happens like below:

long waiting.......(2~3 minutes)
Redirecting to /bin/systemctl status  firewall.service
Failed to get D-Bus connection: Failed to authenticate in time.

And when I minus the nfs export entries from 8000+ to 1, the bug disappeared.
I think even though someting wrong with special service(such as rpcbind/nfs), the other services(fiewall) should not be affected in systemd. So I reported it as bug to check the supposed behavior of systemd.

Comment 4 Lukáš Nykrýn 2014-11-06 09:01:58 UTC
Thanks for the reproducer, it is nicely reproducible on my machine and I have a hunch where the problem might be. But it will require some further investigation.

Comment 5 Lukáš Nykrýn 2014-11-07 15:09:05 UTC
Created attachment 954969 [details]
Test srpm package

Here is a test srpm package. It contains two huge backported patches from upstream and it seems to fix the bug.

Comment 7 Lukáš Nykrýn 2015-01-13 16:02:18 UTC
Does this solves your case?

Comment 8 XuWang 2015-01-19 11:40:50 UTC
(In reply to Lukáš Nykrýn from comment #7)
> Does this solves your case?

Thanks for your work, I think this new systemd srpm solved my case perfectly.

I build the srpm, install and reboot system to make it effective.
And it seems to work fine.

Before use the new systemd, the service rpcbind/nfs start will hung, and the firewalld will also be influenced; but with the new systemd, the rpcbind start/restart/stop and the nfs start/restart/stop is very fast with the 8000+ export entries.
And I mentioned the firewalld hung a long time when rpcbind/nfs working wrong, but with the new systemd, rpcbind/nfs works so good, and firewalld works fine too.

Comment 10 Lukáš Nykrýn 2015-05-12 14:39:16 UTC
fixed by rebase

Comment 14 errata-xmlrpc 2015-11-19 15:02:03 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://rhn.redhat.com/errata/RHBA-2015-2092.html