You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Timothy Palpant <ti...@palpant.us> on 2019/02/22 23:31:01 UTC
NullPointerException when running nodetool stopdaemon
I am trying to use `nodetool stopdaemon` to stop Cassandra but hitting the
following error:
```
$ cassandra_ctl nodetool -h 127.0.0.1 -p 5100 stopdaemon
error: null
-- StackTrace --
java.lang.NullPointerException
at
org.apache.cassandra.config.DatabaseDescriptor.getDiskFailurePolicy(DatabaseDescriptor.java:1877)
at
org.apache.cassandra.utils.JVMStabilityInspector.inspectThrowable(JVMStabilityInspector.java:62)
at
org.apache.cassandra.tools.nodetool.StopDaemon.execute(StopDaemon.java:39)
at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:254)
at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:168)
```
This looks very similar to:
https://issues.apache.org/jira/browse/CASSANDRA-13030
but I am running v3.11.1, which has that fix in it:
```
$ cassandra_ctl nodetool -h 127.0.0.1 -p 5100 version
ReleaseVersion: 3.11.1
```
Has anyone else run into this problem, or know of a way to work around it?
(or am I running the command incorrectly?)
Thanks!
Tim
Re: NullPointerException when running nodetool stopdaemon
Posted by dm...@gmail.com,
dm...@gmail.com.
On 2019/02/22 23:31:01, Timothy Palpant <ti...@palpant.us> wrote:
> I am trying to use `nodetool stopdaemon` to stop Cassandra but hitting the
> following error:
>
> ```
> $ cassandra_ctl nodetool -h 127.0.0.1 -p 5100 stopdaemon
> error: null
> -- StackTrace --
> java.lang.NullPointerException
> at
> org.apache.cassandra.config.DatabaseDescriptor.getDiskFailurePolicy(DatabaseDescriptor.java:1877)
> at
> org.apache.cassandra.utils.JVMStabilityInspector.inspectThrowable(JVMStabilityInspector.java:62)
> at
> org.apache.cassandra.tools.nodetool.StopDaemon.execute(StopDaemon.java:39)
> at org.apache.cassandra.tools.NodeTool$NodeToolCmd.run(NodeTool.java:254)
> at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:168)
> ```
>
> This looks very similar to:
> https://issues.apache.org/jira/browse/CASSANDRA-13030
> but I am running v3.11.1, which has that fix in it:
>
> ```
> $ cassandra_ctl nodetool -h 127.0.0.1 -p 5100 version
> ReleaseVersion: 3.11.1
> ```
>
> Has anyone else run into this problem, or know of a way to work around it?
> (or am I running the command incorrectly?)
>
> Thanks!
> Tim
>
Hello,
Two months ago, i got the same issue when i did upgrade minor from DSE 5.1.8 to 5.1.12
error message was:
Jan 23, 2019 10:12:25 AM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: error unmarshalling return; nested exception is:
java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: javax.management.remote.rmi.RMIJRMPServerImpl]
Jan 23, 2019 10:12:25 AM ClientCommunicatorAdmin Checker-run
WARNING: Failed to check connection: java.rmi.NoSuchObjectException: no such object in table
Jan 23, 2019 10:12:25 AM ClientCommunicatorAdmin Checker-run
WARNING: stopping
suggestion: The cassandra process did not exit and i killed it manually before restarting DSE
Datastax is working on this bug .
For now, with this version, you can use these two commands:
nodetool -h hostname drain
after it finish, kill java process
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@cassandra.apache.org
For additional commands, e-mail: user-help@cassandra.apache.org