New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DS not shutting down when disk monitoring threshold is reached to half #722
Comments
Comment from nkinder (@nkinder) at 2013-06-06 00:23:43 Actually there might be something else going wrong. That error message should not be repeating every 10 seconds, because it supposed to turn off verbose logging. If its turned off, its not suppose to keep logging that same message. |
Comment from mreynolds (@mreynolds389) at 2013-06-07 01:40:58 attachment |
Comment from mreynolds (@mreynolds389) at 2013-06-07 20:09:34 git merge ticket47385 git push origin master 383cc74..fcd2ceb master -> master commit fcd2ceb 1.3.1
1.3.0
commit f315d67 1.2.11 79739bd..70c5bc1 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 70c5bc1 |
Comment from mreynolds (@mreynolds389) at 2013-07-10 21:10:21 Reopening, if a large chunk of disk space is consumed that would put the server below the halfway mark of the threshold at one shot, the server will not shutdown as expected. |
Comment from mreynolds (@mreynolds389) at 2013-07-10 21:53:42 There was an integer overflow for the halfway mark |
Comment from mreynolds (@mreynolds389) at 2013-07-10 22:22:29 git merge ticket47385 git push origin master commit 8486837 1.3.1 2e1d633..ad8f908 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 1.3.0 1987727..49ed254 389-ds-base-1.3.0 -> 389-ds-base-1.3.0 1.2.11 |
Comment from mreynolds (@mreynolds389) at 2017-02-11 23:03:27 Metadata Update from @mreynolds389:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47385
DS is not shutting down when disk monitoring threshold is reached to half.
Steps to Reproduce:
Configure dse.ldif for disk monitoring with higher threashold
nsslapd-disk-monitoring-threshold: 5242880
nsslapd-disk-monitoring: on
configure nsslapd-disk-monitoring-logging-critical so that DS shuts down
instead of stop logging audit & access logs
nsslapd-disk-monitoring-logging-critical: on
Actual results:
Keeps putting the same message every 10 seconds
[30/May/2013:14:24:58 +0200] - Disk space is low on disk (/var/log), remaining
space: 36212 Kb, setting error loglevel to zero.
[30/May/2013:14:25:08 +0200] - Disk space is low on disk (/var/log), remaining
space: 36212 Kb, setting error loglevel to zero.
[30/May/2013:14:25:18 +0200] - Disk space is low on disk (/var/log), remaining
space: 36212 Kb, setting error loglevel to zero.
[30/May/2013:14:25:28 +0200] - Disk space is low on disk (/var/log), remaining
space: 36212 Kb, setting error loglevel to zero
Expected results:
[28/May/2013:18:48:10 -0400] - Disk space is too low on disk (/var), remaining
space: 2920 Kb, disabling access and audit logging.
[28/May/2013:19:00:01 -0400] - Disk space is too low on disk (/var), remaining
space: 2968 Kb, deleting rotated logs.
[28/May/2013:19:00:11 -0400] - Disk space on (/var) is too far below the
threshold(20971520 bytes). Waiting 1 minutes for disk space to be cleaned up
before shutting slapd down...
[28/May/2013:19:01:11 -0400] - Disk space is still too low (2960 Kb).
Signaling slapd for shutdown...
[28/May/2013:19:01:11 -0400] - slapd shutting down - signaling operation
threads
[28/May/2013:19:01:11 -0400] - slapd shutting down - closing down internal
subsystems and plugins
[28/May/2013:19:01:11 -0400] - Waiting for 4 database threads to stop
[28/May/2013:19:01:12 -0400] - All database threads now stopped
[28/May/2013:19:01:12 -0400] - slapd stopped.
Additional info:
It shut down properly when nsslapd-disk-monitoring-threshold is configured as
default 2 mb.
It would be nice if besides ns-slapd exit also the lockfile is removed (what
happens when you do dirsrv stop)
The text was updated successfully, but these errors were encountered: