Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: deployments running endlessly #4740

Open
ton77v opened this issue Jan 5, 2025 · 1 comment
Open

[Bug]: deployments running endlessly #4740

ton77v opened this issue Jan 5, 2025 · 1 comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@ton77v
Copy link

ton77v commented Jan 5, 2025

Error Message and Logs

Yesterday I've found that all the deployments (repo- and docker-based) are queued for hours while nothing happens. I've checked the deployments logs and found out that a few days ago one of the deployments just hung after the success e.g.:

2024-Dec-31 05:23:41.358199
Starting pull request (#133) deployment of XXX:main.
...
2024-Dec-31 05:40:36.757449
time="2024-12-31T05:40:36Z" level=warning msg="Found orphan containers ([wgwosgg-041140314269 wgwosgg-pr-132]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
2024-Dec-31 05:40:36.775610
Container wgwosgg-pr-133  Creating
2024-Dec-31 05:40:36.856169
wgwosgg-pr-133 Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.
2024-Dec-31 05:40:36.874800
Container wgwosgg-pr-133  Created
2024-Dec-31 05:40:36.874800
 Container wgwosgg-pr-133  Starting
2024-Dec-31 05:40:37.154697
Container wgwosgg-pr-133  Started
2024-Dec-31 05:40:37.170425
New container started.

^^^^^^^^^^^^^^ however it was shown as "running for XXX,XXX seconds; the only unusual thing there were the orphans; I've checked they seem to appear the same day

The "Logs" tab, indeed, had two "ghost" PR deployments that were actually closed Dec 31th

There were a couple of other deployments also running for "2 days", "4 days", a couple of successful ones and the rest was just hanging in "queued".

While in the UI I've also noted this message frequently pops: #4309 however I've seen it before

Steps to Reproduce

Unfortunately I've noticed the issue a few days after and can't see what exactly caused that. Orphan containers... ?

Canceling all the pending deployments, stopping the "ghost" containers, running docker prune and restarting the services solved the issue

Example Repository URL

No response

Coolify Version

v4.0.0-beta.380

Are you using Coolify Cloud?

Yes (Coolify Cloud)

Operating System and Version (self-hosted)

No response

Additional Information

No response

@ton77v ton77v added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 5, 2025
@blk-raffy
Copy link

Hi, this is a duplicate:
#4641 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants