sorry
The msg showed is not an error.
I made that mistake because I associate - wrong - these message with the
output of dirserv-admin log with the error msg from the console ("Failed to
install a local copy of 389-ds-1.2.6.jar or one if its supporting
files....")...
bye
2013/4/29 Maximiliano de Mattos <[email protected]>
> hi...
>
> well... i found that i need to set these values
>
> nsAdminAccessAddresses: *
> nsAdminAccessHosts:
>
> in admis serv config...
>
> so now, I have these errors (one less!)
>
> [Mon Apr 29 10:13:03 2013] [notice] [client 192.168.41.201]
> admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth
> handler
>
> any ideas? :(
>
> thanks in advance! ;)
>
>
> 2013/4/26 Maximiliano de Mattos <[email protected]>
>
>> ok...
>>
>> I setup a dns to bring resolution for remote machine and looks ok
>>
>> remote_machine# host 192.168.41.201
>> 201.41.168.192.in-addr.arpa domain name pointer ldap01.maximatt.com
>> remote-machine# host ldap01.maximatt.com
>> ldap01.maximatt.com has address 192.168.41.201
>>
>> well.. I had thought of a remote chance to fix the problem by a dns
>> resolve (I had to try it)
>> But no... the problem persist..
>>
>> [Fri Apr 26 10:51:37 2013] [notice] [client 192.168.41.201]
>> admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.41.201
>> [Fri Apr 26 10:51:37 2013] [notice] [client 192.168.41.201]
>> admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth
>> handler
>>
>> any idea? :(
>>
>>
>> thanks in advance! ;)
>>
>>
>>
>>
>>
>> 2013/4/26 Maximiliano de Mattos <[email protected]>
>>
>>> mmmm
>>>
>>> well.. I was supposed that I have the dns resolution ok... but it's not
>>> true :(
>>> I go fix dns resolution and try again whats happends...
>>>
>>> bye!
>>>
>>>
>>> 2013/4/26 Maximiliano de Mattos <[email protected]>
>>>
>>>> Hi...
>>>>
>>>> Well.. I found admin-serv log, and exists these messages :
>>>>
>>>> [Fri Apr 26 08:46:54 2013] [notice] [client 192.168.41.201]
>>>> admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth
>>>> handler
>>>> [Fri Apr 26 08:53:35 2013] [notice] [client 192.168.41.201]
>>>> admserv_host_ip_check: ap_get_remote_host could not resolve 192.168.41.201
>>>>
>>>> so, looking for these errors, I found this *Bug
>>>> 846448*<https://bugzilla.redhat.com/show_bug.cgi?id=846448>,
>>>> where recomend to change admin-serv conf:
>>>> http://directory.fedoraproject.org/wiki/Howto:AdminServerLDAPMgmt
>>>>
>>>> I change the admin-serv conf like the wiki saids, but I still cannot
>>>> acces to ldap instance from remote admin-serv. I receive the same log
>>>> message (but in diferent order)..
>>>>
>>>> any ideas? :(
>>>>
>>>> thanks in advance! ;)
>>>>
>>>>
>>>>
>>>> 2013/4/26 Maximiliano de Mattos <[email protected]>
>>>>
>>>>> Hi,
>>>>>
>>>>> I'm starting with 389ds, and I have installed in a remote server a
>>>>> intance of 389ds.
>>>>> Well... I can connect remotely from 389ds console to this server, but
>>>>> when I want to go in console to items "Administrarion Server" or
>>>>> "Directory
>>>>> Server" I receive the followin error messages:
>>>>>
>>>>> "Failed to install a local copy of 389-admin-1.1.jar or one of its
>>>>> supporting files......"
>>>>> "Failed to install a local copy of 389-ds-1.2.6.jar or one if its
>>>>> supporting files...."
>>>>>
>>>>> But looking for this jar files, I can found them
>>>>> (/usr/share/dirsrv/html/java/) in the local computer with 389ds console..
>>>>> but I cannot find a log of 389ds console to see whats happend.. :(
>>>>>
>>>>> some ideas? :(
>>>>>
>>>>> thanks in advance! ;)
>>>>>
>>>>>
>>>>>
>>>>> ****
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Salu2 ;)*
>>>
>>>
>>>
>>>
>>> --
>>> *Salu2 ;)*
>>
>>
>>
>>
>> --
>> *Salu2 ;)*
>
>
>
>
> --
> *Salu2 ;)*
--
*Salu2 ;)*
--
389 users mailing list
[email protected]
https://admin.fedoraproject.org/mailman/listinfo/389-users
