Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 7. Troubleshoot issues and find reference information

Find information to diagnose common connection failures and apply specific software fixes to maintain system health and connectivity.

7.1. RHC connection issues
Copy link

You can diagnose and resolve common problems that prevent the rhc client from communicating with the Red Hat Hybrid Cloud Console. For example, you can verify the core client protocol and check the system logs for specific error messages that indicate a connection failure.

7.1.1. rhc client communication (mqtt)
Copy link

MQTT is the communication technology behind the rhc daemon, rhcd. The client establishes a connection to the Red Hat message broker and waits for new messages. When the client receives new messages, it reads them and almost instantaneously converts them into playbook execution. The client always establishes the communication to the message broker. There is no communication initiated from the Red Hat services to your environment.

7.1.2. Review the rhc daemon log (journalctl)
Copy link

If you are experiencing connection issues, you must confirm that the client successfully established and maintained its connection to the message broker. You can troubleshoot your connection issue by reviewing the rhc daemon log by using the journalctl command.

Prerequisites

  • You have root user access to the system or sudo privileges.
  • The rhc daemon (rhcd or yggdrasil) service must be installed and enabled.
  • You have TCP ports and destinations enabled for the rhc daemon (port 443).

Procedure

  1. To consult recent daemon logs, enter the following command in your terminal: 

    # journalctl -u rhcd
    Copy to Clipboard Toggle word wrap

  2. Use -f, --follow, to show only the most recent journal entries, and continuously print new entries as they are appended to the journal: 

    # journalctl -u rhcd -f
    Copy to Clipboard Toggle word wrap

7.2. Real-time scheduling CPU conflict
Copy link

The insights-client executes commands that collect data on your system. It has a configuration restriction that limits its CPU usage to no more than 30%.

You can define this restriction in the configuration file with the following option:

insights-client-boot.service: CPUQuota=30%

This configuration prevents the insights-client from creating a CPU spike on your system. This spike could interfere with other applications running on your system. Specifically, it could prevent applications that depend on real-time scheduling from initiating.

If you need to enable real-time scheduling, you can disable the CPU quota restriction. The risk of removing this configuration is minimal. However, it is possible that when the insights-client runs, the CPU usage can become unusually high. If this situation occurs and negatively impacts other services on your system, contact Red Hat support.

Additional resources

7.3. Verify network connectivity of required ports
Copy link

If the RHC daemon log (journalctl) indicates communication failures, it can be a problem of a blocked port. Before contacting support, you must verify that your system can reach all required Red Hat service destinations and TCP ports.

Check Connectivity
Ensure that all required ports are open and destinations are accessible. The system needs access for the Subscription Manager, the insights-client, and the RHC daemon.
Check the list of TCP Ports and Destinations
See Manage system connectivity and networking for the definitive list of TCP Ports and Destinations required for full system functionality.

7.4. Create a diagnostic log for support
Copy link

You can create a diagnostic log to share with the support team.

Prerequisites

  • You have root user access to your system.
  • You have installed the insights-client on your system.

Procedure

  1. Enter the insights-client command with the --support option. 

    [root@rhlightspeed]# insights-client --support
    Copy to Clipboard Toggle word wrap

    The command displays informational messages while creating the support file. 

    Collecting logs...
Red Hat Lightspeed version: insights-core-3.0.121-1
Registration check:
status: True
unreachable: False
. . . .
Copying Red Hat Lightspeed logs to archive...
Support information collected in /var/tmp/H_Y43a/insights-client-logs-20190927144011.tar.gz
    Copy to Clipboard Toggle word wrap

  2. Navigate to the collection directory as shown in the Support information collected in message. 

    [root@rhlightspeed]# cd /var/tmp/H_Y43a
    Copy to Clipboard Toggle word wrap

  3. Unpack the compressed tar.gz file. 

    [root@rhlightspeed]# tar -xzf insights-client-logs-20250912112824.tar.gz
    Copy to Clipboard Toggle word wrap

    Extracting the tar.gz copies the log files into your current directory. You can share the tar.gz file with the support team if requested.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top