Are you planning to upgrade to a newer CA Performance Management release? It would come with newer versions of Vertica if you go to 2.5 or the pending 2.6 release due out in the next couple of weeks.
I found this info in an internal Wiki site that might apply, though it was written back in 2012 so is a bit old. At least some of the things it recommends checking might lead to finding something out of place which could be causing this.
Note: There is an issue with the log rotate tool that vertica provides causes the configuration file to have incorrect entries that will cause log not to be rotated. This will be resolved in a future release from vertica 5.0.4
During the installation, a file named vertica is created in the /etc/logrotate.d/ directory
1. Confirm that there is a file named vertica in the /etc/logrotate.d/directory
The file /etc/logrotate.d/vertica should contain the following line:
At database creation, a file is created in the /opt/vertica/config/logrotate/ with the same name as the database.2. Confirm that there is a file with the same name as the database in the /opt/vertica/config/logrotate/ directory.
3. Run logrotate with -dv to check for any errors in the files.
sudo logrotate -dv /etc/logrotate.d/vertica
To capture the output:
sudo logrotate -dv /etc/logrotate.d/vertica 2> /tmp/logrotate.out
Here is an example of the output:
reading config file /etc/logrotate.d/vertica
reading config file testdb
reading config info for /data/dbs/testdb/v_testdb_node0001_catalog/vertica.log
reading config info for /data/dbs/testdb/dbLog
rotating pattern: /data/dbs/testdb/v_testdb_node0001_catalog/vertica.log weekly (52 rotations)
empty log files are rotated, only log files >= 10485760 bytes are rotated, old logs are removed
considering log /data/dbs/testdb/v_testdb_node0001_catalog/vertica.log
log does not need rotating
not running postrotate script, since no logs were rotated
4. To force the logs to rotate you can issue the logrotate with the -f option. If the vertica.log rotates, this confirm that the logrotate is set up correctly by Vertica.
sudo logrotate -vf /etc/logrotate.d/vertica
5. Other things to check if the logrotate is still not working.As the root user:
Confirm that logrotate is being run daily, should be in the /etc/cron.daily directory: ls -l /etc/cron.daily
Check to make sure the /etc/crontab contains a reference to cron.daily
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
Check the log file /var/log/cron for any errors
6. Once log rotation is working properly, you should begin to see gzipped files in the Vertica catalog directory. For example, assuming the following is the customer's catalog directory:
You will start to see gzipped files with names like the following once rotation occurs:
and so forth
Let me know if that reveals anything unusual that might be causing this problem.