cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

Google searches seem dated.. my neo4j browser now on 7687

guys .. is db/data default ? for sucking in mongo

mongo-connector -m localhost:27017 -t http://localhost:7687/db/data -d neo4j_doc_manager
Logging to /home/leveridge/mongo-connector.log.

my neo browser is showing that port 7687 and i disabled auth in neo4j conf file. ie to false. still not joy in connecting mongo-connector. any clues ? thanks a million BTC!

2020-10-22 08:38:56,676 [ALWAYS] mongo_connector.connector:50 - pymongo version: 3.11.0
2020-10-22 08:38:56,685 [ALWAYS] mongo_connector.connector:50 - Source MongoDB version: 4.4.1
2020-10-22 08:38:56,685 [ALWAYS] mongo_connector.connector:50 - Target DocManager: mongo_connector.doc_managers.neo4j_doc_manager version: unknown
2020-10-22 08:38:56,716 [ERROR] httpstream:168 - ! SocketError: Remote end closed connection without response
2020-10-22 08:38:56,716 [CRITICAL] mongo_connector.oplog_manager:714 - Exception during collection dump
Traceback (most recent call last):
File "/home/leveridge/.local/lib/python3.6/site-packages/py2neo/packages/httpstream/http.py", line 322, in submit
response = send()
File "/home/leveridge/.local/lib/python3.6/site-packages/py2neo/packages/httpstream/http.py", line 318, in send
return http.getresponse(**getresponse_args)
File "/usr/lib/python3.6/http/client.py", line 1373, in getresponse
response.begin()
File "/usr/lib/python3.6/http/client.py", line 311, in begin
version, status, reason = self._read_status()
File "/usr/lib/python3.6/http/client.py", line 280, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

During handling of the above exception, another exception occurred:

3 REPLIES 3

Regarding the port question.

7474 is the default http (web browser) port, and 7687 is the default BOLT port.
To see where your db ports are you can ask the database (assuming you have admin role)

call dbms.listConfig() yield name,value 
WHERE name contains 'connector' 
return name,value

which on default ports will look something like this (the part after the : colon is the port information we are after)

╒════════════════════════════════════════════╤══════════════════════════════════╕
│"name"                                      │"value"                           │
╞════════════════════════════════════════════╪══════════════════════════════════╡
│"dbms.connector.bolt.address"               │"0.0.0.0:7687"                    │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.bolt.advertised_address"    │"asdf.com:7687"│
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.bolt.enabled"               │"true"                            │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.bolt.listen_address"        │"0.0.0.0:7687"                    │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.http.address"               │"0.0.0.0:7474"                    │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.http.enabled"               │"true"                            │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.http.listen_address"        │"0.0.0.0:7474"                    │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.https.enabled"              │"true"                            │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connector.https.listen_address"       │"0.0.0.0:7473"                    │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connectors.default_advertised_address"│"localhost"                       │
├────────────────────────────────────────────┼──────────────────────────────────┤
│"dbms.connectors.default_listen_address"    │"0.0.0.0"                         │
└────────────────────────────────────────────┴──────────────────────────────────┘

Joel.. many many thanks 🙂 great info

now into the advanced compatibility tangle as my understandings have grown..

it seems the stack layers of this goal obviously get tangled

Do you know a compatible versioning ? I heard mongo 4.4 doesnt play well with connector 3.1.1 .. only mongo 3.6

and with py2neo into the mix as connector / doc manager was built with 2.0.7 as target .. now I'm messing with 5.something now !

sooooo... anyone you know or indeed yourself know / found a compatible versioning stack for our doc manager and all to be happy ?

mongodb
mongoconnector
docmanager
py2neo
neo4j

curr I am
4.4
3.1.1
1.0.0.dev11
5.0b1
4.1.1

and pymongo ver 3.11.0
I can do a pip3 list to get you the full list if that helps

in highly respective order

Oh and my env is ubuntu1804 and I have python 3.6.9 and I installed all the related stack that needed pip install.. with pip3 install which seemed to do the trick.. ie when i run mongo-connector.. before it falls.. it hits python3.6.9 in the trace .. so thats cool.

anyway the prob is probably the combo of versioning .. maybe my mongo4.4 is too much for doc manager ? ie no REST APIs maybe ?.. but basically I get connect issues from mongo connector.. when all else (except) versioning seems ok.. ie start sequence.. rep sets initated etc etc.. neo4j instance running etc.. browser is cool now thanks to your info 🙂 .. so yes is there an official/from the Ninjas 🙂 as stack version set that plays well ?

any thoughts sir or know anyone we can approach to confirm a happy combo ? else its a lotto game trying to hit the right combo for a neo4j newbie

adding link to your other post for reference, in case someone reads this post first..