6.10 Logging

Logging goes through Log4j 2 (ai.ownsona.*). The package’s level is forced to INFO during the static initializer (so the startup banner, migrator output, and re-embed progress all land in the journal) and dropped to ERROR once startup completes (silencing per-request INFO).

To re-enable INFO for diagnostics, change the trailing Configurator.setLevel call in MCPServer.<clinit> to Level.INFO, redeploy.

Under systemd, application stdout flows to journald, not catalina.out. Inspect with journalctl -u ownsona.service.

6.10.1 What is and isn’t logged