On 08/23/2017 11:18 AM, Morgan Jones wrote: >> On Aug 22, 2017, at 2:15 PM, Mark Reynolds <mareynol@xxxxxxxxxx> wrote: >> >> >> >> On 08/22/2017 01:36 PM, Morgan Jones wrote: >>> Thanks—is there a trick to turning on admin-serv logging? I don’t have one and at least on first blush don’t see a means of enabling it. >> The Admin Server (389-admin/389-adminutil) logs by default. Are you >> saying there is no /var/log/dirsrv/admin-serv/ directory? Or that the >> directory is empty > Oh, sorry, I do have an access and error log in /var/log/dirsrv/admin-serv. The logs are sparse between startup and hang: > ==> error <== > [Wed Aug 23 11:15:13.941399 2017] [:notice] [pid 15780:tid 139865400174336] [client 127.0.0.1:43150] admserv_check_authz(): passing [/admin-serv/authenticate] to the userauth handler > > ==> access <== > 127.0.0.1 - cn=directory manager [23/Aug/2017:11:15:13 -0400] "GET /admin-serv/authenticate HTTP/1.0" 200 329 > >> Also, just to clarify, you are doing all of this on same system >> correct? And when you create 4 server instances the console starts to >> hang? Or have you registered 4 remote servers instead of creating local >> instances? > I’m registering remote servers. We have a total of 5. It starts to hang after installing the 4th. Do you see a drop off in performance as you get close to the 4th? Or everything is fine, then you add more server and its grinds to halt? If you register the servers in a different order, is it still the 4th that causes issues? Or is it one particular server? Mark > > -morgan > _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
