My Oracle Support Banner

ODSEE Directory Server Access Logs are not Being Written (Doc ID 1643247.1)

Last updated on NOVEMBER 07, 2019

Applies to:

Oracle Directory Server Enterprise Edition - Version to [Release 11gR1]
Information in this document applies to any platform.


Access logs are not being written to, other logs such as audit and errors log are being successfully written to.

Permissions have been changed from the default 600 to 640.

nsslapd-accesslog-permissions: 640

Other instances on separate hardware are written to with this permission setting. Also, new DS instances created on the same hardware also work fine and are written to with 640 permissions.

Looking in the access.rotationinfo file we can see that access logs were previously being written to, but suddenly stopped and files were zero bytes.


LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140310-033621 (1394422581) (0)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140309-033601 (1394336161) (0)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140303-033601 (1393817761) (294967295)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140304-033601 (1393904161) (294967295)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140305-033601 (1393990561) (294967295)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140306-033601 (1394076961) (294967295)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140307-033601 (1394163361) (294967295)
LOGINFO:Previous Log File:/<OUD_INSTANCE>/logs/access.20140308-033601 (1394249761) (294967295)

However if we look at the file that previously contained data, it is now empty and zero bytes.

% ls -al access
-rw-------+ 1 <USER> <GROUP> 0 Mar 8 03:36 access




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.