Quite odd, I copied the database into a new 4.0.5 installation and everything is working fine except that it says that LDAP is not running on a LDAP server we have. I know for a fact that the server hasn't been touched, so what's going on?
This is the expression used in the trigger: {Template App LDAP Service:net.tcp.service[ldap].max(#3)}=0
There are no macros defined or anything else. If I ldapsearch to the LDAP server on port 389 it replies.:
[root@pc543 ~]# ldapsearch -x -h ldapserver.nodomain.com
# extended LDIF
#
# LDAPv3
# base <> (default) with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
[root@pc543 ~]#
So, has anything changed in the ldap simple check?
Thanks
/A
This is the expression used in the trigger: {Template App LDAP Service:net.tcp.service[ldap].max(#3)}=0
There are no macros defined or anything else. If I ldapsearch to the LDAP server on port 389 it replies.:
[root@pc543 ~]# ldapsearch -x -h ldapserver.nodomain.com
# extended LDIF
#
# LDAPv3
# base <> (default) with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
[root@pc543 ~]#
So, has anything changed in the ldap simple check?
Thanks
/A
Comment