EXAMPLE ISSUE📢 Velocity errors when starting from Installer: continuous-release-ui, reporting-u unhealthy

[daniel-trow]

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.

[daniel-trow]

ANSWER

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

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

2. Re-run the installer, For Docker Compose Installations

   1. Go to the installation directory and run docker-compose up -d. Sometimes it requires multiple docker-compose up attempts to actually start up.
   2. 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.

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: EXAMPLE ISSUE📢 security-api won't start, container keeps restarting because access key/trial key invalid #8