Higher than normal disk usage on NetBackup 50xx appliances running software version 1.4.1.1 and PureDisk servers running 6.6.3a

Article:TECH182830  |  Created: 2012-03-01  |  Updated: 2012-04-24  |  Article URL http://www.symantec.com/docs/TECH182830
Article Type
Technical Solution


Issue



Disk usage within the /Storage filesystem on the NetBackup 50xx appliances running software version 1.4.1.1 and also PureDisk servers running 6.6.3a will be higher than normal, due to a syntax error in the appliance-specific logrotate configuration files.

The 'logrotate' process is run by the 'cron' scheduler process on the appliance/server on a daily basis, but because the logrotate process exits when it encounters an error, it will not run in full ; thus uncompressed logs and history files under /Storage will consume more space.


Error



No errors will be visible from the appliance web GUI or the CLISH interface, however if '/etc/cron.daily/logrotate' is run from a root prompt, errors can be seen there if the problem is present.

 

To determine if your appliance or server is affected:

1. Login as the 'root' user directly, or via the CLISH and choose the 'admin'->'su' menu options.

2. Execute the command:    /etc/cron.daily/logrotate

3. A system with the issue present will report an issue (similar to the following but possibly not exactly the same):

nbu5020:/etc/logrotate.d # /etc/cron.daily/logrotate
error: PDDODataRemoval:2 lines must begin with a keyword or a filename (possibly in double quotes)
error: PDDODataRemoval:3 bad rotation count 'daily'
nbu5020:/etc/logrotate.d #

In comparison, a system without the problem will return to a prompt within a short time with no error message:

nbu5020:/etc/logrotate.d # /etc/cron.daily/logrotate
nbu5020:/etc/logrotate.d #

If you are not affected, no further action is required.  However, if your appliance or server is affected, continue to the solution and workaround details below.

 


Cause



The configuration files for logrotate reside in /etc/logrotate.d/.

Some of these files have incorrect formatting (syntax errors), causing the logrotate process to exit when such syntax errors are encountered. As a result, the remainder of the configuration is not parsed, resulting in non-compression/removal of log files (some of which can be quite large). 

An example of one of the problematic configuration files is /etc/logrotate.d/PDDODataRemoval, which has incorrect entries on line 2 and 3.  With the syntax error, this file looks like:

/Storage/log/PDDODataRemoval.log {
    7
    rotate daily
    compress
    missingok
    copytruncate
}

 

However, it should read:

 

/Storage/log/PDDODataRemoval.log {
    daily
    rotate 7

    compress
    missingok
    copytruncate
}
 

Solution



The formal solution will be available in the PureDisk EEB bundle Version 6 and higher for both the PureDisk Appliance version 1.4.1.1 (ET2701800) and classic Puredisk version 6.6.3a (ET2657689). 

A workaround is available:

1. Identify the files responsible  - there are typically three sets of configuration files in /etc/logrotate.d/  that cause the problem:

/etc/logrotate.d/PDDODataRemoval   /etc/logrotate.d/cron.*   /etc/logrotate.d/rep\*

2. Move the above files to /tmp, using the following commands:

mv /etc/logrotate.d/PDDODataRemoval /tmp 
mv /etc/logrotate.d/cron.* /tmp 
mv /etc/logrotate.d/rep\* /tmp 

Replace them with the following:

File: /etc/logrotate.d/cron

contents:

/Storage/log/cron.*.log {
        daily
        rotate 7
        compress
        missingok
        notifempty
        copytruncate
}

File: /etc/logrotate.d/PDDODataRemoval.log

Contents:

/Storage/log/PDDODataRemoval.log {
        daily
        rotate 7
        compress
        missingok
        notifempty
        copytruncate
}

 

File: /etc/logrotate.d/rep\*

Contents:

/Storage/log/rep.log.* {  
        daily
        rotate 7
        compress
        missingok
        notifempty
        copytruncate
}
 

To execute log rotation run the following:

logrotate -fv /etc/logrotate.d  

Note that it might take quite a while for this to complete.

When logrotate is finshed check /Storage/log for an excessive amount of rep.log.* files. The EEB bundle v6 will clean these up properly, but if desired, these can be manually removed. 

If you require assistance with these steps or if they do not solve the problem, contact Symantec Technical Support.

 


Supplemental Materials

SourceETrack
Value2673590


Article URL http://www.symantec.com/docs/TECH182830


Terms of use for this information are found in Legal Notices