14 open findingsin prod

Grouped under the component believed to be causing them.

Workload innovation/reqiq has no ready replicas

2 findings attributed to this component

critical

Pod innovation/reqiq-9f796dd5d-524dk is crash-looping

first seen 2h ago

CrashLoopBackOff: back-off 5m0s restarting failed container=app pod=reqiq-9f796dd5d-524dk_innovation(899d2455-308c-4c6b-b15d-007f5aadf834)

How to resolve

Read the previous container's logs with 'kubectl logs -n innovation reqiq-9f796dd5d-524dk --previous'. A crash loop immediately after deploy is usually a missing environment variable or an unreachable dependency.

critical

Workload innovation/reqiq has no ready replicas

first seen 2h ago

No replicas ready out of 1 desired.

How to resolve

This workload is serving no traffic. Check its pods with 'kubectl get pods -n innovation -l' matching its selector, then describe the failing pod.

Broken route — nothing is listening on port 3050

critical

Broken route — nothing is listening on port 3050

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:3050, but no process on this host is bound to that port. Requests to ip10.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 3050, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 3051

critical

Broken route — nothing is listening on port 3051

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:3051, but no process on this host is bound to that port. Requests to investor.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 3051, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 3060

critical

Broken route — nothing is listening on port 3060

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:3060, but no process on this host is bound to that port. Requests to homechore.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 3060, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 3070

critical

Broken route — nothing is listening on port 3070

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:3070, but no process on this host is bound to that port. Requests to sentinelloop.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 3070, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 8090

critical

Broken route — nothing is listening on port 8090

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:8090, but no process on this host is bound to that port. Requests to ip10.ogmworld.com, innovation.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 8090, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 8091

critical

Broken route — nothing is listening on port 8091

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:8091, but no process on this host is bound to that port. Requests to innovation.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 8091, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

Broken route — nothing is listening on port 8092

critical

Broken route — nothing is listening on port 8092

first seen 2h ago

nginx is configured to forward traffic to 127.0.0.1:8092, but no process on this host is bound to that port. Requests to investor.ogmworld.com will return 502 Bad Gateway.

How to resolve

Start the service that is supposed to own port 8092, or remove the stale nginx route if the application has been retired. Check 'docker ps -a' and 'systemctl list-units --state=failed' on this host — a container or unit that exited is the usual cause.

systemd unit certbot.service has failed

critical

systemd unit certbot.service has failed

first seen 2h ago

The certificate renewal unit is in a failed state. TLS certificates renew on a timer; if this stays failed, certificates will silently expire and every HTTPS site on this host will start refusing connections.

How to resolve

Run 'systemctl status certbot.service' and 'certbot renew --dry-run' to see why renewal is failing, and check certificate expiry with 'certbot certificates'.

Pod inspector/ogm-inspector-collect-29848530-r4n28 is not running

Pod inspector/ogm-inspector-collect-29848545-x8w9x is not running

Pod inspector/ogm-inspector-collect-29848560-nz8g2 is not running

Pod inspector/ogm-inspector-collect-29848575-29j56 is not running