Today we’re going to talk about Ansible troubleshooting and specifically about macOS fork errors. I’m Luca Berton and welcome to today’s episode of the Ansible Pilot.
Playbook
The best way of talking about Ansible troubleshooting is to jump in a live Playbook to show you practically the macOS fork error and how to solve it!
error
- error
objc[22868]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[22868]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
fix current session
- fix - current session only
export "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES"
fix all future sessions
- fix - for all future sessions
echo "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES" >> .bash_profile
You could verify the environment of the terminal with the following command:
$ env
[...]
OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES
Conclusion
Now you know better how to troubleshoot the macOS fork error and how to fix it. Subscribe to the YouTube channel, Medium, and Website, X (formerly Twitter) to not miss the next episode of the Ansible Pilot.
Academy
Learn the Ansible automation technology with some real-life examples in my
Udemy 300+ Lessons Video Course.
My book Ansible By Examples: 200+ Automation Examples For Linux and Windows System Administrator and DevOps
Donate
Want to keep this project going? Please donate