Chapter 11. Maintaining Satellite Server This chapter provides information on how to maintain a Satellite Server, including information on how to work with audit records, how to clean unused tasks, and how to recover Pulp from a full disk. 11.1. Deleting Audit Records Audit records are created automatically in Satellite. You can use the foreman-rake audits:expire command to remove audits at any time. You can also use a cron job to schedule audit record deletions at the set interval that you want. By default, using the foreman-rake audits:expire command removes audit records that are older than 90 days. You can specify the number of days to keep the audit records by adding the days option and add the number of days. For example, if you want to delete audit records that are older than seven days, enter the following command: 11.2. Anonymizing Audit Records You can use the foreman-rake audits:anonymize command to remove any user account or IP information while maintaining the audit records in the database. You can also use a cron job to schedule anonymizing the audit records at the set interval that you want. By default, using the foreman-rake audits:anonymize command anonymizes audit records that are older than 90 days. You can specify the number of days to keep the audit records by adding the days option and add the number of days. For example, if you want to anonymize audit records that are older than seven days, enter the following command: 11.3. Deleting Report Records Report records are created automatically in Satellite. You can use the foreman-rake reports:expire command to remove reports at any time. You can also use a cron job to schedule report record deletions at the set interval that you want. By default, using the foreman-rake reports:expire command removes report records that are older than 90 days. You can specify the number of days to keep the report records by adding the days option and add the number of days. For example, if you want to delete report records that are older than seven days, enter the following command: 11.4. Configuring the Cleaning Unused Tasks Feature Satellite performs regular cleaning to reduce disc space in the database and limit the rate of disk growth. As a result, Satellite backup completes faster and overall performance is higher. By default, Satellite executes a cron job that cleans tasks every day at 19:45. Satellite removes the following tasks during the cleaning: Tasks that have run successfully and are older than thirty days All tasks that are older than a year You can configure the cleaning unused tasks feature using these options: To configure the time at which Satellite runs the cron job, set the --foreman-plugin-tasks-cron-line parameter to the time you want in cron format. For example, to schedule the cron job to run every day at 15:00, enter the following command: To configure the period after which Satellite deletes the tasks, edit the :rules: section in the /etc/foreman/plugins/foreman-tasks.yaml file. To disable regular task cleanup on Satellite, enter the following command: To reenable regular task cleanup on Satellite, enter the following command: 11.5. Deleting Task Records Task records are created automatically in Satellite. You can use the foreman-rake foreman_tasks:cleanup command to remove tasks at any time. You can also use a cron job to schedule Task record deletions at the set interval that you want. For example, if you want to delete task records from successful repository synchronizations, enter the following command: 11.6. Deleting a Task by ID You can delete tasks by ID, for example if you have submitted confidential data by mistake. Procedure Connect to your Satellite Server using SSH: Optional: View the task: Delete the task: Optional: Ensure the task has been removed from Satellite Server: Note that because the task is deleted, this command returns a non-zero exit code. 11.7. Recovering from a Full Disk The following procedure describes how to resolve the situation when a logical volume (LV) with the Pulp database on it has no free space. Procedure Let running Pulp tasks finish but do not trigger any new ones as they can fail due to the full disk. Ensure that the LV with the /var/lib/pulp directory on it has sufficient free space. Here are some ways to achieve that: Remove orphaned content: This is run weekly so it will not free much space. Change the download policy from Immediate to On Demand for as many repositories as possible and remove already downloaded packages. See the Red Hat Knowledgebase solution How to change syncing policy for Repositories on Satellite from "Immediate" to "On-Demand" on the Red Hat Customer Portal for instructions. Grow the file system on the LV with the /var/lib/pulp directory on it. For more information, see Growing a File System on a Logical Volume in the Red Hat Enterprise Linux 7 Logical Volume Manager Administration Guide . Note If you use an untypical file system (other than for example ext3, ext4, or xfs), you might need to unmount the file system so that it is not in use. In that case, complete the following steps: Stop Satellite services: Grow the file system on the LV. Start Satellite services: If some Pulp tasks failed due to the full disk, run them again. 11.8. Managing Packages on the Base Operating System of Satellite Server or Capsule Server To install and update packages on the Satellite Server or Capsule Server base operating system, you must enter the satellite-maintain packages command. Satellite prevents users from installing and updating packages with yum because yum might also update the packages related to Satellite Server or Capsule Server and result in system inconsistency. Important The satellite-maintain packages command restarts some services on the operating system where you run it because it runs the satellite-installer command after installing packages. Procedure To install packages on Satellite Server or Capsule Server, enter the following command: To update specific packages on Satellite Server or Capsule Server, enter the following command: To update all packages on Satellite Server or Capsule Server, enter the following command: Using yum to Check for Package Updates If you want to check for updates using yum , enter the command to install and update packages manually and then you can use yum to check for updates: Updating packages individually can lead to package inconsistencies in Satellite Server or Capsule Server. For more information about updating packages in Satellite Server, see Updating Satellite Server . Enabling yum for Satellite Server or Capsule Server Package Management If you want to install and update packages on your system using yum directly and control the stability of the system yourself, enter the following command: Restoring Package Management to the Default Settings If you want to restore the default settings and enable Satellite Server or Capsule Server to prevent users from installing and updating packages with yum and ensure the stability of the system, enter the following command: 11.9. Reclaiming PostgreSQL Space The PostgreSQL database can use a large amount of disk space especially in heavily loaded deployments. Use this procedure to reclaim some of this disk space on Satellite. Procedure Stop all services, except for the postgresql service: Switch to the postgres user and reclaim space on the database: Start the other services when the vacuum completes: 11.10. Reclaiming Space From On Demand Repositories If you set the download policy to on demand, Satellite downloads packages only when the clients request them. You can clean up these packages to reclaim space. For a single repository In the Satellite web UI, navigate to Content > Products . Select a product. On the Repositories tab, click the repository name. From the Select Actions list, select Reclaim Space . For multiple repositories In the Satellite web UI, navigate to Content > Products . Select the product name. On the Repositories tab, select the checkbox of the repositories. Click Reclaim Space at the top right corner. For Capsules In the Satellite web UI, navigate to Infrastructure > Capsules . Select the Capsule Server. Click Reclaim space .

Commands:
foreman-rake audits:expire days=7
foreman-rake audits:anonymize days=7
foreman-rake reports:expire days=7
satellite-installer --foreman-plugin-tasks-cron-line "00 15 * * *"
satellite-installer --foreman-plugin-tasks-automatic-cleanup false
satellite-installer --foreman-plugin-tasks-automatic-cleanup true
foreman-rake foreman_tasks:cleanup TASK_SEARCH='label = Actions::Katello::Repository::Sync' STATES='stopped'
ssh root@satellite.example.com
hammer task info --id My_Task_ID
foreman-rake foreman_tasks:cleanup TASK_SEARCH="id= My_Task_ID "
hammer task info --id My_Task_ID
foreman-rake katello:delete_orphaned_content RAILS_ENV=production
satellite-maintain service stop
satellite-maintain service start
satellite-maintain packages install package_1 package_2
satellite-maintain packages update package_1 package_2
satellite-maintain packages update
satellite-maintain packages unlock yum check update satellite-maintain packages lock
satellite-maintain packages unlock
satellite-maintain packages lock
satellite-maintain service stop --exclude postgresql
su - postgres -c 'vacuumdb --full --all'
satellite-maintain service start