Re: Admin server startup errors 1.0.4-1 on RHEWS3

[Rich Megginson <rmeggins@xxxxxxxxxx>]

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@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

<<attachment: smime.p7s>>

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users