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.
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 ***