Chapter 8. Changing the insights-client schedule
You can disable, enable, and modify the schedule that controls when the Red Hat Lightspeed client runs. By default, the Red Hat Lightspeed client runs every 24 hours. The timers in the default schedules vary so that all systems do not run the client at the same time.
8.1. Disabling the Red Hat Lightspeed client schedule Copy linkLink copied to clipboard!
You must disable the client schedule before you can change the default Red Hat Lightspeed client settings and create a new schedule.
The procedure you use to disable the insights-client schedule depends on your Red Hat Enterprise Linux and client versions.
Additional resources
8.1.1. Disabling the client schedule Copy linkLink copied to clipboard!
Prerequisites
- Root-level access to your system
Red Hat Lightspeed client version 3.x and later
-
NOTE: The
--no-scheduleoption is deprecated in Client 3.x and later.
-
NOTE: The
Procedure
Enter the
insights-clientcommand with the--versionoption to verify you have the required client version installed.insights-client --version
[root@rhlightspeed]# insights-client --version Client: 3.0.6-0 Core: 3.0.121-1Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the
insights-clientcommand with the--disable-scheduleoption to disable the client schedule.insights-client --disable-schedule
[root@rhlightspeed]# insights-client --disable-scheduleCopy to Clipboard Copied! Toggle word wrap Toggle overflow
8.2. Enabling the Red Hat Lightspeed client schedule Copy linkLink copied to clipboard!
When you first enable the client schedule, it runs using its default settings. If you make changes to the schedule, those settings take precedence.
When you run insights-client from the command line, Red Hat Lightspeed client runs using the settings you specify for only that session. When the next scheduled run takes place, it uses the default settings.
8.2.1. Enabling the Red Hat Lightspeed client schedule on RHEL 7 or later Copy linkLink copied to clipboard!
You can enable the client schedule so that it runs on its default settings. If you change the default schedule settings, the changed settings take precedence.
Prerequisites
- Root-level access to your system.
- The client schedule is disabled.
- (Optional) You modified the default schedule.
Procedure
To verify the client version, enter the
insights-clientcommand with the--versionoption.insights-client --version
[root@rhlightspeed]# insights-client --version Client: 3.0.6-0 Core: 3.0.121-1Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enter the
insights-clientcommand with the--enable-scheduleoption to enable the client schedule.insights-client --enable-schedule
[root@rhlightspeed]# insights-client --enable-scheduleCopy to Clipboard Copied! Toggle word wrap Toggle overflow
8.3. Modifying the Red Hat Lightspeed client schedule Copy linkLink copied to clipboard!
To change when the Red Hat Lightspeed client runs, modify the schedule. The method that you use depends on the RHEL release and client version that your system is running.
Select the procedure that matches your version of RHEL.
-
For Red Hat Enterprise Linux 7.4 and earlier, use
cronto modify the system schedule. -
For Red Hat Enterprise Linux 7.5 and later, update the
systemdsettings and theinsights-client-timerfile.
8.3.1. Scheduling insights-client using systemd settings Copy linkLink copied to clipboard!
Use this for systems running RHEL 7.5 and later with Client 3.x.
You can change the default schedule for running insights-client by updating the system systemd settings and the insights-client.timer file.
Prerequisites
- Root-level access to your system.
Procedure
To edit the settings in the
insights-client.timerfile, enter thesystemctl editcommand and the file name.systemctl edit insights-client.timer
[root@rhlightspeed]# systemctl edit insights-client.timerCopy to Clipboard Copied! Toggle word wrap Toggle overflow This action opens an empty file with the default system editor, on RHEL 6, 7, and 8. On RHEL 9 and later, running the command opens a file with a template that includes the original
systemdservice file as a reference.Enter different settings to modify the schedule. The values in this example are the default settings for
systemd.[Timer] OnCalendar=daily RandomizedDelaySec=14400
[Timer] OnCalendar=daily RandomizedDelaySec=14400Copy to Clipboard Copied! Toggle word wrap Toggle overflow Enable the
insights-clientschedule.insights-client --enable-schedule
[root@rhlightspeed]# insights-client --enable-scheduleCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Additional resources
-
Review the man pages for
systemctl(1),systemd.timer(5), andsystemd.time(7)to understandsystemd -
What is
cronand how is it used?
8.3.2. Refreshing the package cache for systems managed by Red Hat Satellite Copy linkLink copied to clipboard!
Red Hat Lightspeed now provides the optional --build-packagecache command to provide accurate reporting for applicable updates on Satellite-managed systems. This option rebuilds the yum/dnf package caches for insights-client, and creates a refreshed list of applicable updates for the system.
You can run the command manually to rebuild the package caches immediately, or you can edit the client configuration file (/etc/insights-client/insights-client.conf) to rebuild the package caches automatically each time the system checks in to Red Hat Lightspeed.
Additional resources
-
For more information about how to run the
--build-packagecachecommand, see Managing system content and patch updates on RHEL systems. -
For more information about the
--build-packagecacheoptions, see Red Hat Lightspeed shows incorrect patch reporting for Satellite-managed systems. - For more information about managing errata in Red Hat Satellite, see Managing errata.