What causes "--proxied-server-log-path %v" in gastownhall/beads?

Read the wrapped detail after '--proxied-server-log-path ' for the exact cause

--proxied-server-log-path %v

Error message

--proxied-server-log-path %v

What it means

The log path file failed validateProxiedServerLogPath; init wraps the validator's message behind this prefix. Typical causes are a nonexistent parent directory or a path that is a directory rather than a writable file location.

Source

Thrown at cmd/bd/init.go:466

			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-config-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverConfigPath) {
				return fmt.Errorf("--proxied-server-config-path must be an absolute path, got %q", serverConfigPath)
			}
			if err := validateProxiedServerConfig(serverConfigPath); err != nil {
				return fmt.Errorf("--proxied-server-config-path %v", err)
			}
		}
		if serverLogPath != "" {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-log-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverLogPath) {
				return fmt.Errorf("--proxied-server-log-path must be an absolute path, got %q", serverLogPath)
			}
			if err := validateProxiedServerLogPath(serverLogPath); err != nil {
				return fmt.Errorf("--proxied-server-log-path %v", err)
			}
		}
		if serverRootPath != "" {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-root-path requires --proxied-server")
			}
			if !filepath.IsAbs(serverRootPath) {
				return fmt.Errorf("--proxied-server-root-path must be an absolute path, got %q", serverRootPath)
			}
			if err := validateProxiedServerRootPath(serverRootPath); err != nil {
				return fmt.Errorf("--proxied-server-root-path %v", err)
			}
		}
		if serverProxyPort != 0 {
			if !initProxiedServer {
				return fmt.Errorf("--proxied-server-port requires --proxied-server")
			}
			if serverProxyPort < 1 || serverProxyPort > 65535 {

View on GitHub (pinned to 71377f2769)

Solutions

Read the wrapped detail after '--proxied-server-log-path ' for the exact cause
Create the parent directory (mkdir -p) and ensure write permission
Point the flag at a file path, not an existing directory

Example fix

// before
bd init --proxied-server --proxied-server-log-path /var/log/bd/bd.log  # dir missing
// after
mkdir -p /var/log/bd && bd init --proxied-server --proxied-server-log-path /var/log/bd/bd.log

Defensive patterns

Strategy: validation

Validate before calling

LOG=/var/log/bd/bd.log
mkdir -p "$(dirname "$LOG")" && [ ! -d "$LOG" ] && [ -w "$(dirname "$LOG")" ] || { echo 'bad log path'; exit 1; }

Prevention

mkdir -p the log parent directory before init
Ensure the path is a file location, not an existing directory
Verify write permission on the log directory for the bd process user

When it happens

Trigger: Running `bd init --proxied-server --proxied-server-log-path <path>` where the parent directory does not exist, the path is not writable, or it points to a directory.

Common situations: Typo'd log directories; log path inside a read-only mount; forgetting to mkdir the log directory before init.

Understand the failure class

Background: Config validation failed: what "invalid value for {key}" and settings-rejection errors mean across 19 open-source libraries — this error's family across 19 libraries.

Related errors

AI-assisted analysis of gastownhall/beads@71377f2769 (2026-08-30). Data as JSON: /api/errors/a2e523f2b4c5f311. Report an issue: GitHub.