Description
In the nginx logs, you’ll typically see an error similar to:
nginx: [emerg] host not found in upstream "minio-data:9500" in /etc/nginx/conf.d/default.conf:20Cause
On S3-based systems, the internal minio-data containers are not running, and nginx should be updated to reference the minio-internal endpoints instead.
The patching logic was not included in the v1.5.1 upgrade workflow. As a result, nginx continues to reference containers which don’t exist in S3 deployments, hence nginx fails to start with a missing-host error.
Workaround
To resolve the issue manually, you can patch the Image Artist 1.5.1 nginx configuration using the following steps:
-
Undeploy the Image Artist stack
Refer to: Image Artist: How do I redeploy/restart the container stack?
-
Navigate to the
ImA‑1.5.1installation directory, then run all four commands below:sed -i 's\ server minio-data:9500; # minio-data\ server minio-internal:9000; # minio-data\g' config/nginx_gemma sed -i 's\ server minio-data:9501; # minio-data\ server minio-internal:9001; # minio-data\g' config/nginx_gemma sed -i 's\ server minio-data:9500; # minio-data\ server minio-internal:9000; # minio-data\g' nginx/columbus.conf sed -i 's\ server minio-data:9501; # minio-data\ server minio-internal:9001; # minio-data\g' nginx/columbus.conf
-
Redeploy the Image Artist stack
Refer to: Image Artist: How do I redeploy/restart the container stack?
Once these changes are applied, nginx should start normally and the system will operate correctly with S3 storage.
Comments
0 comments
Please sign in to leave a comment.