Are there really no entries after those INFO messages? That indicates that
a person/script/daemon/tool/process killed Cassandra. Perhaps check the OS
logs to see if oom-killer kicked in to see if the C* process was
terminated. Cheers!
>
Nothing in the cassandra logs (system/debug) last lines are
INFO [RMI TCP Connection(10)-127.0.0.1] 2022-02-06 08:41:50,334
BinLog.java:420 - Attempting to configure bin log: Path: /mnt/fql_data Roll
cycle: HOURLY Blocking: true Max queue weight: 268435456 Max log
size:34359738368 Archive command
That looks like a nodetool stack - can you check the Cassandra log for
corresponding error?
> On Feb 6, 2022, at 12:52 AM, Gil Ganz wrote:
>
>
> Hey
> I'm trying to enable full query log on cassandra 4.01 node and it's causing
> cassandra to shutdown
>
> nodetool enablefullquerylog --path
Hey
I'm trying to enable full query log on cassandra 4.01 node and it's causing
cassandra to shutdown
nodetool enablefullquerylog --path /mnt/fql_data
Cassandra has shutdown.
error: null
-- StackTrace --
java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:267)
