Katello 3.17 Documentation

Tracer

Tracer displays a list of services and applications that are outdated and need to be restarted.

Additional documentation around the Tracer appliaction can be found here

Using Tracer

Installing Tracer

With the CLI

Make sure that the “Katello Client Release Package” repository is installed and enabled on the client, then install the katello-host-tools-tracer package:

# yum install katello-host-tools-tracer

Run the katello-tracer-upload command, which will upload the Tracer data to the Katello server:

# katello-tracer-upload

With the UI

Go to “Hosts” - “Content Hosts” in the Katello UI. Click on the host name you will be installing Tracer on, click the button labeled “Enable Traces”:

Install Tracer UI

Clicking “Enable Traces” on the host will take you to the Package Actions page to confirm installing the katello-host-tools-tracer package:

UI Tracer Install Package Perform

Clicking “Perform” will kick off a Remote Execution job to install the katello-host-tools-tracer package:

Install Tracer Job

Viewing traces for a content host in the UI

To verify that Katello is receiving Tracer information from the client, within the Katello UI, go to “Hosts” - “All hosts”, and click on the name of the host that Tracer was installed on.

The host should now have a “Traces” property:

View Host Trace Status

Go to “Hosts” - “Content Hosts” in the Katello UI. Click on the host name, and go to the “Traces” tab to see more details:

Host Trace Details

Viewing traces with the CLI

To list all hosts and see the trace status

# hammer host list --fields id,name,trace status

---|---------------------|----------------
ID | NAME                | TRACE STATUS
---|---------------------|----------------
2  | client1.katello.lan | Reboot required
3  | client2.katello.lan | Reboot required
1  | katello.katello.lan |
---|---------------------|----------------

To look at a host in detail and see the trace status

# hammer host info --id 1

Id:                       1
Name:                     centos7.thinkstation.example.com
Organization:             Default Organization
Location:                 Default Location
Cert name:                centos7.thinkstation.example.com
Managed:                  no
Installed at:
Last report:
Uptime (seconds):         329570
Status:
    Global Status: Error
Network:
    IPv4 address: 192.168.121.249
    MAC:          52:54:00:00:85:7f
Network interfaces:
 1) Id:           1
    Identifier:   eth0
    Type:         interface (primary, provision)
    MAC address:  52:54:00:00:85:7f
    IPv4 address: 192.168.121.249
    FQDN:         centos7.thinkstation.example.com
Operating system:
    Architecture:           x86_64
    Operating System:       CentOS 7
    Build:                  no
    Custom partition table:
Subscription Information:
    UUID:            f3a4de5f-0ff3-40b9-828f-ee1fb3ef6337
    Last Checkin:    2020-05-15 21:29:34 UTC
    Release Version:
    Autoheal:        true
    Registered To:   centos7-katello-devel-stable.example.com
    Registered At:   2020-05-15 21:25:15 UTC
    System Purpose:  
        Service Level:  
        Purpose Usage:  
        Purpose Role:
        Purpose Addons:
Trace Status:             Reboot required

To get a list of traces for a single host

# hammer host traces list --host-id 1

---------|---------------------|-----------------------------------------|------------
TRACE ID | APPLICATION         | HELPER                                  | TYPE
---------|---------------------|-----------------------------------------|------------
     | auditd              | sudo systemctl restart auditd           | daemon
     | bash                | You will have to log out & log in again | session
     | chronyd             | sudo systemctl restart chronyd          | daemon
     | crond               | sudo systemctl restart crond            | daemon
     | dbus                | You will have to reboot your computer   | static
     | getty@tty1          | You will have to log out & log in again | session
     | gssproxy            | sudo systemctl restart gssproxy         | daemon
     | irqbalance          | sudo systemctl restart irqbalance       | daemon
     | kernel              | You will have to reboot your computer   | static
     | lvm2-lvmetad        | sudo systemctl restart lvm2-lvmetad     | daemon
     | NetworkManager      | sudo systemctl restart NetworkManager   | daemon
     | polkit              | sudo systemctl restart polkit           | daemon
     | postfix             | sudo systemctl restart postfix          | daemon
     | rpcbind             | sudo systemctl restart rpcbind          | daemon
     | rsyslog             | sudo systemctl restart rsyslog          | daemon
     | sshd                | sudo systemctl restart sshd             | daemon
     | ssh-vagrant-session | You will have to log out & log in again | session
     | systemd             | You will have to reboot your computer   | static
---------|---------------------|-----------------------------------------|------------

Resolving traces for a single Content Host

Go to “Hosts” - “Content Hosts” in the Katello UI. Click on the host name, and go to the “Traces” tab to see more details:

View Host Traces

Tracer is recommending that rsyslog be restarted. Click the box for rsyslog, then click “Restart Selected”. Katello will kick off a Remote Execution job to restart the rsyslog service.

Single Host Trace Job

Resolving traces on multiple Content Hosts

Visit Content Hosts and select the hosts you would like to remediate traces on:

View Bulk Host Traces

Select the services from the list that you want to remediate and click “Restart Selected”:

Bulk Host Traces Select

You will return to the Content Host page with a notification and a link to view the job invocations that have been kicked off with Remote Execution:

Bulk Hosts Traces Job