Hey guys I am getting this error running meltano e...
# announcements
h
Hey guys I am getting this error running meltano elt through the cli. I am using
tap-facebook
and
target-postgres
Copy code
Traceback (most recent call last):
  File "/project/.venv/meltano/bin/meltano", line 8, in <module>
    sys.exit(main())
  File "/project/.venv/meltano/lib/python3.7/site-packages/meltano/cli/__init__.py", line 38, in main
    cli(obj={"project": None})
  File "/project/.venv/meltano/lib/python3.7/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/project/.venv/meltano/lib/python3.7/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/project/.venv/meltano/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/project/.venv/meltano/lib/python3.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/project/.venv/meltano/lib/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/project/.venv/meltano/lib/python3.7/site-packages/meltano/cli/params.py", line 23, in decorate
    return func(*args, **kwargs)
  File "/project/.venv/meltano/lib/python3.7/site-packages/meltano/cli/params.py", line 50, in decorate
    project, settings_service.get("database_uri"), default=True
  File "/project/.venv/meltano/lib/python3.7/site-packages/meltano/core/db.py", line 35, in project_engine
    raise ValueError("No engine registered for this project.")
ValueError: No engine registered for this project.
I saw that this issue was fixed a while ago here so I am confused on why it is happening now. Any help would be appreciated
d
This suggests that the
database_uri
setting (https://meltano.com/docs/settings.html#database-uri) is set to
None
, could that be? What current value and source do you see listed for that setting when you run
meltano config meltano list
?
h
I figured it out, thanks for the response! It was because the variable in my instance were not being read properly and had to run as root.