We had just moved from 1.0.4 to 389 by doing a fresh install then LDIF import. We are doing Master<->Master replication with another machine. Everything was working alright... then we restarted the machine to see if SysV init scripts would bring it up, but did not shut it down appropriately first. Curiously, the GUI management tool can start the server... apparently it does something that we're not doing. Thanks for your help. -----Original Message----- From: 389-users-bounces at lists.fedoraproject.org on behalf of Morris, Patrick Sent: Sat 1/23/2010 12:50 PM To: General discussion list for the 389 Directory server project. Subject: Re: error log showing Detected Disorderly Shutdown on startup Rankin, Kent wrote: > > Upon startup, this is occurring: > > [23/Jan/2010:12:31:42 -0500] - 389-Directory/1.2.4 B2009.307.1545 > starting up > [23/Jan/2010:12:31:42 -0500] - Detected Disorderly Shutdown last time > Directory Server was running, recovering database. > > Any ideas? > How was the the LDAP server shut down before this startup? That message indicates it wasn't shut down cleanly. -- 389 users mailing list 389-users at lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 3546 bytes Desc: not available Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20100123/eebc667c/attachment.bin
