9 open findingsin prod

Grouped under the component believed to be causing them.

Broken route — nothing is listening on port 3050

critical

Broken route — nothing is listening on port 3050

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-3050blocks 1 component

Broken route — nothing is listening on port 3051

critical

Broken route — nothing is listening on port 3051

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-3051blocks 1 component

Broken route — nothing is listening on port 3060

critical

Broken route — nothing is listening on port 3060

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-3060blocks 1 component

Broken route — nothing is listening on port 3070

critical

Broken route — nothing is listening on port 3070

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-3070blocks 1 component

Broken route — nothing is listening on port 7880

critical

Broken route — nothing is listening on port 7880

first seen 44h ago

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

How to resolve

Start the service that is supposed to own port 7880, 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-7880blocks 1 component

Broken route — nothing is listening on port 8090

critical

Broken route — nothing is listening on port 8090

first seen 44h 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 innovation.ogmworld.com, ip10.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.

ogm:prod:prod-kvm8:port:127.0.0.1-8090blocks 1 component

Broken route — nothing is listening on port 8091

critical

Broken route — nothing is listening on port 8091

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-8091

Broken route — nothing is listening on port 8092

critical

Broken route — nothing is listening on port 8092

first seen 44h 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.

ogm:prod:prod-kvm8:port:127.0.0.1-8092blocks 1 component

Kubernetes API server is not reachable

critical

Kubernetes API server is not reachable

first seen 44h ago

Kubernetes API server is not serving on :6443. kubelet is running, and the static pod manifests are still in place, so this is a runtime failure rather than a removed cluster. kubectl reports: The connection to the server 31.220.52.144:6443 was refused - did you specify the right host or port?

How to resolve

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-kvm8blocks 3 components