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

Problem: Zombie processes on host after in update 2.9.109 #2069

Closed
guyke01 opened this issue May 29, 2024 · 2 comments
Closed

Problem: Zombie processes on host after in update 2.9.109 #2069

guyke01 opened this issue May 29, 2024 · 2 comments
Assignees

Comments

@guyke01
Copy link

guyke01 commented May 29, 2024

Issue

Since update 2.9.109 i see a lot of zombie processes on the Ubuntu host form SSH after running a playbook. It seems that the proces is not exiting after completing a runbook.

In the previous version 2.9.75 this behavior was not occuring. The logs provided are the zombie processes after running a playbook. After restarting the semaphore container the zombie processes are killed.

Impact

Ansible (task execution)

Installation method

Docker

Database

MySQL

Browser

Microsoft Edge

Semaphore Version

2.9.109

Ansible Version

N/A. Docker installation.

Logs & errors

id ansible
uid=1001(ansible) gid=1001(ansible) groups=1001(ansible)
docker inspect $(docker ps -q) --format '{{.Config.User}} {{.Name}}'
1001 /semaphore_server
 /semaphore_db
ansible     46284  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46284  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46285  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46286  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46287  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46289  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46290  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46291  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46292  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46294  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46295  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46296  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46297  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46299  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46300  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46301  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46302  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46304  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46305  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
ansible     46306  0.0  0.0      0     0 ?        Zs   18:00   0:00 [ssh] <defunct>
ansible     46307  0.0  0.0      0     0 ?        Z    18:00   0:00 [ssh] <defunct>
pstree -p -s 46307
systemd(1)───containerd-shim(34474)───semaphore(34520)───ssh(46307)
docker compose restart
[+] Restarting 2/2
 ✔ Container semaphore_server  Started                                                                                                                              0.5s 
 ✔ Container semaphore_db      Started                                                                                                                              2.0s
ps aux | grep 'Z'
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root       51865  0.0  0.1   6480  2280 pts/0    S+   21:47   0:00 grep --color=auto Z

Manual installation - system information

No response

Configuration

No response

Additional information

No response

@tboerger
Copy link
Collaborator

Potentially because tini have been removed. Tini prevents zombie processes.

@fiftin fiftin added the bug label May 29, 2024
@fiftin
Copy link
Collaborator

fiftin commented May 29, 2024

Hi @guyke01 , @tboerger I reproduces the issue. Yes, it is true, tini kills zombies. Will be returned in next release (ASAP).

@fiftin fiftin self-assigned this May 29, 2024
truecharts-admin added a commit to truecharts/charts that referenced this issue May 30, 2024
…@05c9a6f by renovate (#22652)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [semaphoreui/semaphore](https://togithub.com/semaphoreui/semaphore) |
patch | `v2.9.75` -> `v2.9.112` |

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>semaphoreui/semaphore (semaphoreui/semaphore)</summary>

###
[`v2.9.112`](https://togithub.com/semaphoreui/semaphore/releases/tag/v2.9.112)

[Compare
Source](https://togithub.com/semaphoreui/semaphore/compare/v2.9.75...v2.9.112)

#### Bugfixes

- Docker: Fixed zombie processes
[semaphoreui/semaphore#2069
- Docker: Moved Python venv from `~/venv` to `/opt/semaphore/venv` to
fix issue
[semaphoreui/semaphore#2060
- Docker: LDAP issue
[semaphoreui/semaphore#2063
-   UI: Remove extra close button in Template dialog

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4zODIuMCIsInVwZGF0ZWRJblZlciI6IjM3LjM4Mi4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbImF1dG9tZXJnZSIsInVwZGF0ZS9kb2NrZXIvZ2VuZXJhbC9ub24tbWFqb3IiXX0=-->
@fiftin fiftin closed this as completed May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants