ubuntu-389-directory-server team mailing list archive
-
ubuntu-389-directory-server team
-
Mailing list archive
-
Message #00158
[Bug 1097523] Re: Calling restart on init script does not restart daemon
Hello Tom, or anyone else affected,
Accepted 389-ds-base into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/389-ds-
base/1.2.10.4-0ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: 389-ds-base (Ubuntu Precise)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/1097523
Title:
Calling restart on init script does not restart daemon
Status in “389-ds-base” package in Ubuntu:
Fix Released
Status in “389-ds-base” source package in Precise:
Fix Committed
Bug description:
[Impact]
restarting the daemon instance doesn't always work properly
[Test Case]
configure an instance, try restarting it
[Regression Potential]
low, it's verified to work on a later release
--
When calling /etc/init.d/dirsrv restart the daemon doesn't fully
shutdown after stop before start is called. The effect of this is that
the service will stop if started and vice-versa. Adding a sleep
between stop and start seems to fix this issue, though is probably not
the right answer. The init script in RHEL/CentOS appears to work
correctly, and is attached in case it is helpful.
root@server:~# /etc/init.d/dirsrv restart
* Starting 389 DS instance core1: ... [ OK ]
root@server:~# [08/Jan/2013:19:56:24 +0000] - 389-Directory/1.2.11.7 B2013.04.31 starting up
[08/Jan/2013:19:56:24 +0000] - slapd started. Listening on All Interfaces port 389 for LDAP requests
root@server:~# /etc/init.d/dirsrv restart
* Shutting down 389 DS instance core1: ... [ OK ]
* Starting 389 DS instance core1: ... [ OK ]
root@server:~# [08/Jan/2013:19:56:28 +0000] createprlistensockets - PR_Bind() on All Interfaces port 389 failed: Netscape Portable Runtime error -5982 (Local Network address is in use.)
[08/Jan/2013:19:56:27 +0000] - slapd shutting down - signaling operation threads
[08/Jan/2013:19:56:27 +0000] - slapd shutting down - waiting for 2 threads to terminate
[08/Jan/2013:19:56:27 +0000] - slapd shutting down - closing down internal subsystems and plugins
[08/Jan/2013:19:56:27 +0000] - Waiting for 4 database threads to stop
[08/Jan/2013:19:56:27 +0000] - All database threads now stopped
[08/Jan/2013:19:56:27 +0000] - slapd stopped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/1097523/+subscriptions
References