Not able to use the start-up script `marquez-api exited with code 134`
xanterx opened this issue · 3 comments
xanterx commented
While using the ./docker/up.sh --seed
command as mentioned in the quickstart docs. marquez-api is not getting started and erroring out after some blank logs with code 134
marquez-api | WARNING 'MARQUEZ_CONFIG' not set, using development configuration.
marquez-api | INFO [2024-08-31 16:22:32,952] org.eclipse.jetty.util.log: Logging initialized @9509ms to org.eclipse.jetty.util.log.Slf4jLog
marquez-api | INFO [2024-08-31 16:22:33,430] io.dropwizard.server.DefaultServerFactory: Registering jersey handler with root path prefix: /
marquez-api | INFO [2024-08-31 16:22:33,437] io.dropwizard.server.DefaultServerFactory: Registering admin handler with root path prefix: /
marquez-api | INFO [2024-08-31 16:22:33,440] io.dropwizard.assets.AssetsBundle: Registering AssetBundle with name: graphql-playground for path /graphql-playground/*
marquez-api | INFO [2024-08-31 16:22:33,489] marquez.MarquezApp: Running startup actions...
marquez-api | INFO [2024-08-31 16:22:33,633] org.flywaydb.core.internal.license.VersionPrinter: Flyway Community Edition 8.5.13 by Redgate
marquez-api | INFO [2024-08-31 16:22:33,634] org.flywaydb.core.internal.license.VersionPrinter: See what's new here: https://flywaydb.org/documentation/learnmore/releaseNotes#8.5.13
marquez-api | INFO [2024-08-31 16:22:33,634] org.flywaydb.core.internal.license.VersionPrinter:
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api |
marquez-api | [Too many errors, abort]
marquez-api | /usr/src/app/entrypoint.sh: line 19: 100 Aborted (core dumped) java ${JAVA_OPTS} -jar marquez-*.jar server ${MARQUEZ_CONFIG}
marquez-api exited with code 134
boring-cyborg commented
Thanks for opening your first issue in the Marquez project! Please be sure to follow the issue template!
phixMe commented
Hmm, I tried this myself and it seems to work ok. Are you running on a windows platform? We have some setup instructions for that setup here.
Alternatively, you can use the ./docker/up.sh --build --seed
command to build from source directly as an alternative.
xanterx commented
Was facing this on
- MAC OS 14.6.1
- Apple M1 chip (ARM)
- Rancher Desktop with dockerd(moby) container engine
I did some hit and trial. And able to resolve it by following steps on Rancher Desktop.
- Enabling
VZ
experimental emulation and Enable Rosetta support option for that.