-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nettest does not validate whether ports are open #32
Comments
I suspect that this could be very expensive due to combinatorial explosion if its any more than just checking the state of the firewall on each node. Could you please expand your thoughts a little? |
How about a different test? How about we run nmap to all nodes from one node of each node type? Would this solve your issue? |
I didn't mean to run a full iperf3 test against all ports we use, just to check if a TCP connect goes through. I'd not want to pull in nmap for such a simple test. |
Ok so to get this clear in my head: (1) detect if ceph is running and shut down if so. Is that the summary? |
Wait, why would you shutdown Ceph? No - though detecting this and warning is a good idea. You'd not want a diagnosis tool to disrupt cluster operation. netcat is a good option, yes. |
I don want to make the test for firewall invasive, but to do this I suspect it has to be invasive. 2 different processes cant bind to the same port, so you cant test a message passed the firewall if another process is bound to the port. I am also concerned about the runtime of such a test. |
Closing since nettest componentis currently being re-written. |
Fix for ntp to start without error:
There could be firewall rules or others interfering.
Maybe running quick iperf3 tests or similar against the ports that we expect the nodes to use (from ceph.conf)?
The text was updated successfully, but these errors were encountered: