Access to the DPS cn=monitor tree

Question

I'd like to be able to access the cn=monitor tree of DPS without having to bind as the proxy manager.
Is there a possible DPS setup to achieve this like using a pool without data source or creating a data
source that point to the proxy itself ?

Answer 1

I had actually the same kind of configuration as the one you mentioned, excepted that I didn't wanted to use an anonymous
bind. In such a case, I had the errors below. Then, I tried to connect as anonymous, and it worked, which should be somewhat
sufficient in my use case.
Anyway, I'm interested in understanding why I had errors/problems when using a specific account.
Of course, I had a connection handler for it, and I also had defined a specific view under cn=config, since I didn't want
to create the user in the directory or in a separate LDIF view.
That view base was "ou=special users,cn=config". I also had to extend the proxy schema to prevent warning messages
about unknown objectclass/attributes in the proxy "server.out" file.
I did it in its own schema file, but never managed the proxy to take it under account.
(So, it seems like it's not recommended/supported to modify the proxy schema, this way at least)
Then, when searching the cn=monitor tree, I had the following behaviour, while it was working at the same time with
an anonymous bind:
ldapsearch -b "cn=monitor" -D "cn=monitoring user,ou=special users,cn=config" -w password objectclass=top
ldap_simple_bind: Operations error
ldap_simple_bind: additional info: Unable to read BIND response from server proxyldaptest:389/
The above errors always came about 40 seconds after the request (??...) with the following access logs
[26/Feb/2009:10:43:22 +0100] - CONNECT - INFO - conn=866 client=127.0.0.1:60772 server=localhost:389 protocol=LDAP
[26/Feb/2009:10:43:22 +0100] - PROFILE - INFO - conn=866 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[26/Feb/2009:10:43:22 +0100] - OPERATION - INFO - conn=866 op=0 BIND dn="cn=monitoring user,ou=special users,cn=config" method="SIMPLE" version=3
[26/Feb/2009:10:43:22 +0100] - SERVER_OP - INFO - conn=866 op=0 BIND dn="cn=monitoring user,ou=special users,cn=config" method="SIMPLE"" version=3 s_msgid=1 s_conn=proxyldaptest:622
[26/Feb/2009:10:43:42 +0100] - OPERATION - INFO - conn=866 op=0 BIND RESPONSE err=1 msg="Unable to read BIND response from server proxyldaptest:389/" s_conn=proxyldaptest:622 server=proxyldaptest Replaying bind operation to s_conn=proxyldaptest:766 server=proxyldaptest:389/
[26/Feb/2009:10:43:42 +0100] - SERVER_OP - INFO - conn=866 op=0 BIND dn="cn=monitoring user,ou=special users,cn=config" method="SIMPLE"" version=3 s_msgid=1 s_conn=proxyldaptest:766
[26/Feb/2009:10:44:05 +0100] - OPERATION - INFO - conn=866 op=0 BIND RESPONSE err=1 msg="Unable to read BIND response from server proxyldaptest.univ-lyon2.fr:389/" etime=42431
[26/Feb/2009:10:44:05 +0100] - OPERATION - INFO - conn=866 op=1 UNBIND
[26/Feb/2009:10:44:05 +0100] - DISCONNECT - INFO - conn=866 reason="unbind"
The error log was as follows:
[26/Feb/2009:10:40:18 +0100] - BACKEND - WARN - No data source available for ADD,DELETE,MODIFY, in data source pool cn=defaultdatasourcepool,cn=datasource pools,cn=config .You may want to check whether the configuration of this pool contains at least one data source enabled and with non-zero weights.
[26/Feb/2009:10:42:18 +0100] - BACKEND - WARN - Error occured to send UNBIND to proxyldaptest:578
[26/Feb/2009:10:42:18 +0100] - BACKEND - WARN - No data source available for ADD,DELETE,MODIFY, in data source pool cn=defaultdatasourcepool,cn=datasource pools,cn=config .You may want to check whether the configuration of this pool contains at least one data source enabled and with non-zero weights.
.... (tons of the same warning)
[26/Feb/2009:10:43:44 +0100] - BACKEND - WARN - No data source available for ADD,DELETE,MODIFY, in data source pool cn=defaultdatasourcepool,cn=datasource pools,cn=config .You may want to check whether the configuration of this pool contains at least one data source enabled and with non-zero weights.
[26/Feb/2009:10:43:48 +0100] - BACKEND - WARN - LDAP server proxyldaptest:389/ is unreacheable.
[26/Feb/2009:10:43:52 +0100] - BACKEND - WARN - Availability check indicated that LDAP server proxyldaptest:389/ is not available. Stopping server.
[26/Feb/2009:10:44:00 +0100] - BACKEND - WARN - Availability check indicated that LDAP server proxyldaptest:389/ is not available. Stopping server.
[26/Feb/2009:10:44:04 +0100] - BACKEND - WARN - Attempt to bind as cn=proxy manager to backend server proxyldaptest.univ-lyon2.fr:389/ failed. Timeout when waiting to read from input stream
[26/Feb/2009:10:44:04 +0100] - BACKEND - ERROR - Failed to create a connection to proxyldaptest:389/
[26/Feb/2009:10:44:04 +0100] - BACKEND - WARN - No data source available for ADD,DELETE,MODIFY, in data source pool
....(tons of the same warning)
see next message for the end ..