Grouped under the component believed to be causing them.
2 findings attributed to this component
CrashLoopBackOff: back-off 5m0s restarting failed container=app pod=reqiq-9f796dd5d-524dk_innovation(899d2455-308c-4c6b-b15d-007f5aadf834)
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.
No replicas ready out of 1 desired.
This workload is serving no traffic. Check its pods with 'kubectl get pods -n innovation -l' matching its selector, then describe the failing pod.
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.
Run 'systemctl status certbot.service' and 'certbot renew --dry-run' to see why renewal is failing, and check certificate expiry with 'certbot certificates'.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Run 'systemctl status certbot.service' and 'certbot renew --dry-run' to see why renewal is failing, and check certificate expiry with 'certbot certificates'.
Container is exited.
Inspect why it stopped with 'docker logs --tail 100 ogm-dbgate'. If it is part of a compose project, 'docker compose up -d' from that project's directory will recreate it.
Container is exited.
Inspect why it stopped with 'docker logs --tail 100 ogm-uptime-kuma'. If it is part of a compose project, 'docker compose up -d' from that project's directory will recreate it.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848530-r4n28' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848545-x8w9x' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848560-nz8g2' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848575-29j56' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-56544f4f64-58wrm' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848515-hv8gn' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848530-mgxcg' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848545-6tn56' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848560-n7xmw' and read the Events section.
No longer reported by its host — was present in the previous collection.
Run 'kubectl describe pod -n inspector ogm-inspector-collect-29848575-p8pl6' and read the Events section.
nfs is healthy on ogm-datacenter, but Dev — KVM4 cannot open a TCP connection to it (port 2049). The services are up; the network path is not.
This is a network path problem, not a service problem. ogm-datacenter publishes these ports through Docker, which bypasses plain 'ufw allow' rules — the allow-list lives in the DOCKER-USER chain, maintained by scripts/setup-firewall.sh in the ogm-datacenter repository. Add this host's public IP to the ALLOWED_SOURCES array in that script and re-run it, then re-collect to confirm.