Router unhealthy and keep restarting

Solution In Progress - Updated -

Issue

  • The router pods under OpenShift was unhealthy and were killed and restarted by liveness probe and readiness probes.

  • It is happening very frequently, every minute, and this is contributing connection delay for application.

11:34:10 AM     router-11-xf85v     Pod     Warning     Unhealthy   Readiness probe failed: Get http://localhost:xxxx/healthz: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
9 times in the last 2 minutes
11:34:10 AM     router-11-xf85v     Pod     Warning     Unhealthy   Liveness probe failed: Get http://localhost:xxxx/healthz: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
2 times in the last minute
  • The Openshift environment is having 30 plus router pods.

Environment

  • Openshift Container Platform
    • v3.2

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.