Search

Your Notifications (0)

There are currently no notifications. You're all set!

Knowledge Base
ChemDraw and ChemOffice+ Products Signals Notebook E-Notebook and ChemBioOffice Enterprise Spotfire and Signals Spotfire Products Image Artist Spectrus, Percepta, Katalyst, Luminata and more
Downloads
Downloads
Community
Ideas Portal Product Basics
About Support
Legal Resources Support and Maintenance Plans Product Life Cycle Support News
Contact Support

Image Artist: Nginx Fails to Start After Upgrading to ImA v1.5.1 on Systems Using S3 Storage

Nicholas Wyatt
  • Updated

Description

After upgrading from ImA v1.5.0 to v1.5.1, systems that use S3-based storage may find that the nginx service does not start.

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:20
 
This issue only affects installations where internal MinIO data services are disabled because S3 is being used.
 

Cause

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:

  1. Undeploy the Image Artist stack

    Refer to: Image Artist: How do I redeploy/restart the container stack?

  2. Navigate to the ImA‑1.5.1 installation 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

  3. 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.

Related articles

Comments

0 comments

Please sign in to leave a comment.