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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.