Skip to main content

Troubleshoot

Start with what reached Neo4j. In the Neo4j Browser:

CALL db.labels() YIELD label RETURN collect(label)

Nothing is recorded​

No Execution label at all.

  • The run configuration does not point at the location. In Hop GUI, open the run configuration the run used: Execution information location must be putki-neo4j. The installer only sets it on run configurations that had no location, local or local-audit.
  • Hop cannot reach Neo4j. The run's log shows Error registering execution or Unable to connect. The host and port are NEO4J_HOSTNAME and NEO4J_PORT in the environment file the run used. Hop in a container: localhost is the container itself; use the Neo4j service's name on a shared Docker network.
  • The run had no environment. The connection's settings are variables from the environment file. Run with the environment selected (-e with hop-run).

Executions, but no Workflow or Pipeline nodes​

The execution graph needs the variable HOP_GRAPH_LOGGING_CONNECTION=neo4j when the run starts:

  • In the project's environment file. The installer puts it there, and it applies only when the run uses that environment.
  • Not in hop-config.json with an empty value. Hop declares this variable with an empty value in its hop-config.json, and a value there wins over an operating system environment variable or a -D option of the same name. Setting HOP_GRAPH_LOGGING_CONNECTION in a container's environment therefore has no effect. Use the environment file, or set the value in hop-config.json itself (hop-conf.sh -sv HOP_GRAPH_LOGGING_CONNECTION=neo4j).

Runs end with "A serious error occurred" and many NullPointerExceptions​

The execution information location could not connect when the run started, usually an unresolved variable such as ${NEO4J_PASSWORD} because the run had no environment, and every later step reports it. Fix the connection as above.

The Neo4j Browser opens but cannot connect​

The Browser connects to the Bolt address Neo4j advertises, NEO4J_BOLT_ADVERTISED (localhost:7687). If you changed NEO4J_BOLT_PORT or reach the server under another name, set it to match and run docker compose -f docker-compose-neo4j.yml up -d.

Asking for help​

Send these to Putki support, with passwords removed:

cat VERSION; docker compose version
docker compose -f docker-compose-neo4j.yml ps -a
docker compose -f docker-compose-neo4j.yml logs neo4j --tail 100

and the Hop log of a run that should have been recorded.