Cust1

Customer 1 runs a small web platform on two hosts: the web host cust1 and the database host db1.

Hosts

Host	Role	Agent access
cust1.gobyl.cc	Website and application	ssh as root, key in OpenBao at secret/customers/cust1
db1.gobyl.cc	PostgreSQL database	Read-only: ssh as dbops (no sudo), key at secret/customers/cust1-db. See Db1

Services on cust1

Service	How it runs	Port	Notes
Website	nginx, static files in /var/www/html	80	Public trading dashboard with a live platform-telemetry graph. Market data and the telemetry traces are generated in the browser, so the page renders with the application down and the graph is not a measurement of the host
Application	systemd unit nodeapp, code in /opt/app	3000	Account service: serves customer positions from PostgreSQL on db1 as JSON at /api/positions, which the website fetches. Reads config from /opt/app/config.json

Operational notes

• Restart services with systemctl restart nginx|nodeapp.
• Application logs: journalctl -u nodeapp. It exits nonzero if /opt/app/config.json is missing or the database is unreachable.
• The database is PostgreSQL on Db1, port 5432, reachable only from inside the network. If the app reports database errors, check db1 too - but remember this agent may only diagnose there, not change anything.
• Disk pressure history: log growth under /var/log has filled the disk before. Safe to delete old files in /var/log/app-debug/.
• Monitoring: Icinga checks website, nodeapp and disk on cust1, and postgres and disk on db1, from the ops core host.

Escalation

Before changing anything, check the Maintenance calendar and open tickets for planned work. If the fix is not obvious or requires data-destructive steps, stop and hand over to the on-call engineer in the Incidents channel. Changes on db1 always require an engineer (or an emergency access grant) - see Db1.