ODSEE 11g Logs Not Reaching Minimum Disk Free Limit On Linux (Doc ID 1902767.1)

Last updated on SEPTEMBER 16, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version 11.1.1.3.0 to 11.1.1.7.1 [Release 11gR1]
Linux x86-64

Symptoms

On : 11.1.1.7.0 on Linux

ACTUAL BEHAVIOR
---------------
ODSEE 11g Directory Server. Log files are not being allowed to grow to a size large enough to reach the limit specified by nsslapd-accesslog-logminfreediskspace

As an example, you want your access logs to keep growing until there is only 2Gb of disk space left on the filesystem. You may have the following settings (the most important being 'minimum disk free').

# ./dsconf get-log-prop -w password1 -h localhost -p 389 ACCESS
max-age : 1M
max-disk-space-size : unlimited
max-file-count : 1000
max-size : 100M
min-free-disk-space-size : 2G

# grep accesslog /export/servers/test/config/dse.ldif
nsslapd-accesslog-maxlogsize: 100
nsslapd-accesslog-logrotationtime: 1
nsslapd-accesslog-logrotationtimeunit: day
nsslapd-accesslog-maxlogsperdir: 1000
nsslapd-accesslog-logmaxdiskspace: -1
nsslapd-accesslog-logminfreediskspace: 2048

The behaviour however is different to the log settings and can be seen in 3 different ways. Logs are being deleted before they should and we see,

1) The minimum free disk space stays at around 8Gb instead of 2Gb.
2) Disk usage output seems to reach a maximum at 15Gb even though this is set to unlimited.
3) Number of archived logs stays around ~150 even though this is set to 1000.




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms