# Getting fatal error cannot recover from stack overflow when running ansible core 2.11.12

**URL:** <https://forum.ansible.com/t/getting-fatal-error-cannot-recover-from-stack-overflow-when-running-ansible-core-2-11-12/3209>\
**Category:** Get Help\
**Created:** [January 8, 2024, 6:27pm UTC](https://forum.ansible.com/t/getting-fatal-error-cannot-recover-from-stack-overflow-when-running-ansible-core-2-11-12/3209 "2024-01-08T18:27:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Systemgeek-louis](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/systemgeek-louis/32/1938_2.png) [@Systemgeek-louis](https://forum.ansible.com/u/Systemgeek-louis)\
**Post date:** [January 8, 2024, 6:27pm UTC](https://forum.ansible.com/t/getting-fatal-error-cannot-recover-from-stack-overflow-when-running-ansible-core-2-11-12/3209/1 "2024-01-08T18:27:20Z")

</div>

I put ansible in debug and these are the last few lines I am seeing:

```auto
Read vars_file 'vars.yml'
 12999 1704737576.69532: done with get_vars()
 12999 1704737576.69540: in VariableManager get_vars()
 12999 1704737576.69557: Loading data from /etc/ansible/vars.yml
Read vars_file 'vars.yml'
 12999 1704737576.69573: done with get_vars()
Fatal Python error: Cannot recover from stack overflow.

```

There are 152 lines in my vars.yaml file but I have been running like this for well over a year with no issues. No we are seeing this message.

This is on Rocky 8 with python 3.6

Any one have any clue what ios going on or how to better debug things?

---

<div class="post-metadata">

**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\
**Post date:** [January 9, 2024, 1:59pm UTC](https://forum.ansible.com/t/getting-fatal-error-cannot-recover-from-stack-overflow-when-running-ansible-core-2-11-12/3209/2 "2024-01-09T13:59:54Z")

</div>

The debug messages about the vars\_file loading is probably not directly related to the issue, and there’s not enough info to guess. There’s recursion somewhere that’s exceeding Python’s internal stack depth, so it crashes. You might get a more relevant error if you reduce the stack depth [29.1. sys — System-specific parameters and functions — Python 3.6.15 documentation](https://docs.python.org/3.6/library/sys.html#sys.setrecursionlimit) so a RecursionError is raised instead.
