Watchtower Control Room

Somchai Scheduler

Monitor connected apps, review incidents, onboard new projects, and keep your operational contract in one calm place.

production

Somchai Scheduler

Healthy

http://100.67.241.67:18080/health

Container Pattern
somchai-scheduler
Source
Manual
Container
chili-radio-somchai-somchai-scheduler-1
Last Alert
None yet
Open Errors
0
Open Warnings
0
Info Events
0
Monitoring
Active
Edit project Implementation guide
Health

Endpoint Snapshot

LIVE

http://100.67.241.67:18080/health

Healthy
Status Code
200
Response Time
24 ms
Failures
0
Recent Alerts

Somchai Scheduler Incident Feed

Somchai Scheduler · Health

Live health recovered

Info
Live endpoint recovered for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:11:59 UTC
View raw incident details
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 28ms
Recovered at: 2026-06-23T06:11:59.484024+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Scheduler · Health

Live health check failed

Info
Live endpoint is failing for Somchai Scheduler
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:11:59 UTC
View raw incident details
Project: Somchai Scheduler
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 10996ms
Consecutive failures: 2
Checked at: 2026-06-23T06:02:52.475321+00:00
Somchai Scheduler · Log

1 log error(s) detected

Error
### Error 1: Database Connection Timeout * **Root Cause:** The application failed to establish a connection to its PostgreSQL database within the allowed time. The `psycopg` library, which the application uses to talk to the database, gave up after waiting for a response that never came. * **Simple Explanation:** The application tried to call the database, but the database didn't pick up the phone in time. * **Things to Investigate:** * **Network Issues:*…
Status: Recorded Occurrences: 1 Last seen: 2026-06-23 06:10:57 UTC
View full analysis
### Error 1: Database Connection Timeout * **Root Cause:** The application failed to establish a connection to its PostgreSQL database within the allowed time. The `psycopg` library, which the application uses to talk to the database, gave up after waiting for a response that never came. * **Simple Explanation:** The application tried to call the database, but the database didn't pick up the phone in time. * **Things to Investigate:** * **Network Issues:** Check if there are any network problems (e.g., firewall rules, DNS issues) preventing the application server from reaching the database server. * **Database Health:** Verify that the PostgreSQL database is running, healthy, and not overloaded. An overloaded database may be too slow to accept new connections. * **Configuration:** Double-check that the database hostname, port, and other connection details in the application's configuration are correct. * **Severity:** **CRITICAL**. The application cannot perform its core functions without a database connection.
View raw incident details
Fingerprint: cee6e7c5115a
Occurrences: 1

2026-06-23T06:10:11.960947330Z psycopg.errors.ConnectionTimeout: connection timeout expired
Somchai Scheduler · Log

1 log error(s) detected

Error
**Error 1: Database Connection Timeout** * **Root Cause:** The application failed to establish a connection with its PostgreSQL database within the configured time limit. * **Explanation:** The application tried to contact its database to read or write information, but the database did not respond in time. This is like making a phone call and hanging up because no one answered. * **Potential Fixes:** * **Check Database Health:** Verify the PostgreSQL data…
Status: Recorded Occurrences: 1 Last seen: 2026-06-23 06:04:47 UTC
View full analysis
**Error 1: Database Connection Timeout** * **Root Cause:** The application failed to establish a connection with its PostgreSQL database within the configured time limit. * **Explanation:** The application tried to contact its database to read or write information, but the database did not respond in time. This is like making a phone call and hanging up because no one answered. * **Potential Fixes:** * **Check Database Health:** Verify the PostgreSQL database server is running, healthy, and not overloaded. * **Verify Network Connectivity:** Ensure there are no network issues (e.g., firewall rules, DNS problems) preventing the application container from reaching the database server. * **Verify Configuration:** Double-check that the application's database connection details (hostname, port, credentials) are correct. * **Severity:** **CRITICAL**. An inability to connect to the database will likely render the entire application or its core features non-functional.
View raw incident details
Fingerprint: cee6e7c5115a
Occurrences: 1

2026-06-23T06:03:38.678652885Z psycopg.errors.ConnectionTimeout: connection timeout expired