Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1398020 - ypbind wont start
Summary: ypbind wont start
Keywords:
Status: CLOSED DUPLICATE of bug 1396893
Alias: None
Product: Fedora
Classification: Fedora
Component: ypbind
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matej Mužila
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-23 21:40 UTC by Stephen Adler
Modified: 2016-11-25 13:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-25 13:10:22 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Stephen Adler 2016-11-23 21:40:24 UTC 
Description of problem:
systemd times out when starting ypbind

Version-Release number of selected component (if applicable):
ypbind.x86_64                    3:1.38-6.fc25

How reproducible:
every time

Steps to Reproduce:
1. execute 'systemctl start ypbind.service'
2.
3.

Actual results:
fails to start

Expected results:
properly start ypbind

Additional info:
If I open a 2nd terminal window, then I can do the following
in 1st window I type 'systemctl start ypbind.service'
in 2nd window just after typing systemctl start ypbind.service in the first I type 'ypwhich'
I get back the proper result of the NIS service being bound to the proper NIS domain. So the ypbind is started, but then systemctl command hangs waiting for it to start, but it has started.

after about 2 minutes, the original systemct start command returns with a fail state of time out. Then when I type 'ypwhich' I get an error telling me NIS is not bound.

So there is something going on with ypbind in which it's not properly telling systemctl that it started.
Comment 1 Stephen Adler 2016-11-25 13:10:22 UTC 
looks like there is another bug submitted which is a replica of this one. The other bug report seems to be addressing this problem.

https://bugzilla.redhat.com/show_bug.cgi?id=1396893

You can close down this bug if you wish.

*** This bug has been marked as a duplicate of bug 1396893 ***
Note You need to log in before you can comment on or make changes to this bug.