Repository navigation
Commit c0ced5d
Build with --noBuildLock and clear a stale lock first
Hugo takes an flock on .hugo_build.lock at startup and waits for it
indefinitely with no message, no error and no timeout. The observed symptom
is a build that copies the static files and then stops: 66 files and 16 MB
in the staging tree, a sleeping process at near-zero CPU, low RSS, and no
further output. Reproduced exactly by holding the lock against an otherwise
healthy build.
The workspace is on NFS, where a lock left by an uncleanly killed build
outlives the process that took it, so this recurs on its own. The lock also
guards against a concurrent second build, which cannot happen here: the
container is the only builder and Rancher runs it start_once. It protects
nothing and fails invisibly.
Clear any stale lock file as well, so nothing is left lying around now that
Hugo no longer manages it.
Verified: with the lock held, the build now completes rather than hanging.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X1AuLA5tHPwpD7Hp5utPkS1 parent 22843cf commit c0ced5d
1 file changed
Lines changed: 16 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
40 | | - | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
41 | 56 | | |
42 | 57 | | |
43 | 58 | | |
| |||
0 commit comments