|
Hello All,
I’m working with the new 389 Console for Windows v1.1.6 connecting to my remote server. When opening the console it sits at the "Initializing..." screen for exactly 10
minutes (600 seconds), then the console opens. Once open I see the "Server Group" and the admin/directory servers listed. Any action to open either server takes another 10 minutes.
I made a few config tweaks in admin-serv/local.conf to clear admserv_check notices in the error logs. No other errors are showing in the logs (/var/log/dirsrv/*/*). I’ve lowered the cache settings from the default 600 to 30 for testing in the dse.ldif; no change. Firewalls are off everywhere. I get the same results running the console on the local DS server as I do running from my remote windows desktops (WinXP 32bit and a Win7
64bit desktop; both running Java 1.6.0_20). I am able to connect with Apache Directory Studio and other LDAP browsers without the 10 minute wait time; it seems specific to the console. Any suggestions? Thanks! This electronic message transmission contains information from Black Hills Corporation, its affiliate or subsidiary, which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware the disclosure, copying, distribution or use of the contents of this information is prohibited. If you received this electronic transmission in error, please reply to sender immediately; then delete this message without copying it or further reading. |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
