Description of problem: /etc/rc.d/init.d/ypbind occasionally fails to wait for ypbind server to be started, and hance executes a 'stop' Version-Release number of selected component (if applicable): ypbind-1.19-9.fc7 How reproducible: Sometimes Steps to Reproduce: 1. service ypbind start Actual results: Service sometimes fails to start Expected results: Started service... Additional info:
Created attachment 158515 [details] Fix to problem
This happens to me as well, except that it consistently fails to start. Here is part of the issue: For whatever reason, on my system, "rpcinfo -p" is only showing the portmapper bindings. /etc/init.d/ypbind uses "rpcinfo -p" to determine if ypbind started successfully. Since ypbind doesn't appear in the output, it concludes that something is wrong and stops the service. "rpcinfo -p localhost" shows the full expected information so I've modified my /etc/init.d/ypbind accordingly. I don't know if this is a bug in rpcinfo or what. Perhaps the fact that I have ipv6 enabled is related? who knows. At the very least, I suggest deploying an interim package which uses the "rpcinfo -p localhost" technique.
(In reply to comment #2) > This happens to me as well, except that it consistently fails to start. Here is > part of the issue: > > For whatever reason, on my system, "rpcinfo -p" is only showing the portmapper > bindings. /etc/init.d/ypbind uses "rpcinfo -p" to determine if ypbind started > successfully. Since ypbind doesn't appear in the output, it concludes that > something is wrong and stops the service. > > "rpcinfo -p localhost" shows the full expected information so I've modified my > /etc/init.d/ypbind accordingly. I don't know if this is a bug in rpcinfo or > what. Perhaps the fact that I have ipv6 enabled is related? who knows. At the > very least, I suggest deploying an interim package which uses the "rpcinfo -p > localhost" technique. Does this mean that my fix doesn't work (which relies on ypwhich only)?
I have been suffering from this problem for some time now. After applying the patch to ypbind init script solved the problem !!!! Thanks!