OGM Inspector

Components

229

Relationships

292

Critical

Warnings

Down

Last collection

16h ago

5/5 hosts

Probable root causes

Ranked by how much of the current breakage each one explains.

Kubernetes API server is not reachable3 components downstream
Check the static pod containers with 'crictl ps -a | grep kube-apiserver' and read 'journalctl -u kubelet -p err -n 50' for the reason the container will not start. Until this is resolved, no deployment, scaling or self-healing can happen on this cluster.
ogm:prod:prod-kvm8:k8s_control_plane:k8s-control-plane@prod-kvm8
Broken route — nothing is listening on port 30501 component downstream
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.
ogm:prod:prod-kvm8:port:127.0.0.1-3050
Broken route — nothing is listening on port 30511 component downstream
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.
ogm:prod:prod-kvm8:port:127.0.0.1-3051
Broken route — nothing is listening on port 30601 component downstream
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.
ogm:prod:prod-kvm8:port:127.0.0.1-3060

kubernetes · systemd · nginx

9 down54 healthy3 unknown

Public hostnames

kubernetes · systemd · nginx

1 down52 healthy2 unknown

Public hostnames

docker · systemd · nginx

25 healthy1 unknown

Public hostnames

docker · systemd

3 down1 degraded76 healthy2 unknown

nginx forwards these hostnames to a port with no process listening — visitors get a 502.

Environment	Backend	Reason
prod	127.0.0.1:3050	nginx forwards ip10.ogmworld.com/ here, but nothing is listening on port 3050 on this host.
prod	127.0.0.1:3051	nginx forwards investor.ogmworld.com/ here, but nothing is listening on port 3051 on this host.
prod	127.0.0.1:3060	nginx forwards homechore.ogmworld.com/_next/static/ here, but nothing is listening on port 3060 on this host.
prod	127.0.0.1:3070	nginx forwards sentinelloop.ogmworld.com/_next/static/ here, but nothing is listening on port 3070 on this host.
prod	127.0.0.1:7880	nginx forwards meet.ogmworld.com/ here, but nothing is listening on port 7880 on this host.
prod	127.0.0.1:8090	nginx forwards ip10.ogmworld.com^~ /api/ here, but nothing is listening on port 8090 on this host.
prod	127.0.0.1:8091	nginx forwards innovation.ogmworld.com/reqiq/ here, but nothing is listening on port 8091 on this host.
prod	127.0.0.1:8092	nginx forwards investor.ogmworld.com^~ /api/ here, but nothing is listening on port 8092 on this host.
stage	127.0.0.1:32229	nginx forwards stage.samskriti.ogmworld.com/ here, but nothing is listening on port 32229 on this host.