Skip to content

docs: correct log locations in DEPLOYMENT.md (buildlog.txt not on shared FS) - #1312

Merged
jonfroehlich merged 1 commit into
masterfrom
1252-fix-deployment-log-paths
Jun 15, 2026
Merged

docs: correct log locations in DEPLOYMENT.md (buildlog.txt not on shared FS)#1312
jonfroehlich merged 1 commit into
masterfrom
1252-fix-deployment-log-paths

Conversation

@jonfroehlich

Copy link
Copy Markdown
Member

Documentation-only. Found while debugging the 2.8.2 prod deploy.

docs/DEPLOYMENT.md implied all four logs (debug.log, buildlog.txt, httpd-access.log, httpd-error.log) could be tailed via SSH under /cse/web/research/makelab/www. In reality only debug.log is on the shared CSE filesystem (with a rotated debug.log.1). buildlog.txt and the httpd-*.log files live on the Docker host (grabthar / docker-test2), which isn't SSH-reachable — they're available via the web /logs/ URL or the deploy email.

Changes:

  • Log table now has a "Where to find it" column making the location of each log explicit.
  • Scoped the Accessing Logs via SSH section to debug.log and added an scp example for pulling it down.
  • Added a note that buildlog.txt is emailed on every push (the most reliable copy).

No code change.

🤖 Generated with Claude Code

…red FS)

While debugging a prod deploy we found buildlog.txt is NOT under
/cse/web/research/makelab/www on recycle — only debug.log (+ rotated
debug.log.1) is mounted to the shared CSE filesystem. buildlog.txt and the
httpd-*.log files live on the Docker host (grabthar/docker-test2), which is
unreachable via SSH; they're available via the web /logs/ URL or the deploy
email. Clarified the log table with a "Where to find it" column, scoped the
SSH instructions to debug.log, and added an scp example.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jonfroehlich
jonfroehlich merged commit 568200f into master Jun 15, 2026
1 check passed
@jonfroehlich
jonfroehlich deleted the 1252-fix-deployment-log-paths branch June 15, 2026 23:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant