FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Directory

 
 
LinkBack Thread Tools
 
Old 10-11-2010, 07:29 PM
"Wendt, Trevor"
 
Default Slow Console Interaction

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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 10-11-2010, 08:48 PM
Rich Megginson
 
Default Slow Console Interaction

Wendt, Trevor wrote:
>
> 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?
>
No idea. Try running the console with 389-console -D 9 -f console.log -
see if there are any clues in console.log
>
> 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@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 10-11-2010, 11:16 PM
"Wendt, Trevor"
 
Default Slow Console Interaction

Rich,

Ran the console in debug mode and got "Console: cannot connect to the user database" after my 10 minute wait. The slapd service was up and running the entire time.

Figured out that the console does a reverse DNS lookup and could not resolve the entry. Fixed the dns entry and the console now works as expecteded.

Appreciate the help!



-----Original Message-----
From: 389-users-bounces@lists.fedoraproject.org [mailto:389-users-bounces@lists.fedoraproject.org] On Behalf Of Rich Megginson
Sent: Monday, October 11, 2010 2:48 PM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Slow Console Interaction

Wendt, Trevor wrote:
>
> 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?
>
No idea. Try running the console with 389-console -D 9 -f console.log -
see if there are any clues in console.log
>
> 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@lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users

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@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 

Thread Tools




All times are GMT. The time now is 02:48 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org