On Mon, Apr 21, 2014 at 10:05:58AM -0400, Stephen Gallagher wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On 04/17/2014 04:13 AM, Jakub Hrozek wrote:
> On Wed, Apr 16, 2014 at 10:47:10PM -0400, Simo Sorce wrote:
>> On Wed, 2014-04-16 at 19:49 -0400, Dmitri Pal wrote:
>>> I had some interesting experience during Red Hat summit. The
>>> network was significantly overloaded. The VPN was slow and
>>> probably bleeding packets on the way like crazy. Any access to
>>> internal web page took a while and was happening in multiple
>>> steps. When screen was locking it was taking about 30 sec (I
>>> have not measured but that was a feeling) to log in. I am not
>>> sure we can do much about it but the flaky network is probably
>>> going to lead to some timeouts and bad user experience.
>> I think this may be a recent regression. We are never supposed to
>> wait more than a handful of seconds, but I am noticing that with
>> latest RHEL6 updates my RHEL desktop also sometimes gets stuck a
>> while on authentication (VPN). I have not experienced this in F20
>> (but my domain controller is local).
> Simo, if you can reproduce the error locally, would you mind
> enabling debug logs or trying out the 6.6 preview packages?
> I only have headless VMs with RHEL6 and I'm not sure I could
> reproduce the bug there. But it sounds like something we should
> fix, so any debug information would be welcome, at least to know
> where to start with local debugging.
> btw when I tried to reproduce the bug Thomas was seeing, I saw
> some blocking DNS calls in openldap's initialization path, but that
> was on F-20.
OpenLDAP isn't supposed to be calling DNS at all. That's the entire
reason we open the port ourselves now and then pass the FD to it. If
it suddenly started running DNS, that's probably a regression in the
OK, I will do a bit more testing later this week, after I finish some
patches for Jan P. I think this would result in an openldap bug report.