many zombie processes forked by st2actionrunner
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
many zombie processes forked by st2actionrunner
/opt/stackstorm/st2/bin/python /opt/stackstorm/st2/bin/st2actionrunner --config-file /etc/st2/st2.conf
root 16338 0.0 0.0 0 0 ? Zs Oct24 0:00 _ [sudo]
root 16343 0.0 0.0 0 0 ? Zs Oct24 0:00 _ [sudo]
root 16362 0.0 0.0 0 0 ? Zs Oct24 0:00 _ [sudo]
STACKSTORM VERSION
2.6.0
run in kubernetes, the start command is '/opt/stackstorm/st2/bin/python /opt/stackstorm/st2/bin/st2actionrunner --config-file /etc/st2/st2.conf'
Steps to reproduce the problem
I do not how to show how to reproduce the problem;
But the actionrunner has many failed task:
| + 660345606d32900001909d4c | email.mistral-network-check | admin@example.org | failed (2130s elapsed) | Tue, 26 Mar 2024 22:00:00 | Tue, 26 Mar 2024 22:03:33 UTC |
| | | | | UTC | |
| + 66034d716d32900001909d56 | email.mistral-network-check | admin@example.org | failed (3800s elapsed) | Tue, 26 Mar 2024 22:34:25 | Tue, 26 Mar 2024 22:35:03 UTC |
| | | | | UTC | |
| + 66035b816d32900001909d5f | email.mistral-network-check | admin@example.org | failed (3800s elapsed) | Tue, 26 Mar 2024 23:34:25 | Tue, 26 Mar 2024 23:35:03 UTC |
| | | | | UTC | |
| + 660369916d32900001909d68 | email.mistral-network-check | admin@example.org | failed (4200s elapsed) | Wed, 27 Mar 2024 00:34:25 | Wed, 27 Mar 2024 00:35:07 UTC |
| | | | | UTC | |
| + 660377a16d32900001909d71 | email.mistral-network-check | admin@example.org | failed (4400s elapsed) | Wed, 27 Mar 2024 01:34:25 | Wed, 27 Mar 2024 01:35:09 UTC |
| | | | | UTC | |
| + 660385b16d32900001909d7a | email.mistral-network-check | admin@example.org | failed (4200s elapsed) | Wed, 27 Mar 2024 02:34:25 | Wed, 27 Mar 2024 02:35:07 UTC |
| | | | | UTC | |
+----------------------------+------------------------------+-------------------+--------------------------+------------------------------+-------------------------------+
Expected Results
no zombie processes
Actual Results
What happened? What output did you get?
has many zombie processes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the st2actionrunner entry point invoked by /opt/stackstorm/st2/bin/python in the reported Kubernetes setup, and review how it handles the listed failed tasks. Reproduce or inspect the runner under the reported conditions; done means failed actions no longer leave zombie [sudo] processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100