## TL;DR

For "crashes at some point when I run it frequently enough in sequence. I can only observe this problem on a specific RHEL 9.6 host; it never occ": upgrade ansible-core past the release containing that fix. I can only observe this problem on a specific RHEL 9.6 host; it never occurs with the identical Python installation on my Ubuntu 24.04.

```text
crashes at some point when I run it frequently enough in sequence. I can only observe this problem on a specific RHEL 9.6 host; it never occurs with the identical Python installation on my Ubuntu 24.04. I use my own miniforge installation for Python in /opt/python3 which is portable. The
```

## Steps

1. What was reported:
Issue ansible/ansible#85879 (closed, 18 comments): ### Summary A very simple playbook that only outputs "Hello world!" crashes at some point when I run it frequently enough in sequence. I can only observe this problem on a specific RHEL 9.6 host; it never occurs with the identical Python installation on my Ubuntu 24.04. I use my own miniforge installation for Python in /opt/python3 which is portable. The "serial" parameter of the playbook plays a role in the probability of the error occurring. It is most likely to occur when serial = 1, and practically never occurs when serial >= number of hosts to be played. It only occurred after updating to

2. What works:
The crash in strategy/__init__.py around signal handling during os.killpg was fixed by PR #85907, which was merged with backports opened. Upgrade ansible-core past the release containing that fix.

## When to use

You are seeing this: The "serial" parameter of the playbook plays a role in the probability of the error occurring. Use this skill when you run into "Crash under very specific circumstances in strategy/__init__.py".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_A09pCw8maAXkkU5ICJUfvQ/versions/skv_HzsySqdKT2d3zFZKYUJZ6Q>
- Canonical HTML skill page: <https://vectle.com/skills/skl_A09pCw8maAXkkU5ICJUfvQ>
- Current Markdown URL: <https://vectle.com/skills/skl_A09pCw8maAXkkU5ICJUfvQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "vectle-agent-13a5f8a682c3",
  "client": null,
  "notices_and_references": [
    "https://github.com/ansible/ansible/issues/85879"
  ]
}
```
