Latest cyrus-sasl 2.1.25 introduces a new mechanism called SCRAM. Unlike the other mechanisms, SCRAM generates entropy as soon as the cyrus-sasl library is loaded. This is a problem because cyrus-sasl defaults to using /dev/random instead of /dev/urandom when it loads up. I was having numerous test failures until gdb'ing slapd and finding it was stuck initializing SCRAM while starting up.
If you rebuild cyrus-sasl to use /dev/urandom (They thankfully have a configure switch for it), things'll work a lot more smoothly.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Quanah Gibson-Mount wrote:
Latest cyrus-sasl 2.1.25 introduces a new mechanism called SCRAM. Unlike the other mechanisms, SCRAM generates entropy as soon as the cyrus-sasl library is loaded. This is a problem because cyrus-sasl defaults to using /dev/random instead of /dev/urandom when it loads up. I was having numerous test failures until gdb'ing slapd and finding it was stuck initializing SCRAM while starting up.
If you rebuild cyrus-sasl to use /dev/urandom (They thankfully have a configure switch for it), things'll work a lot more smoothly.
Seems this might be the cause for (closed) ITS#7069 and ITS#7070.
Ciao, Michael.
-
Michael Ströder -
Quanah Gibson-Mount