Knowledge Document: Logrotate crashes daily with Open Enterprise Server Cluster Service

1 Likes

Environment
Open Enterprise Server (OES) 2018 SP2
Open Enterprise Server (OES) 2018 SP3

Situation
The message log shows something like:
cluster-server systemd[1]: Starting Rotate log files...
cluster-server logrotate[3636]: error: stat of /var/opt/novell/log/ncs/ncs-dns.monitor.out failed: : No such file or directory
cluster-server logrotate[3636]: error: stat of /var/opt/novell/log/ncs/ncs-ftp.monitor.out failed: : No such file or directory
cluster-server logrotate[3636]: error: stat of /var/opt/novell/log/ncs/ncs-ndsd-care.monitor.out : No such file or directory
cluster-server systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE
cluster-server systemd[1]: Failed to start Rotate log files.
cluster-server systemd[1]: logrotate.service: Unit entered failed state.
cluster-server systemd[1]: logrotate.service: Failed with result 'exit-code'.

Cause
The root cause of logrotates' crash is, that there are no more logs available to rotate, if "novell-ncs-monitor-log" ran once. A second run of logroate leads to the error

Resolution
Add a line missingok to the end of configuration parameters within /etc/logrotate.d/novell-ncs-monitor-log:
{
 daily
 rotate365 
....
}
similar to this
{
  daily
  rotate 365
  ....
  missingok
}

Access support article here

Labels:

Knowledge Docs
Comment List
Related
Recommended