2017-08-09 119 views
1

Cassandra总是正常的,但是今天当我进入cassandra的bin文件夹并运行./cassandra时,没有任何响应,只需进入新的命令行并且没有打开过程。而且我也无法打开cqlsh。你能帮我解决这个问题吗?我无法打开cassandra

SYSTEM.LOG显示唯一的错误:

ERROR [main] 2017-08-07 10:33:59,154 CassandraDaemon.java:655 - Port already in use: 7199; nested exception is: 
java.net.BindException: Address already in use (Bind failed) 
java.net.BindException: Address already in use (Bind failed)   
at java.net.PlainSocketImpl.socketBind(Native Method) ~[na:1.8.0_141]   
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) ~[na:1.8.0_141] 
at java.net.ServerSocket.bind(ServerSocket.java:375) ~[na:1.8.0_141]   
at java.net.ServerSocket.<init>(ServerSocket.java:237) ~[na:1.8.0_141] 
at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:231) ~[na:1.8.0_141] 
at org.apache.cassandra.utils.RMIServerSocketFactoryImpl.createServerSocket(RMIServerSocketFactoryImpl.java:33) ~[apache-cassandra-2.2.10.jar:2.2.10]   
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:666) ~[na:1.8.0_141]  
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:330) ~[na:1.8.0_141]  
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:249) ~[na:1.8.0_141]  
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411) ~[na:1.8.0_141]  
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) ~[na:1.8.0_141]  
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:236) ~[na:1.8.0_141]  
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:213) ~[na:1.8.0_141]  
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:173) ~[na:1.8.0_141]  
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:144) ~[na:1.8.0_141]  
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239) ~[na:1.8.0_141]  
at org.apache.cassandra.service.CassandraDaemon.maybeInitJmx(CassandraDaemon.java:119) [apache-cassandra-2.2.10.jar:2.2.10]  
at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:188) [apache-cassandra-2.2.10.jar:2.2.10]  
at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:533) [apache-cassandra-2.2.10.jar:2.2.10]  
at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:642) [apache-cassandra-2.2.10.jar:2.2.10] 
+2

检查system.log的任何错误 –

+0

我已经在问题中添加了错误,但我想也许是这个问题 – Oak

回答

0

好像端口已在使用。 你可以杀死过程如下

sudo fuser -n tcp 7199 

它会显示该端口上运行的所有进程ID。 你可以使用下面的命令杀死。

sudo kill -9 Pid 

现在开始卡桑德拉。它将开始。

+0

我是root用户,所以没有sudo。并找不到热熔器命令 – Oak

+0

找到** ps ax | grep cassandra **并杀死该进程ID。 –

+0

root @ srv-machine-learning01:〜#ps ax | grep cassandra 845 pts/2 S + 0:00 grep cassandra root @ srv-machine-learning01:〜#kill -9 845 -bash:kill(845) - 没有这样的过程 – Oak

0

如果某件事情合法地使用默认的JMX端口(7199),您可以很容易地更改Cassandra用于JMX的端口。寻找在cassandra-env.sh文件JMX_PORT线,并将其更改为您知道是不是正在使用的端口:

JMX_PORT="7199" 

到:

JMX_PORT="9455" 

消除端口冲突,并查看是否卡桑德拉将开始然后。