Neo4j shell connect to local server: connection refused

1,521 views
Skip to first unread message

Normen Müller

unread,
Jan 8, 2015, 9:02:22 AM1/8/15
to ne...@googlegroups.com
Hi,

as posted at http://goo.gl/RSluPw I have some trouble with connecting to a local server via the shell. There I also posted, that after installing the shell-tools, the error disappeared ... which is unfortunately wrong.

Here is what I did: I installed neo4j-community-2.1.6 (without any modifications), started the server, and then wanted to connect via the shell (as stated here http://goo.gl/jI12RO). What am I missing here?

Also I wonder, why "waiting for server to be ready" lasts quite some time as well as the `neo4j-shell` command till it returns with an error.

Here is my console output:

[~/bin/neo4j]

$ ls

CHANGES.txt   NOTICE.txt    bin/          lib/

LICENSE.txt   README.txt    conf/         plugins/

LICENSES.txt  UPGRADE.txt   data/         system/

[~/bin/neo4j]

$ java -version

java version "1.7.0_67"

Java(TM) SE Runtime Environment (build 1.7.0_67-b01)

Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

[~/bin/neo4j]

$ ./bin/neo4j start

Using additional JVM arguments:  -server -XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties -Djava.util.logging.config.file=conf/logging.properties -Dlog4j.configuration=file:conf/log4j.properties -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow

Starting Neo4j Server...WARNING: not changing user

process [5481]... waiting for server to be ready............................................................................... OK.

http://localhost:7474/ is ready.

[~/bin/neo4j]

$ neo4j-shell

ERROR (-v for expanded information):

Exception creating connection to: 172.24.46.19; nested exception is: 

java.net.SocketException: Host is down


 -host      Domain name or IP of host to connect to (default: localhost)

 -port      Port of host to connect to (default: 1337)

 -name      RMI name, i.e. rmi://<host>:<port>/<name> (default: shell)

 -pid       Process ID to connect to

 -c         Command line to execute. After executing it the shell exits

 -file      File containing commands to execute, or '-' to read from stdin. After executing it the shell exits

 -readonly  Connect in readonly mode (only for connecting with -path)

 -path      Points to a neo4j db path so that a local server can be started there

 -config    Points to a config file when starting a local server


Example arguments for remote:

-port 1337

-host 192.168.1.234 -port 1337 -name shell

-host localhost -readonly

...or no arguments for default values

Example arguments for local:

-path /path/to/db

-path /path/to/db -config /path/to/neo4j.config

-path /path/to/db -readonly

[~/bin/neo4j]

$ neo4j-shell -v

ERROR (-v for expanded information):

Connection refused

java.rmi.ConnectException: Connection refused to host: 172.24.46.19; nested exception is: 

java.net.ConnectException: Operation timed out

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)

at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)

at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)

at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:129)

at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:194)

at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:148)

at com.sun.proxy.$Proxy1.welcome(Unknown Source)

at org.neo4j.shell.impl.AbstractClient.sayHi(AbstractClient.java:215)

at org.neo4j.shell.impl.RemoteClient.findRemoteServer(RemoteClient.java:63)

at org.neo4j.shell.impl.RemoteClient.<init>(RemoteClient.java:55)

at org.neo4j.shell.impl.RemoteClient.<init>(RemoteClient.java:43)

at org.neo4j.shell.ShellLobby.newClient(ShellLobby.java:165)

at org.neo4j.shell.StartClient.startRemote(StartClient.java:297)

at org.neo4j.shell.StartClient.start(StartClient.java:175)

at org.neo4j.shell.StartClient.main(StartClient.java:120)

Caused by: java.net.ConnectException: Operation timed out

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)

at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)

at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

at java.net.Socket.connect(Socket.java:579)

at java.net.Socket.connect(Socket.java:528)

at java.net.Socket.<init>(Socket.java:425)

at java.net.Socket.<init>(Socket.java:208)

at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)

at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:147)

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)

