condor_q and condor_status are slow and failing to respond in MRG 2.0

Solution Verified - Updated -

Issue

  • We had a brief episode of condor commands not responding or being extremely slow to respond resulting in a large number of errors refering to closed sockets or UDP messages.

Environment

  • Red Hat Enterprise MRG Grid (MRG-G) 2.0 - 2.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content