NetWorker 19.10 and 19.11: Growing file /tmp/cryptolib.log

Each time we start NetWorker components (processes), it loads and initializes the OpenSSL library and is adding a message into the log file.
The file /tmp/cryptolib.log is increasing over time.

nwserver:/tmp # ls -l /tmp/cryptolib.log
-rw-r--r-- 1 root root 3819297 Aug  9 13:33 /tmp/cryptolib.log 
nwserver:/tmp #

This issue is related to the OpenSSL library used in NetWorker 19.10 and 19.11. It is not allowing the FIPS mode and reporting it to the file.

Workaround:

The file can be disregarded. Periodically delete the /tmp/cryptolib.log file to prevent space consumption issues.

Alternatively, you can use logrotate to rotate the log file daily, retain X number of copies, and delete the oldest.

1. Confirm if the logrotate package is installed:

   logrotate --version

   NOTE: logrotate is a Linux operating system package not provided by NetWorker. If logrotate is not installed, see OS vendor-specific documentation for installing the logrotate package.

2. Edit the /etc/logrotate.conf to include specifications for rotating /tmp/cryptolib.log. For example, append the following lines to the end of the file:

   /tmp/cryptolib.log {
           daily
           rotate 7
           compress
           missingok
           create 0644 root root
           su root root
   }

   • daily: rotate the log daily.
   • rotate 7: Keep seven rotated log files before deleting the oldest one. This can be changed depending on the wanted number of copies and available space on the system.
   • compress: compress the rotated log files to save space.
   • missingok: If the log file is missing, move on to the next one without issue.
   • create 0644 root root: Create a new log file with permissions 0644 and ownership root:root after rotation. This matches the default permissions and ownership of the original /tmp/cryptolib.log file.
   • su root root: Switch to user root and group root for creating new log files.

3. Test the logrotate settings:

   sudo logrotate -d /etc/logrotate.conf

Solution:

The problem will be resolved with NetWorker 19.12.