Dear Maintainer,

krb5-kdc is missing a dependency on libverto-libev1. Or something krb5
depends on does. Doing a "safe-upgrade" recently, slapd failed to start
because the kdc failed to start. The syslog error message was:
    Cannot allocate memory - while creating main loop

Plently of free space. Looking at the code I saw the libvert loading and
on a random hunch installed libverto-libev1 since it was the only
libverto* package I didn't have installed. This allowed kdc to start.

Hi.  It sounds from your report like you are saying that you had
libverto1 and libverto-glib1 installed but not libverto-libev1, and
that the kdc failed to function.

Is that correct?

Hi,

I observed the same behaviour:

 >> Hi.  It sounds from your report like you are saying that you had
 >> libverto1 and libverto-glib1 installed but not libverto-libev1, and
 >> that the kdc failed to function.

 > Is that correct?

Absolutely. Only when libverto-libev1 is installed, kdc and kadmind will
start.

Regards,
Jens

I'd like to add that I am seeing this issue as well; have been since Nov 30 or so, but haven't gotten around to fixing it until now.

I wasn't able to get my kdc to start (debian+sid+mit kerberos)

After following Josh's advice of adding libverto-libev1, I was able to start both my KDC and kadmin server.
--
Troy Telford
troy.telford@gmail.com

control: tags -1 confirmed
control: reassign -1 libverto1
control: found -1 libverto1/0.2.2-1

Yeah, I can reproduce.
The way this issupposed to work is that  libverto1 should work with any
of the plugins.
However, it appears the glib plugin is broken.