Creation Of Log Rotation For The BRM Webservice.log File Stops Any Logging To That File
(Doc ID 2426190.1)
Last updated on MARCH 12, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The user is trying to configure logrotate for BRM WebService at Linux OS level and trigger it by cron job, a new logrotate configuration file is created in /etc/logrotate.d called webservice.
When creating log rotation for BRM webservice, the log file stops being updated.
Here is the logrotate configuration for BRM webservice;
create 644 processbrmapp processbrmapp
/bin/mv /u01/app/brm/7.5/var/brm/webservice.log.1 /u01/app/brmlog/prod/wb1/soap_endpoint/webservice.log_$day
The file permission is -rw-r--r--
When the file is rotated daily (i.e. set back to zero size), the application stops updating to it, but permissions on the file do not change.
This is causing issues when logging production BRM services.
Is there any kind of daemon reload or -HUP signal required to have logging restored properly for BRM after rotation?
Does BRM, for any reason, require a special configuration in logrotate in order for logging to continue after rotation?
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