Config loading logs spurious "Failed to load config" at Info level #27

New Issue

clawbot · 2026-03-02T01:29:58+01:00

clawbot commented

2026-03-02 01:29:58 +01:00

Bug

When running without a config.yaml file (common for env-var-only deployments and Docker), five identical messages are logged at Info level on every startup:

{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}
{"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"}

This comes from pkg/config and is confusing because:

It says "Failed" which implies an error, but the app works fine without a config file
It appears 5 times (presumably once per config key lookup)
It's at Info level, polluting normal startup logs

Fix

Either:

Change these to Debug level so they only appear when DEBUG=true
Check for config file existence once at startup and only log one message
Suppress the message entirely when no config file is expected (env-var-only mode)

Category

Nice-to-have. Cosmetic but affects operational clarity.

## Bug When running without a `config.yaml` file (common for env-var-only deployments and Docker), five identical messages are logged at Info level on every startup: ```json {"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"} {"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"} {"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"} {"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"} {"level":"INFO","msg":"Failed to load config: configuration file config.yaml not found in directory tree"} ``` This comes from `pkg/config` and is confusing because: 1. It says "Failed" which implies an error, but the app works fine without a config file 2. It appears 5 times (presumably once per config key lookup) 3. It's at Info level, polluting normal startup logs ## Fix Either: 1. Change these to Debug level so they only appear when DEBUG=true 2. Check for config file existence once at startup and only log one message 3. Suppress the message entirely when no config file is expected (env-var-only mode) ## Category Nice-to-have. Cosmetic but affects operational clarity.

clawbot added the

bot

label 2026-03-02 01:29:58 +01:00

clawbot referenced this issue

2026-03-02 01:31:01 +01:00

1.0/mvp #15

clawbot referenced this issue from a commit

2026-03-02 01:42:01 +01:00

fix: remove spurious config load log message (closes #27)

clawbot referenced this issue

2026-03-02 01:42:14 +01:00

feat: webhooker 1.0 MVP — entity rename, core engine, delivery, management UI #16

clawbot referenced this issue

2026-03-02 01:42:33 +01:00

1.0/mvp #15

clawbot referenced this issue

2026-03-02 02:23:31 +01:00

feat: webhooker 1.0 MVP — entity rename, core engine, delivery, management UI #16

sneak commented

2026-03-02 07:52:25 +01:00

let’s get rid of file-based configuration entirely.

clawbot commented

2026-03-02 07:54:00 +01:00

Understood — removing file-based configuration entirely. Env vars only, no Viper, no config.yaml. Will implement after the current delivery engine worker pool rework completes (same branch).

clawbot referenced this issue from a commit

2026-03-02 08:06:16 +01:00

refactor: remove file-based configuration, use env vars only

clawbot referenced this issue

2026-03-02 08:06:38 +01:00

feat: webhooker 1.0 MVP — entity rename, core engine, delivery, management UI #16

sneak closed this issue

2026-03-04 01:19:43 +01:00

Sign in to join this conversation.