mysqldump causes OOMKIlled error exit code 137

Solution Verified - Updated -

Issue

  • When running RHSSO backup script and 3scale backup script, RH-SSO MySQL database dump script failed to complete.
  • Noticed the error command terminated with exit code 137 when the mysqldump command is executed.
  • Following events were noticed in the sso-mysql pod
Events:
  FirstSeen     LastSeen        Count   From                            SubObjectPath                   Type            Reason          Message
  ---------     --------        -----   ----                            -------------                   --------        ------          -------
  48m           48m             1       kubelet, nodeX.example.com      spec.containers{sso-mysql}      Warning         Unhealthy       Readiness probe errored: rpc error: code = Unknown desc = container not running
  48m           48m             1       kubelet, nodeX.example.com      spec.containers{sso-mysql}      Warning         Unhealthy       Readiness probe failed:
  48m           48m             1       kubelet, nodeX.example.com      spec.containers{sso-mysql}      Normal          Killing         Killing container with id docker://sso-mysql:Container failed liveness probe.. Container will be killed and recreated.

Environment

  • Red Hat 3scale API Management (2.6.0 On-Premises)
  • Red Hat Single Sign-On (7.3)

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