Virt-who takes a long time to report all host to guest mappings to Red Hat Satellite 6.

Environment

• Red Hat Satellite 6.4

Issue

• Virt-who fails with an exception SSLError: ('The read operation timed out',) while reporting host to guests mappings on Red Hat Satellite WebUI.

    # virt-who -o -d
  
    Host-to-guest mapping to "Example" including 348 hypervisors and 8842 guests
    2019-03-08 13:40:36,471 [virtwho.destination_xxxxxxx ERROR]    MainProcess(9506):Thread-3 @virt.py:run:397 - Thread 'destination_xxxxxxx' fails with  exception:
  SSLError: ('The read operation timed out',)
  

Resolution

• Override and increase the value of server-timeout parameter depending upon the hosts and guest load under the [server] section in /etc/rhsm/rhsm.conf file which is 180 seconds by default.

• NOTE: Make the changes as stated below only on the server where virt-who is configured and restart the virt-who service.

  [server]
  server_timeout = [360]                       <<< 360 seconds
  # systemctl restart virt-who
  

For more KB articles/solutions related to Virt-who and Virtual Datacenter (VDC) Subscriptions Issues, please refer to the Consolidated Troubleshooting Article for Virt-who and Virtual Datacenter (VDC) Subscriptions Issues

Root Cause

• In the etc/rhsm/rhsm.conf file the server_timeout parameter was set to the default value which was too less with respect to the load on Red Hat Satellite.

Diagnostic Steps

• Check the value for timeout parameter in the /usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py file on both Red Satellite server as well as virt-who server.

  #  grep -A2 -B2 -i timeout /usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py
  

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.