Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Directory Server Enterprise Edition - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
On : 18.104.22.168.0 version,
Access logs 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.
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:/export/master1/logs/access.20140310-033621 (1394422581) (0)
LOGINFO:Previous Log File:/export/master1/logs/access.20140309-033601 (1394336161) (0)
LOGINFO:Previous Log File:/export/master1/logs/access.20140303-033601 (1393817761) (294967295)
LOGINFO:Previous Log File:/export/master1/logs/access.20140304-033601 (1393904161) (294967295)
LOGINFO:Previous Log File:/export/master1/logs/access.20140305-033601 (1393990561) (294967295)
LOGINFO:Previous Log File:/export/master1/logs/access.20140306-033601 (1394076961) (294967295)
LOGINFO:Previous Log File:/export/master1/logs/access.20140307-033601 (1394163361) (294967295)
LOGINFO:Previous Log File:/export/master1/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 -la access.20140308-033601
-rw-------+ 1 ldapmgr ldapgrp 0 Mar 8 03:36 access.20140308-033601
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