On Sun, 12 Feb 2012, Marco Pizzoli wrote:
> On Sun, Feb 12, 2012 at 5:41 PM, Alexander Bokovoy <aboko...@redhat.com>wrote:
> > On Sun, 12 Feb 2012, Marco Pizzoli wrote:
> > > I'm having the same issue with another freeipa setup which was installed
> > > directly from the updates-testing repository.
> > > He was working correctly once installed but then, after the first
> > power-on
> > > after the installation, no working from the 389-ds side.
> > >
> > > [12/Feb/2012:16:19:44 +0100] - 389-Directory/1.2.10.rc1 B2012.035.328
> > > starting up
> > > [12/Feb/2012:16:19:44 +0100] - Detected Disorderly Shutdown last time
> > > Directory Server was running, recovering database.
> > > [12/Feb/2012:16:19:44 +0100] - libdb: unable to join the environment
> > So there is something fishy with 389-ds shutdown on reboots? Am I
> > correct in assuming that you had FreeIPA working after install, then
> > power cycled the VM and after restart it didn't come back online?
> Well, just to be clear, each time I talked about reboot actually I intended
> "shutdown -h now" and powering on the day after.
> Was there anything specific about shutdown? Anything similar to
> > https://fedorahosted.org/freeipa/ticket/2302 ?
> I don't get hangs or other type of similar evidences. My system just
> complete (correctly, it seems) a shutdown sequence.
> I am not yet an expert about systemd, so I don't know if it's just going to
> kill the service if it doesn't respond in a specific time to a request to
> shut down.
> I'm working with more than one virtual machine active on my not-so-new
> laptop, so the promptness of response is very low...
> If you want me to do any kind of test, just let me know.
If you could reproduce similar results with new VM, it would be good
to get access to the 389-ds database in question and exact steps to
reproduce the failure.
/ Alexander Bokovoy
Freeipa-users mailing list