Security Software

I found a really odd behavior on my access log. It rotates and generates the archived log with the date-time name, but then it keeps writing to the 'archived' version instead of to the new access log. See my directory listing below, and the rotation onfo.
The access log rotated on 09/12 at 19:07, and it was neer written to again! While the archived version is being written to as I write this post. I am including the configuration parms at the end of this post.
Has anybody seen this before?
Please help!

Enrique.

-rw-rw-r-- 1 ldpadmd ldpadmd 0 Sep 13 19:07 access
-rw-rw-r-- 1 ldpadmd ldpadmd 37207343 Sep 14 08:55 access.20100912-190712

[ldpadmd@edclldpu101 logs]$ cat access.rotationinfo
LOGINFO:Log file created at: 13/Sep/2010:19:07:42 (1284419262)
LOGINFO:Previous Log File:/unta/ldp/logs/pmi/userua/logs/access.20100912-190712 (1284332832) (34225)
LOGINFO:Previous Log File:/unta/ldp/logs/pmi/userua/logs/access.20100911-190642 (1284246402) (0)
LOGINFO:Previous Log File:/unta/ldp/logs/pmi/userua/logs/access.20100910-190612 (1284159972) (0)
LOGINFO:Previous Log File:/unta/ldp/logs/pmi/userua/logs/access.20100909-190542 (1284073542) (86336)

From dse.ldif:

nsslapd-accesslog-logging-enabled: on
nsslapd-accesslog-logrotationtime: 1
nsslapd-accesslog-logrotationtimeunit: day
nsslapd-accesslog-maxlogsperdir: 5
nsslapd-accesslog-permissions: 664
nsslapd-accesslog-logmaxdiskspace: 1024
nsslapd-accesslog: /unta/ldp/logs/pmi/userua/logs/access
nsslapd-accesslog-logexpirationtimeunit: week
nsslapd-accesslog-maxlogsize: 100
nsslapd-accesslog-logexpirationtime: 2
nsslapd-accesslog-logminfreediskspace: 10
nsslapd-accesslog-level: 256