Can you describe the type of environment you are running in? This sure sounds like odd firewall behavior I’ve seen in the past.
> On Oct 31, 2023, at 4:56 PM, Ben Klein <bklein...@gmail.com> wrote: > > On October 30, 2023, at approximately 15:38 UTC, Cassandra stopped responding > to TCP pings on port 9042 and to nodetool requests. However, systemd reported > that it was still online. The first node to fail was the seed node > (192.168.0.44), followed within the next couple minutes by the other two > (192.168.0.15 and 192.168.0.20). Looking through the logs on the first node, > I did not see anything out of the ordinary. When the service was restarted > (through systemd), it came up with no problem, but this is the second time > this has happened in the last month. > > I have attached all of the log files from the primary node. I have also > attached the cassandra.yaml file, which is the same on all three nodes. > > What could possibly be causing this? Is there anything else that I should be > looking at? > > <cassandra.log><cassandra.yaml><gc.log><system.log>
