Hi,

Yes it appears to be a ldap / dirsrv not starting issue.....Cant see anything 
in the install log, I have raised a case with RH anyway.

I ran the un-install 3 or 4 times and it finally cleaned up.....

regards

Steven Jones

Technical Specialist - Linux RHCE

Victoria University, Wellington, NZ

0064 4 463 6272

________________________________________
From: Rob Crittenden [rcrit...@redhat.com]
Sent: Tuesday, 31 January 2012 4:54 a.m.
To: Steven Jones
Cc: freeipa-users@redhat.com
Subject: Re: [Freeipa-users] unable to install or uninstall ipa

Steven Jones wrote:
> Example of install failure messages,
>
> ======
> Warning: skipping DNS resolution of host vuwunicoipam001.unix.vuw.ac.nz
> The IPA Master Server will be configured with
> Hostname:    vuwunicoipam001.unix.vuw.ac.nz
> IP address:  10.70.3.10
> Domain name: unix.vuw.ac.nz
>
>
> The following operations may take some minutes to complete.
> Please wait until the prompt is returned.
>
> Configuring ntpd
>    [1/4]: stopping ntpd
>    [2/4]: writing configuration
>    [3/4]: configuring ntpd to start on boot
>    [4/4]: starting ntpd
> done configuring ntpd.
> Configuring directory server: Estimated time 1 minute
>    [1/35]: creating directory server user
>    [2/35]: creating directory server instance
>    [3/35]: adding default schema
>    [4/35]: enabling memberof plugin
> root        : CRITICAL Failed to load memberof-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/memberof-conf.ldif -x -D cn=Directory Manager -y 
> /tmp/tmpkbE724' returned non-zero exit status 255
>    [5/35]: enabling referential integrity plugin
> root        : CRITICAL Failed to load referint-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/referint-conf.ldif -x -D cn=Directory Manager -y 
> /tmp/tmpExKKnk' returned non-zero exit status 255
>    [6/35]: enabling winsync plugin
> root        : CRITICAL Failed to load ipa-winsync-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/ipa-winsync-conf.ldif -x -D cn=Directory Manager -y 
> /tmp/tmppChSx9' returned non-zero exit status 255
>    [7/35]: configuring replication version plugin
> root        : CRITICAL Failed to load version-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/version-conf.ldif -x -D cn=Directory Manager -y 
> /tmp/tmpqy9Fkp' returned non-zero exit status 255
>    [8/35]: enabling IPA enrollment plugin
> root        : CRITICAL Failed to load enrollment-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f /tmp/tmpoWPpcO 
> -x -D cn=Directory Manager -y /tmp/tmpxbRGyx' returned non-zero exit status 
> 255
>    [9/35]: enabling ldapi
> root        : CRITICAL Failed to load ldapi.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f /tmp/tmpVSJoE2 
> -x -D cn=Directory Manager -y /tmp/tmpqsK_aD' returned non-zero exit status 
> 255
>    [10/35]: configuring uniqueness plugin
> root        : CRITICAL Failed to load unique-attributes.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f /tmp/tmpWJEh76 
> -x -D cn=Directory Manager -y /tmp/tmpzxvY9u' returned non-zero exit status 
> 255
>    [11/35]: configuring uuid plugin
> root        : CRITICAL Failed to load uuid-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/uuid-conf.ldif -x -D cn=Directory Manager -y /tmp/tmpdYNh2T' 
> returned non-zero exit status 255
> root        : CRITICAL Failed to load uuid-ipauniqueid.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f /tmp/tmpkEOmk2 
> -x -D cn=Directory Manager -y /tmp/tmp9ZDoXY' returned non-zero exit status 
> 255
>    [12/35]: configuring modrdn plugin
> root        : CRITICAL Failed to load modrdn-conf.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/modrdn-conf.ldif -x -D cn=Directory Manager -y /tmp/tmpofFRs8' 
> returned non-zero exit status 255
> root        : CRITICAL Failed to load modrdn-krbprinc.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f /tmp/tmpDxRP25 
> -x -D cn=Directory Manager -y /tmp/tmpUexNQN' returned non-zero exit status 
> 255
>    [13/35]: enabling entryUSN plugin
> root        : CRITICAL Failed to load entryusn.ldif: Command 
> '/usr/bin/ldapmodify -h vuwunicoipam001.unix.vuw.ac.nz -v -f 
> /usr/share/ipa/entryusn.ldif -x -D cn=Directory Manager -y /tmp/tmpgsBw1B' 
> returned non-zero exit status 255
> =========
>
>
> regards
>
> Steven Jones
>
> Technical Specialist - Linux RHCE
>
> Victoria University, Wellington, NZ
>
> 0064 4 463 6272
>
> ________________________________________
> From: freeipa-users-boun...@redhat.com [freeipa-users-boun...@redhat.com] on 
> behalf of Steven Jones [steven.jo...@vuw.ac.nz]
> Sent: Monday, 30 January 2012 2:03 p.m.
> To: freeipa-users@redhat.com
> Subject: [Freeipa-users] unable to install or uninstall ipa
>
> I have a failed install with lots of critical failures...
>
> :(
>
> When I try to re-install it says its installed but when I try to --uninstall 
> it will not.....
>
> How do I clean it up manually?
>
> ========
> [root@vuwunicoipam001 ~]# ipa-server-install --uninstall
>
> This is a NON REVERSIBLE operation and will delete all data and configuration!
>
> Are you sure you want to continue with the uninstall procedure? [no]: yes
> Shutting down all IPA services
> Removing IPA client configuration
> Unconfiguring directory server
> Unexpected error - see ipaserver-uninstall.log for details:
>   [Errno 2] No such file or directory: '/etc/dirsrv/slapd-UNIX-VUW-AC-NZ'
> [root@vuwunicoipam001 ~]#
> ========

To clean it up look at the files in /var/lib/ipa/sysrestore. There
you'll find files that were backed up, a state file indicating the
initial state when the installer started and an index file which
accounts for all the backup files.

You can remove [dirsrv] from the state file perhaps but be sure the
instance really is gone.

It is safe to re-run the uninstaller multiple times and sometimes this
is required to get everything cleaned up on some kinds of failures.

The problem is that the 389-ds isn't starting up for some reason. You
may find the reason why in /var/log/ipaserver-install.log or the 389-ds
logs.

rob

_______________________________________________
Freeipa-users mailing list
Freeipa-users@redhat.com
https://www.redhat.com/mailman/listinfo/freeipa-users

Reply via email to