[Fedora-directory-users] Admin server startup errors 1.0.4-1 on RHEWS3

Thu Jan 10 22:14:21 UTC 2008

Raj Seenivasan wrote:
> I have a similar problem with the migration from 1.0.4 to 1.1
> Please HELP!
>
> Below are the steps I followed and the error msgs.
>
> After doing "yum install fedora-ds" ran the migration script.
>
> *[root at ldap log]# migrate-ds.pl -f /tmp/diradm.inf *
> <snip>
Right.  migrate-ds.pl will migrate the directory servers only.  Not any 
of the console or admin server information.
> I tried to run the migarte-ds-admin after doing migrate-ds and below 
> is the error.
>
> *[root at ldap /]# migrate-ds-admin.pl -f /tmp/diradm.inf *
> Beginning migration of Directory and Administration servers from 
> /opt/fedora-ds . . .
> Beginning migration of directory server instances in /opt/fedora-ds . . .
> The target directory server instance already exists at 
> /etc/dirsrv/slapd-ldap/dse.ldif.  Skipping migration.  Note that if 
> you want to migrate the old instance you will have to first remove the 
> new one of the same name.
>
> Beginning migration of Administration server from /opt/fedora-ds . . .
> Creating Admin Server files and directories . . .
> The server 'ldaps://ldap.test.com:636/o=NetscapeRoot' is not 
> reachable.  Error: unknown error
>
> Exiting . . .
> Log file is '/tmp/migraterXVtnt.log'
>
>
> *[root at ldap /]# cat /var/log/dirsrv/admin-serv/error *
> [Thu Jan 10 16:15:18 2008] [crit] mod_admserv_post_config(): unable to 
> create AdmldapInfo
> Configuration Failed
>
> *Also tried to run migrate-ds-admin.pl after a fresh install of 1.1 
> without executing migrate-ds.pl and the same error showed up.*
>
> Please note that I don't have any issues starting/stopping my old 
> instance of fedora-ds and my old instance was completely stopped while 
> performing the above steps.
Take a look at your directory server access log - 
/var/log/dirsrv/slapd-ldap/access - do you see any SSL connection 
attempts from around the time of the "The server 
'ldaps://ldap.test.com:636/o=NetscapeRoot' is not reachable.  Error: 
unknown error" message?

ls -al /etc/dirsrv/admin-serv

/usr/lib/mozldap/ldapsearch -h ldap.test.com -p 636 -Z -P 
/etc/dirsrv/admin-serv -s base -b "" "objectclass=*"
>
> Thanks.
>
>
> On Jan 3, 2008, at 8:05 PM, Rich Megginson wrote:
>
>> Ken Marsh wrote:
>>>
>>> Hi all,
>>>
>>> I gave up on ES5 64 bit due to the FDS/Apache 2.2 httpd.conf 
>>> conflicts. I guess I could craft my own httpd.conf, but I’m not 
>>> feeling creative. J
>>>
>>> I’ve installed fedora-ds-1.0.4-1.RHEL3.i386.opt.rpm on RHEWS3 where 
>>> it is much happier with the Apache 2.0 worker installed there. Once 
>>> again the admin server configuration bombed out,
>>>
>> This is the cause of all of your subsequent problems. If setup fails 
>> to configure the admin server, it will be practically impossible to 
>> do anything else with the admin server or console. So let's start 
>> there. What errors did you get during setup?
>>>
>>> and I can start a console but it finds on admin server to connect 
>>> to. Once again, I hacked up the *.conf.tmpl templates, copied up 
>>> start-admin script and linked the modules and the magic file in from 
>>> their OS locations. Oh yeah, had to set LD_LIBRARY_PATH to 
>>> /opt/fedora-ds/bin/slapd/lib .
>>>
>>> Now when I try to start the admin server, I get no stderr or stdout 
>>> and an exit value of 1. In the admin-serv/logs/error is:
>>>
>>> [Thu Jan 03 18:19:53 2008] [error] (1)Operation not permitted: 
>>> mod_mime_magic: can't read magic file 
>>> /opt/fedora-ds/admin-serv/conf/magic
>>>
>>> [Thu Jan 03 18:19:54 2008] [crit] mod_admserv_post_config(): unable 
>>> to create AdmldapInfo
>>>
>>> Configuration Failed!
>>>
>>> [Thu Jan 03 18:57:46 2008] [crit] mod_admserv_post_config(): unable 
>>> to create AdmldapInfo
>>>
>>> Configuration Failed!
>>>
>>> When I try to check on the config information in the DS, I get this 
>>> error:
>>>
>>> # ./ldapsearch -b o=netscaperoot -D "cn=directory manager" -w 
>>> 'mypassword' "objectclass=nsAdminConfig" dn
>>>
>>> ldap_search: No such object
>>>
>>> Any ideas? It looked like the admin server setup script bombed out 
>>> before it populated the directory server (which seems to be 
>>> running). How do I duplicate what it was supposed to do?
>>>
>>> Perhaps a deeper question, why does the admin setup script bomb out 
>>> on two very different architectures?
>>>
>> This usually has to do with hostname resolution i.e. the hostname you 
>> chose does not resolve to the configured IP address or vice versa.
>>>
>>> Thanks,
>>>
>>> Ken.
>>>
>>> ------------------------------------------------------------------------
>>>
>>> --
>>> Fedora-directory-users mailing list
>>> Fedora-directory-users at redhat.com 
>>> <mailto:Fedora-directory-users at redhat.com>
>>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>>  
>>
>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users at redhat.com 
>> <mailto:Fedora-directory-users at redhat.com>
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3245 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20080110/2aaa24f0/attachment.bin>