Recent IMAP Activity Is Still Being Logged Into A Previous Log File
(Doc ID 2203522.1)
Last updated on MARCH 14, 2019
Applies to:Oracle Communications Messaging Server - Version 7.0.5 and later
Information in this document applies to any platform.
Noticing a a bug in the new log roll over manager where recent IMAP activity is still being logged into a previous log file.
$ tail imap
[11/Aug/2016:07:40:00 -0700] mailhostA rollovermanager: General Information: Log created (1470926400)
[11/Aug/2016:07:40:00 -0700] mailhostA rollovermanager: General Notice: Log rotation performed. -----> rollovermanager <-----
NOTE: tail only showed two lines. So that is the whole file.
What should have been the previous log file is still being updated. You can see that from the above time stamps.
Also note which processes have which files open:
mailhostA:/gcs/app/mail/msg/log$ fuser imap
mailhostA:/gcs/app/mail/msg/log$ ps -ef|grep 32378
msadmin 32378 24780 0 Aug 08 ? 0:01 /opt/sun/comms/messaging64/lib/msrollovermgr
msadmin 21117 20849 0 09:16:26 pts/1 0:00 grep 32378
mailhostA:/gcs/app/mail/msg/log$ fuser imap.38.1470900991
imap.38.1470900991: 32348o 32347o 32346o 32345o 32344o 32343o 32342o 32341o 32340o 32339o 32338o 32337o 32336o 32335o 32334o 32333o 32332o 32331o 32330o 32329o
The new log is only open by msrollovermgr.
The previous log is still open by all the imapd processes.
Upgraded from MS 7u5 to MS 18.104.22.168
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