Linux services can appear active while applications are unresponsive

Systemd, the Linux process supervisor, reports a service as active simply because its main process ID exists in the kernel's task list. It does not monitor whether the application is actually ready to handle network traffic or is healthy internally. This can lead to situations where a service shows a green, running status but is frozen, deadlocked, or otherwise unable to accept connections. The disconnect occurs because systemd's role is process supervision, not application health inspection.