Opening the bbolt database only reported timeout, which sounds like a broken config. Catch bolt.ErrTimeout with errors.Is and say another process holds the lock, and that caddy reload is the right command when Caddy is already running. The error stays fatal. |
||
|---|---|---|
| .. | ||
| caddyevents | ||
| caddyfs | ||
| caddyhttp | ||
| caddypki | ||
| caddytls | ||
| filestorage | ||
| internal/network | ||
| logging | ||
| metrics | ||
| standard | ||