Has anyone had an instance where CallManager (ver. 6.1) has aborted an LDAP sync and erased all the LDAP users from its database?
During the latest sync, our LDAP server had this error in its logs:
"Server failed to flush BER data back to client -"
And in doing research the server will display this error if the client closes the connection before the server is done sending data to it. As a result, this seemingly caused the sync to abort and all the LDAP End Users to be unavailable from CallManager. I had to perform a re-sync for them to appear again (without device associations, RDPs, etc. -- which I had to redo b/c of an unknowing backup that had failed).
This is the first time this has occurred and seems to be the result of the a massive purge of nearly 10,000 accounts in LDAP. Is there any configurable setting that I can change within CallManager to increase the timeout value? I'm hoping I won't get burned by this the next time we have a purge.
2008-06-22 22:00:20,111 ERROR [DSLDAPSyncImpl(879a6223-bb24-cf76-1cc9-5c2c2134335b)] ldapplugable.DSLDAPSyncImpl (DSLDAPSyncImpl.java:343) - LDAPSync(879a6223-bb24-cf76-1cc9-5c2c2134335b)[Run] SizeLimit configured in directory is less than the number of \
results retrieved. Cannot continue.\
2008-06-22 22:00:20,113 INFO [DSLDAPSyncImpl(879a6223-bb24-cf76-1cc9-5c2c2134335b)] ldapplugable.DSLDAPSyncImpl \
I was unable to view CSCsk09658...only Cisco employees allowed. But we are using a Sun One directory server. I will run that setting by our LDAP admin to see what it's currently set for and if it needs changed.
The other two bugs you have listed do not pertain to our setup since we're using a specific OU to sync up with, not the root directory.
The question I have is why did it all the sudden error out when it had been performing syncs for the last few weeks without a problem? And when it did error out, why did it wipe out all the LDAP accounts within UCM (not to mention all their device associations, permissions, etc)?
We were wondering if it was possible to customize the search filter, not the search base? It would be better if we didn't have to sync the entire directory every time, but only active users.
Also, the problem also may be attributed to hitting another server we had in our LDAP list, one that is configured to have a limit. I have since removed it from the list entirely since we will never use it for this purpose, but I can't see anything in the dirsync logs that would verify this.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.