... 14 more


 -host      Domain name or IP of host to connect to (default: localhost)

 -port      Port of host to connect to (default: 1337)

 -name      RMI name, i.e. rmi://<host>:<port>/<name> (default: shell)

 -pid       Process ID to connect to

 -c         Command line to execute. After executing it the shell exits

 -file      File containing commands to execute, or '-' to read from stdin. After executing it the shell exits

 -readonly  Connect in readonly mode (only for connecting with -path)

 -path      Points to a neo4j db path so that a local server can be started there

 -config    Points to a config file when starting a local server


Example arguments for remote:

-port 1337

-host 192.168.1.234 -port 1337 -name shell

-host localhost -readonly

...or no arguments for default values

Example arguments for local:

-path /path/to/db

-path /path/to/db -config /path/to/neo4j.config

-path /path/to/db -readonly

[~/bin/neo4j]



Why is the shell trying to connect to host: 172.24.46.19?

Best, /nm





Michael Hunger

unread,
Jan 8, 2015, 9:16:21 AM1/8/15
to ne...@googlegroups.com
Can you check your /etc/hosts and/or your network interfaces

Somehow that address seems to be returned as localhost for the shell.

Otherwise please check that enable_remote_shell=true is set in conf/neo4j.properties

Cheers, Michael

--
You received this message because you are subscribed to the Google Groups "Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Normen Müller

unread,
Jan 8, 2015, 9:25:24 AM1/8/15
to ne...@googlegroups.com
Hi Michael,

first of all thanks for your answer! As to the latest group announcement (http://goo.gl/duFxTb) I re-posted my question at http://goo.gl/LI18ao.

Do we want to proceed there?

Anyway, here is my `/etc/hosts`:

$ cat /etc/hosts

##

# Host Database

#

# localhost is used to configure the loopback interface

# when the system is booting.  Do not change this entry.

##

127.0.0.1 localhost

255.255.255.255 broadcasthost

::1             localhost


Nothing special.

And my network configuration:

$ ifconfig 

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

options=3<RXCSUM,TXCSUM>

inet6 ::1 prefixlen 128 

inet 127.0.0.1 netmask 0xff000000 

inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 

nd6 options=1<PERFORMNUD>

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

stf0: flags=0<> mtu 1280

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

ether 3c:15:c2:c6:a3:fc 

inet6 fe80::3e15:c2ff:fec6:a3fc%en0 prefixlen 64 scopeid 0x5 

inet 172.24.46.15 netmask 0xfffffe00 broadcast 172.24.47.255

nd6 options=1<PERFORMNUD>

media: autoselect

status: active

en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=60<TSO4,TSO6>

ether 72:00:03:8f:85:80 

media: autoselect <full-duplex>

status: inactive

en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500

options=60<TSO4,TSO6>

ether 72:00:03:8f:85:81 

media: autoselect <full-duplex>

status: inactive

bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=63<RXCSUM,TXCSUM,TSO4,TSO6>

ether 02:24:9b:40:2d:00 

Configuration:

id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0

maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200

root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0

ipfilter disabled flags 0x2

member: en1 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 6 priority 0 path cost 0

member: en2 flags=3<LEARNING,DISCOVER>

        ifmaxaddr 0 port 7 priority 0 path cost 0

nd6 options=1<PERFORMNUD>

media: <unknown type>

status: inactive

p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304

ether 0e:15:c2:c6:a3:fc 

media: autoselect

status: inactive

awdl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1452

ether aa:f5:c3:ff:62:34 

inet6 fe80::a8f5:c3ff:feff:6234%awdl0 prefixlen 64 scopeid 0xa 

nd6 options=1<PERFORMNUD>

media: autoselect

status: active

en4: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500

options=23<RXCSUM,TXCSUM,TSO4>

ether 00:24:9b:04:5b:98 

inet6 fe80::224:9bff:fe04:5b98%en4 prefixlen 64 scopeid 0x4 

inet 172.24.36.1 netmask 0xfffffe00 broadcast 172.24.37.255

nd6 options=1<PERFORMNUD>

media: autoselect (100baseTX <full-duplex,flow-control>)

status: active


Any further suggestions?

Normen Müller

unread,
Jan 8, 2015, 9:44:45 AM1/8/15
to ne...@googlegroups.com
I also tried to enable the remote shell but again without any success (cf. http://goo.gl/LI18ao).
Reply all
Reply to author
Forward
0 new messages