Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1170707 - cos_cache_build_definition_list does not stop during server shutdown
cos_cache_build_definition_list does not stop during server shutdown
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.0
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Noriko Hosoi
Viktor Ashirov
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-12-04 11:23 EST by mreynolds
Modified: 2015-03-05 04:39 EST (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-1.3.3.1-10.el7
Doc Type: Bug Fix
Doc Text:
Cause: The COS cache rebuild process does not check for a server shutdown. Consequence: The server can take a very long time to shutdown depending on how many COS templates/definitions there are. Fix: Check for shutdown and abort the COS cache rebuild. Result: The server shutsdown in a reasonable amount of time even if the cache is being rebuilt.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 04:39:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0416 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 09:26:33 EST

  None (edit)
Description mreynolds 2014-12-04 11:23:04 EST
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47967

If there are many cos definitions, and entries that use cos, the definition building can take a long time (over 30 minutes).  Trying to stop the server does not break out of this definition building loop, and you have to kill the server.
Comment 1 mreynolds 2014-12-04 16:08:59 EST
Fixed upstream.

Verification is a little tricky, this was originally reproduced with customer specific data that had over 4500 COS templates.

[1]  Setup DS
[2]  Add 4500 COS templates
[3]  Modify 1 template
[4]  Stop the server.

The server should stop with 30 seconds
Comment 3 Amita Sharma 2014-12-24 05:23:22 EST
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample45000,ou=People,dc=example,dc=com
.
.
.
.
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample2729,ou=People,dc=example,dc=com
.
.
.
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample6,ou=People,dc=example,dc=com
.
.
.
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample3,ou=People,dc=example,dc=com

/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample2,ou=People,dc=example,dc=com
/usr/lib64/mozldap/ldapmodify -a -p 389 -h localhost -D cn=directory manager -w Secret123 -f /export/cos1.ldif
adding new entry cn=cosTemplateExample1,ou=People,dc=example,dc=com


[root@dhcp201-126 export]# ldapmodify -D "cn=directory manager" -w Secret123 -p 389 -h localhost << EOF
> dn: cn=cosTemplateExample1,ou=People,dc=example,dc=com
> changetype: modify
> replace: postalCode
> postalCode: 90867
> EOF
modifying entry "cn=cosTemplateExample1,ou=People,dc=example,dc=com"

[root@dhcp201-126 export]# date
Wed Dec 24 15:52:49 IST 2014
[root@dhcp201-126 export]# /usr/lib64/dirsrv/slapd-dhcp201-126/start-slapd 
[root@dhcp201-126 export]# date
Wed Dec 24 15:53:00 IST 2014
[root@dhcp201-126 export]# /usr/lib64/dirsrv/slapd-dhcp201-126/stop-slapd 
[root@dhcp201-126 export]# date
Wed Dec 24 15:53:07 IST 2014

Hence VERIFIED.
Comment 5 errata-xmlrpc 2015-03-05 04:39:50 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html

Note You need to log in before you can comment on or make changes to this bug.