Red Hat Bugzilla – Bug 594693
ypbind probes for the fastest server too often
Last modified: 2013-10-31 21:33:41 EDT
+++ This bug was initially created as a clone of Bug #594668 +++
Description of problem:
The ypbind manual page says that it checks the current server every 20s to confirm it is up, and also pings all configured servers every 15 minutes to check on which is currently the fastest to respond. In fact it pings the servers every minute which may cause ypbind to flip the servers very often.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure ypbind to try to contact more servers, i.e. add two servers to /etc/yp.conf (one of them must be reachable):
2. start ypbind in the debug mode
3. it logs out the pings of the servers
The "Check new for fastest server." logs appear every minute:
The "Check new for fastest server" logs appear every 15 minutes (as documented)
This seems to be caused by the ypbind-mt-1.19-log-binds.patch which contains the following chunk:
@@ -1031,7 +1067,8 @@ test_bindings (void *param __attribute__
lastcheck += ping_interval;
- if (lastcheck >= 900) /* 900 = 15min. */
+ //if (lastcheck >= 900) /* 900 = 15min. */
+ if (lastcheck >= 60) /* 900 = 15min. */
At the first glance it looks like this has been added for the debugging purposes to test the patch for the bug #198689. We should revert this part or explain why does the interval have to be shortened this much and fix the documentation.
--- Additional comment from firstname.lastname@example.org on 2010-05-21 06:55:09 EDT ---
Correct, it seems it was added for debugging purposes.
The limit should be set back to 900.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.