To prevent the messages from appearing in the future, you should add the following cron job on each CPM of the chassis to ensure that the database is regularly vacuumed. Edit the
/var/spool/cron/postgres file on the CPM and add the highlighted line with "
vacuumdb -z -a" if it is missing:
0 2 * * 1-6 /usr/bin/vacuumdb -z -d running-config
0 2 * * 0 /usr/bin/vacuumdb -z -a
0 */2 * * * /usr/bin/vacuumdb -z -t webSessionTable -d running-config
0 */2 * * * /usr/bin/vacuumdb -z -t alarmTable -d running-config This is the recommended content of the postgres crontab file and has been included with XOS V9.7.2. The change is referenced in the Release Notes:
ID 102207 The vacuum command now runs on all postgres databases on a daily schedule.
Workaround
To eliminate these messages, you need to manually vacuum the postgres database. Use the following steps:
1. Create a copy of the current running-configuration:
CBS# copy running-config -flat /tmp/backup_xos_config
Save and keep a copy of the configuration external to the chassis.
2. Run the following commands to vacuum the database and to clear the error:
/usr/bin/vacuumdb -z -d running-config_alt -U postgres
/usr/bin/vacuumdb -z -d postgres -U postgres