date:20170822

[389-users] Re: Console hang after 4th server install

2017-08-22 Thread Mark Reynolds



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

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?

Regards,
Mark
>
> -morgan
>
>
>> On Aug 17, 2017, at 3:16 PM, Mark Reynolds  wrote:
>>
>> 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 
  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@lists.fedoraproject.org
>
>
> To unsubscribe send an email to 
>
> 389-users-le...@lists.fedoraproject.org
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: Console hang after 4th server install

2017-08-22 Thread Morgan Jones

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.

-morgan


> On Aug 17, 2017, at 3:16 PM, Mark Reynolds  wrote:
> 
> 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 
>>>  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@lists.fedoraproject.org
 
 
 To unsubscribe send an email to 
 
 389-users-le...@lists.fedoraproject.org
> 
___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Announcing Directory Server 1.3.6.8-1

2017-08-22 Thread Mark Reynolds


389 Directory Server 1.3.6.8

The 389 Directory Server team is proud to announce 389-ds-base
version 1.3.6.8

Fedora packages are available from the Fedora 26.

https://bodhi.fedoraproject.org/updates/FEDORA-2017-c95a212f02

The new packages and versions are:

  * 389-ds-base-1.3.6.8-1 Fedora 26

Source tarballs are available for download at Download
389-ds-base Source



  Highlights in 1.3.6.8

  * Bug fix


  Installation and Upgrade

See Download  for
information about setting up your yum repositories.

To install, use *yum install 389-ds* yum install 389-ds After install
completes, run *setup-ds-admin.pl* if you have 389-admin installed,
otherwise please run *setup-ds.pl* to set up your directory server.

To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run
*setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please
run *setup-ds.pl* to update your directory server/admin
server/console information.

See Install_Guide
 for more
information about the initial installation, setup, and upgrade

See Source 
for information about source tarballs and SCM (git) access.


  Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list:
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org

If you find a bug, or would like to see a new feature, file it in our
Pagure project: https://pagure.io/389-ds-base

  * Bump version to 1.3.6.8
  * Ticket 49356 - mapping tree crash can occur during tot init

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Announcing Directory Server 1.3.7.2-1

2017-08-22 Thread Mark Reynolds

*389 Directory Server **1.3.7.2*

The 389 Directory Server team is proud to announce 389-ds-base
version 1.3.7.2

Fedora packages are available on Fedora 27 and 28(Rawhide).

https://koji.fedoraproject.org/koji/taskinfo?taskID=21401020 - Fedora 28
https://koji.fedoraproject.org/koji/taskinfo?taskID=21401182 - Fedora 27

The new packages and versions are:

  * 389-ds-base-1.3.7.2-1

Source tarballs are available for download at Download
389-ds-base Source



  Highlights in 1.3.7.2

  * Security fix, bug fixes, and enhancements


  Installation and Upgrade

See Download  for
information about setting up your yum repositories.

To install, use *yum install 389-ds* yum install 389-ds After install
completes, run *setup-ds-admin.pl* if you have 389-admin installed,
otherwise please run *setup-ds.pl* to set up your directory server.

To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run
*setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please
run *setup-ds.pl* to update your directory server/admin
server/console information.

See Install_Guide
 for more
information about the initial installation, setup, and upgrade

See Source 
for information about source tarballs and SCM (git) access.


  Feedback

We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list:
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject.org

If you find a bug, or would like to see a new feature, file it in our
Pagure project: https://pagure.io/389-ds-base

  * Bump version to 1.3.7.2
  * Ticket 49038 - Fix regression from legacy code cleanup
  * Ticket 49295 - Fix CI tests
  * Ticket 48067 - Add bugzilla tests for ds_logs
  * Ticket 49356 - mapping tree crash can occur during tot init
  * Ticket 49275 - fix compiler warns for gcc 7
  * Ticket 49248 - Add a docstring to account locking test case
  * Ticket 49445 - remove dead code
  * Ticket 48081 - Add regression tests for pwpolicy
  * Ticket 48056 - Add docstrings to basic test suite
  * Ticket 49349 - global name ‘imap’ is not defined
  * Ticket 83 - lib389 - Fix tests and create_test.py
  * Ticket 48185 - Remove referint-logchanges attr from referint’s config
  * Ticket 48081 - Add regression tests for pwpolicy
  * Ticket 83 - lib389 - Replace topology agmt objects
  * Ticket 49331 - change autoscaling defaults
  * Ticket 49330 - Improve ndn cache performance.
  * Ticket 49347 - reproducable build numbers
  * Ticket 39344 - changelog ldif import fails
  * Ticket 49337 - Add regression tests for import tests
  * Ticket 49309 - syntax checking on referint’s delay attr
  * Ticket 49336 - SECURITY: Locked account provides different return code
  * Ticket 49332 - Event queue is not working
  * Ticket 49313 - Change the retrochangelog default cache size
  * Ticket 49329 - Descriptive error msg for USN cleanup task
  * Ticket 49328 - Cleanup source code
  * Ticket 49299 - Add normalized dn cache stats to dbmon.sh
  * Ticket 49290 - improve idl handling in complex searches
  * Ticket 49328 - Update clang-format config file
  * Ticket 49091 - remove usage of changelog semaphore
  * Ticket 49275 - shadow warnings for gcc7 - pass 1
  * Ticket 49316 - fix missing not condition in clock cleanu
  * Ticket 49038 - Remove legacy replication
  * Ticket 49287 - v3 extend csnpl handling to multiple backends
  * Ticket 49310 - remove sds logging in debug builds
  * Ticket 49031 - Improve memberof with a cache of group parents
  * Ticket 49316 - Fix clock unsafety in DS
  * Ticket 48210 - Add IP addr and connid to monitor output
  * Ticket 49295 - Fix CI tests and compiler warnings
  * Ticket 49295 - Fix CI tests
  * Ticket 49305 - Improve atomic behaviours in 389-ds
  * Ticket 49298 - fix missing header
  * Ticket 49314 - Add untracked files to the .gitignore
  * Ticket 49303 - Fix error in CI test
  * Ticket 49302 - fix dirsrv importst due to lib389 change
  * Ticket 49303 - Add option to disable TLS client-initiated renegotiation
  * Ticket 49298 - force sync() on shutdown
  * Ticket 49306 - make -f rpm.mk rpms produces build without
tcmalloc enabled
  * Ticket 49297 - improve search perf in bpt by removing a deref
  * Ticket 49284 - resolve crash in memberof when deleting attrs
  * Ticket 49290 - unindexed range searches don’t provide notes=U
  * Ticket 49301 - Add one logpipe test case


___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org

[389-users] Re: Console hang after 4th server install

[389-users] Re: Console hang after 4th server install

[389-users] Announcing Directory Server 1.3.6.8-1

[389-users] Announcing Directory Server 1.3.7.2-1

4 matches

Site Navigation

Mail list logo

Footer information