This update is for all GroundWork customers running GroundWork Monitor 7.2.1 who want to ensure that all NoMa logfiles are properly rotated and are not subject to infinite growth.
This Technical Bulletin provides a documented and scripted method of applying the log-rotation recommendations in internal ticket GWMON-13520, which covers several NoMa logfiles that were previously overlooked.
The following NoMa-generated logfiles have not historically been under logrotate control:
The noma_downtime.log logfile in particular has been seen to grow huge in production.
To repair, a new /etc/logrotate.d/groundwork-noma-extras config file for logrotate is supplied that handles these files. Other logfiles generated by operation of NoMa were already handled by existing configuration, and are not dealt with by this patch.
- You need to be running GroundWork Monitor Enterprise, any version between 7.1.0 and 7.2.1. Rollup patches do not include this fix.
- This technical bulletin does not depend upon prior technical bulletins
- There is no need to schedule a downtime to apply this technical bulletin, because installing or uninstalling it does not involve restarting parts of GroundWork Monitor.
- As the root user, copy the attached tarball to an empty directory on the GW server already in place.
- Unpack the tarball using the command:
- Change into the directory created by untarring:
- Run the installer script:
The install script will test that you are on a GroundWork system running a version between 7.1.0 and 7.2.1 inclusive, that you have not already installed this patch, and that you want to go ahead.
- Respond to the install-confirmation prompt when it appears.
- A new file will be copied into place. Monitoring in general can continue while this patch is installed.
Once this is installed, the additional NoMa logfiles will eventually be rotated once they exceed a reasonable size.
The administrator might wish to look at the files listed above, a day after this patch is installed. If the initial pass of log rotation caused some of those files to be rotated, and the old copies are huge and no longer needed, manual pruning of those rotated-out copies may be desired, to recover the space. Otherwise, the space will be recovered automatically over the log run, after a sufficient number of additional logfile rotations are triggered by continued growth of the logfiles.
No further administrator action is generally needed.
Reversal of this patch will remove the changes made to the GW server by removing the one added logrotate config file.
- As the root user, navigate to the patch-unpack directory you created when installing the patch. (If that directory no longer exists, first unpack the patch again.)
- Run the uninstall command: