Skip to content

Latest commit

 

History

History
46 lines (28 loc) · 2.36 KB

FAQ.md

File metadata and controls

46 lines (28 loc) · 2.36 KB

1. Velocity errors when starting from Installer: continuous-release-ui, reporting-u unhealthy

Receiving this error when trying to start Velocity from installer...

? Do you want to start Velocity now?[Y,n] Yes { Error: Command failed: docker-compose up -d --remove-orphans velocity_database_1 is up-to-date velocity_rabbitnode1_1 is up-to-date velocity_rcl-web-client_1 is up-to-date velocity_reporting-sync-api_1 is up-to-date velocity_reporting-consumer_1 is up-to-date velocity_continuous-release-consumer_1 is up-to-date velocity_security-api_1 is up-to-date velocity_application-api_1 is up-to-date velocity_continuous-release-poller_1 is up-to-date ERROR: for continuous-release-ui Container "6eb6f5cf843f" is unhealthy. ERROR: for reporting-ui Container "6eb6f5cf843f" is unhealthy.

ANSWER

This could have multiple root causes, here is some troubleshooting...

  1. Make sure your machine and containerization platform have enough resources.

  2. Try running the installer again.

  3. If "continuous-release-ui" and "reporting-ui " are unhealthy, it might be due to an issue with security-api. Check security-api health/logs to diagnose.

    1. Known security-api issues with this symptom: #8

Docker Compose

  • Go to the installation directory and run docker-compose up -d. Sometimes it requires multiple times to actually start up.

  • If that doesn't work, run docker-compose ps to see which containers aren't healthy, then get the logs of those containers that are not healthy.

2. security-api won't start and the container keeps restarting because it says the access or trial key is not valid.

ANSWER

A valid access or trial key is required to start security-api. This key can be provided as an environmental variable or through the database. The Velocity installer checks the validity of a key before installing, so that Velocity will only be configured with valid keys. Between the database and environmental variable keys, at least one must be valid. It is possible to not yet have a valid key in the database and for an invalid access or trial key to be introduced through an environmental variable that overrides the default configuration and prevents security-api from starting.