Tolstoy's Guide to Debugging Your Applications
summary
Covers concrete CF failure modes and how they get diagnosed: credential rot fixed by Genesis and CredHub, staging failures from network or buildpack mismatch, exhausted PostgreSQL connection limits, and JVM native-memory vs heap misconfiguration. Gives reproducible debugging steps — use cf logs, cf ssh into Diego cells, check Doppler/Cell logs, run TCP and HTTP trace, and inspect the blobstore (example: missing S3 bucket causing an Unknown Error). Describes a homegrown color cutter that captures POST bodies for debugging HTTP payload problems.
AI-written summary · about
chapters (12)
- 0:00Start
- 4:48Resources
- 5:16Configuration
- 6:21Human Mistakes
- 10:03App Staging Failure
- 10:19Buildpack failure
- 10:29App not running after stage
- 11:05Unknown Error
- 11:32NO App Logs
- 13:16CF_TRACE +BOSH SSH+SYS Logs
- 17:21Use tools
- 18:56Ask Different Questions
related talks
54mDebugging Effectively
41mDebug like a scientist
29mFilling the Knowledge Gap: Debugging Edition
29m10 common errors when pushing applications to CloudFoundry
38mFrom the Exorcist to Hercule Poirot
35mDebugging the Mind: A Programmer's Guide to Critical Thinking
18mThe art of investigating problems in software
30mReporting Bugs: Errors Made and Lessons Learned