Sorry these logs look "normal", that message that
keeps repeating is expected when the console is idle (it's waiting
for you to do something).
Perhaps there is something in the admin logs:
/var/log/dirsrv/admin-serv
Regards,
Mark
On 08/16/2017 03:39 PM, Morgan Jones
wrote:
Hello Mark,
See attached, "AbstractServerObject.StatusThread: waiting for change listeners to register” repeats presumably forever after it hangs.
Thanks,
-morgan
On Aug 16, 2017, at 3:23 PM, Mark Reynolds <mareynol@xxxxxxxxxx> wrote:
Hi Morgan,
We need more info. Try running the console in debug mode:
389-console -D 9
Also look at the configuration DS access log
Mark
On 08/16/2017 02:57 PM, Morgan Jones wrote:
I’m in the process of installing 389 in CentOS 7 from epel (versions below) and find that the console becomes unresponsive after I install the 4th server. I can open the console and expand a few servers but within 30 seconds it consistently hangs. I am storing configuration data in one server.
Has anyone else seen this or do you have any insight?
Thanks,
-morgan
[morgan@devldap03 ~]$ rpm -qa|grep 389
pcp-pmda-ds389log-3.11.3-4.el7.x86_64
389-admin-console-1.1.12-1.el7.noarch
389-dsgw-1.1.11-5.el7.x86_64
389-adminutil-1.1.21-2.el7.x86_64
389-admin-1.1.46-1.el7.x86_64
389-ds-console-doc-1.2.16-1.el7.noarch
389-ds-1.2.2-6.el7.noarch
389-ds-base-libs-1.3.5.10-21.el7_3.x86_64
389-ds-base-1.3.5.10-21.el7_3.x86_64
389-admin-console-doc-1.1.12-1.el7.noarch
389-console-1.1.18-1.el7.noarch
pcp-pmda-ds389-3.11.3-4.el7.x86_64
389-ds-console-1.2.16-1.el7.noarch
[morgan@devldap03 ~]$
_______________________________________________
389-users mailing list --
389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to
389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
|
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
