On Fri, Dec 21, 2007 at 01:13:00PM -0800, Mike Marion wrote: > Even weirder... I built a new box in our lab to use for testing and > found that a small subset of paths didn't get loaded in the initial > startup.. but when the default 10min timeout happened, they were then > added. That subset exactly matches the subset we're seeing the bug > with. Nothing obvious in verbose output as to why it didn't load those > paths initially.
Well I have tracked down what appears to be the root cause. The above made me run a loop of ldapsearch queries against our ldap farm and I found that periodically I would get a return missing the exact paths we're seeing being removed then re-added over and over. We have a CSS setup to handle load balancing and failover for the ldap farm and I found that one server behind it is giving out the broken maps. Working on getting that fixed ASAP (I'm not the ldap guy). No details on why this happening over several hours would eventually get the daemon into a state where it finally core-dumped though. But fixing the map results should make that not happen anymore anyway. If I can manage to catch a debug output and/or strace of one that still core-dumps before the ldap side is fixed, I'll pass it along. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com "Do you know what this is? No, I can see you don't. You have that vacant look in your eyes that says, 'Place my head to your ear.. you will hear the sea!'" --Londo, Babylon 5. _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
