Port process down
Modified on Mon, 23 Jun, 2025 at 8:56 AM
When a monitor reports a port is down, there can be two possible causes:
- The process listening on that port is down:
- Handle this as an AMA - Process Down (docker-swarm) issue.
- The port is open but does not accept connections from other nodes, which causes the monitor to fail:
- Check the connection locally first using
telnet. - Check the connection from another node (if applicable).
- Verify the firewall (iptables):
- Run
iptables -L. - If the port is blocked by the firewall:
- Save the current iptables rules:
iptables-save > /etc/network/iptables.rules - Modify the rules to allow connections to that port according to your policy.
- Apply the updated rules:
iptables-restore < /etc/network/iptables.rules
- Save the current iptables rules:
- Run
- If the port is configured to listen only on localhost (
127.0.0.1), escalate to the solutions team to reconfigure the process to listen on all interfaces (0.0.0.0).
- Check the connection locally first using
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article