3.16.1 Service control ¶

sudo systemctl status   ownsona.service
sudo systemctl restart  ownsona.service     # required after any application.ini change
sudo systemctl stop     ownsona.service
sudo systemctl start    ownsona.service
journalctl -u ownsona.service -f             # live application + Tomcat logs

3.16.2 Code change ⇒ deploy ¶

cd /home/ownsona/ownsona
./bld -v build && ./bld war
cp work/Kiss.war /home/ownsona/tomcat/webapps/ROOT.war
# autoDeploy redeploys in ~10 s; no service restart needed for code changes.

application.ini is read once at servlet load, so editing it requires a fresh build (so the new ini lands in the WAR) followed by redeploy or service restart.

3.16.3 Backup control ¶

sudo systemctl list-timers ownsona-backup.timer       # next run
sudo systemctl start ownsona-backup.service           # one-shot now
sudo tail -f /var/log/ownsona-backup.log              # last run + history

3.16.4 Log retention summary ¶

3.16.5 Rotating the bearer token ¶

Generate a new token, update OWNSONA_API_TOKEN in src/main/backend/application.ini, run ./bld -v build && ./bld war to rebuild the WAR, redeploy, and distribute the new token to MCP clients. There is no dual-token grace window; clients see a 401 until they update.

3.16.6 Top common failure modes ¶

• journalctl -u ownsona.service shows BindException: Permission denied: the service couldn’t bind 80/443. systemd’s AmbientCapabilities is missing from ownsona.service, or the service’s User= was changed and the override no longer applies.
• MCP returns EMBEDDING_ERROR with insufficient_quota: the OpenAI account is out of credit. Top up; auth, DB, listing, and text search keep working.
• MCP returns AUTH_FAILED on every request: OWNSONA_API_TOKEN doesn’t match what the client is sending, or the WAR wasn’t rebuilt/redeployed after editing the ini.
• First request after deploy is slow / 404: Tomcat is still redeploying the WAR; ~10 s window with autoDeploy="true".