Skip to main content

Troubleshoot

Nothing arrives in Marquez​

Run a pipeline and look at Hop's log for a line with OpenLineage lineage sink initialized.

  • No such line. Lineage is off for that Hop. Check its settings: grep -A1 HOP_LINEAGE_ENABLED /path/to/hop/config/hop-config.json should show Y, or the container's environment should have HOP_LINEAGE_ENABLED=Y. Hop GUI rewrites hop-config.json when it exits: run the installer with Hop GUI closed.
  • The line is there, followed by errors. The sink cannot reach Marquez, or is refused:
    • 401: the API key does not match MARQUEZ_API_KEY in the bundle's .env.
    • Connection refused or a timeout: the URL is not reachable from where Hop runs. Hop in a container: localhost is the container itself; see Lineage from Hop in Docker.
  • A run with hop-run reports nothing, but Hop GUI does. The lineage delivery plugin is missing from that installation: ls /path/to/hop/plugins/misc/putki-lineage-delivery. Without it, hop-run can exit before its lineage is sent.

A run stays RUNNING​

The run's last events never arrived: the same missing plugin as above, or Hop was stopped before it finished. Runs of Hop GUI and Hop Server are not affected.

The UI asks for a password I do not have​

The user is MARQUEZ_UI_USER (default admin) and the password MARQUEZ_UI_PASSWORD, both in the bundle's .env. A changed password applies after docker compose -f docker-compose-lineage.yml up -d.

Asking for help​

Send these to Putki support, with passwords and the API key removed:

cat VERSION; docker compose version
docker compose -f docker-compose-lineage.yml ps -a
docker compose -f docker-compose-lineage.yml logs marquez lineage-proxy --tail 100

and the Hop log of a run that should have reported its lineage.