---
title: "Discussion on \"CrashLoopBackOff: reading exit codes and debugging restart loops\" | Hashnode"
description: "Discussion on \"CrashLoopBackOff: reading exit codes and debugging restart loops\". CrashLoopBackOff is a restart backoff, not the error. Read exit codes 137, 143 and 1, check probes and startup order, and find the cause in order."
url: "https://hashnode.com/posts/crashloopbackoff-reading-exit-codes-and-debugging-restart-loops/6afbc2e8342318b02989ee50"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [CrashLoopBackOff: reading exit codes and debugging restart loops](https://ryuslog.hashnode.dev/crashloopbackoff-reading-exit-codes-and-debugging-restart-loops?utm_source=hashnode&utm_medium=feed)

CrashLoopBackOff is a restart backoff, not the error. Read exit codes 137, 143 and 1, check probes and startup order, and find the cause in order.

2d ago · 2 min read · ryuslog.hashnode.dev  
Read the article

-   [#kubernetes](https://hashnode.com/tag/kubernetes)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[R (RYUSLOG DEV)](https://hashnode.com/@rshday)

@rshday

  
[View profile](https://hashnode.com/@rshday)

Practical software engineering and syntax guides, plus browser-based developer tools.

I write practical software engineering and language syntax guides at RYUSLOG DEV (https://www.ryuslog.com) — 3,800+ guides across Python, Java, C#, TypeScript, Go, Rust, SQL, Docker, Kubernetes and more — and I build 15 browser-based developer tools that never upload your data (https://www.ryuslog.com/tools).

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
