Stacks always show as unhealthy even though services are running fine #387

Closed
opened 2025-10-31 15:10:29 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @NikoKS on GitHub (May 26, 2025).

Stacks shows as unhealthy even though all services are running fine. I'm guessing it's because some services are exited?

Image

But the exited services are intentionally set up container and are exited after they've run the script.

How do I make it healthy?

Originally created by @NikoKS on GitHub (May 26, 2025). Stacks shows as unhealthy even though all services are running fine. I'm guessing it's because some services are exited? <img width="296" alt="Image" src="https://github.com/user-attachments/assets/317cb736-616f-4eba-98e0-66ac428517ea" /> But the exited services are intentionally set up container and are exited after they've run the script. How do I make it healthy?
Author
Owner

@b- commented on GitHub (May 26, 2025):

Stacks shows as unhealthy even though all services are running fine. I'm guessing it's because some services are exited?

Image But the exited services are intentionally set up container and are exited after they've run the script.

How do I make it healthy?

Stacks -> Scroll down to ADVANCED -> scroll a little further to Ignore Services and add a list of services that normally exit.
Image

Note: this will make Komodo completely ignore the status of those services when you look at the stack health. They'll still be deployed, though.

@b- commented on GitHub (May 26, 2025): > Stacks shows as unhealthy even though all services are running fine. I'm guessing it's because some services are exited? > > <img alt="Image" width="296" src="https://private-user-images.githubusercontent.com/24285511/447598679-317cb736-616f-4eba-98e0-66ac428517ea.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDgzMDI4MzEsIm5iZiI6MTc0ODMwMjUzMSwicGF0aCI6Ii8yNDI4NTUxMS80NDc1OTg2NzktMzE3Y2I3MzYtNjE2Zi00ZWJhLTk4ZTAtNjZhYzQyODUxN2VhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA1MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNTI2VDIzMzUzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQxZTU3NzlhZmVmYTc3ZGUyYzg0NjFlMTQyYzViNGE2MzEwOTMyMmVhMDA2N2E5NzBkZWE5YmNiN2UzMzA5MWQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.zeBgd0NSQQGsxcj8U-WocwkWgPkH6MweFvciwuw1AkM"> > But the exited services are intentionally set up container and are exited after they've run the script. > > How do I make it healthy? Stacks -> Scroll down to __ADVANCED__ -> scroll a little further to _Ignore Services_ and add a list of services that normally exit. ![Image](https://github.com/user-attachments/assets/db873a89-5590-47c4-839a-ad2c6f49fe03) Note: this will make Komodo completely ignore the status of those services when you look at the stack health. They'll still be deployed, though.
Author
Owner

@NikoKS commented on GitHub (May 27, 2025):

Hey, that works! Thank you.

@NikoKS commented on GitHub (May 27, 2025): Hey, that works! Thank you.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#387