bolt unavailable when changing dbms.mode from SINGLE to CORE

[Desotho]

Hello,

i am checking out Neo4j and i want to apologize in advance because this issue might quite stupid. But actually i have no clue to solve it.

I want to check a setup of 3 core servers, but as soon i change dbms.mode=SINGLE to dbms.mode=CORE bolt seems to be unavailable anymore.

dbms.mode=CORE
netstat -tuplen | grep "java"
tcp6       0      0 10.76.104.38:6000       :::*                    LISTEN      0          3261673    416009/java         
tcp6       0      0 10.76.104.38:7000       :::*                    LISTEN      0          3261662    416009/java         
tcp6       0      0 127.0.0.1:6362          :::*                    LISTEN      0          3261674    416009/java         
tcp6       0      0 10.76.104.38:5000       :::*                    LISTEN      0          3262793    416009/java   

dbms.mode=SINGLE
netstat -tuplen | grep "java"
tcp6       0      0 10.76.104.38:7474       :::*                    LISTEN      0          3271451    417484/java         
tcp6       0      0 127.0.0.1:6362          :::*                    LISTEN      0          3271283    417484/java         
tcp6       0      0 10.76.104.38:7687       :::*                    LISTEN      0          3271290    417484/java   

root@dba253a:/opt/neo4j/conf# /opt/neo4j/bin/cypher-shell -a neo4j://10.76.104.38:7687
username: neo4j
password: *****************
Connected to Neo4j using Bolt protocol version 4.4 at neo4j://10.76.104.38:7687 as user neo4j.
Type :help for a list of available commands or :exit to exit the shell.
Note that Cypher queries must end with a semicolon.

[michael_hunger]

Perhaps because the cluster is not yet formed and so the database is not ready to process queries?

Did you check in your debug.log if there are any cluster formation issues?

[Desotho]

Thank you very much for your help. There was indeed a firewall issue and therefore the cluster could not be formed.
After solving this bolt became available.

root@dba253c:/opt/neo4j/logs# netstat -tuplen | grep "java"
tcp6       0      0 10.76.104.67:7687       :::*                    LISTEN      0          505354     110415/java         
tcp6       0      0 10.76.104.67:5000       :::*                    LISTEN      0          505280     110415/java         
tcp6       0      0 10.76.104.67:6000       :::*                    LISTEN      0          505293     110415/java         
tcp6       0      0 10.76.104.67:7474       :::*                    LISTEN      0          505355     110415/java         
tcp6       0      0 10.76.104.67:7000       :::*                    LISTEN      0          505283     110415/java         
tcp6       0      0 127.0.0.1:6362          :::*                    LISTEN      0          505294     110415/java