Ansible troubleshooting - macOS fork error
How to troubleshoot and fix the macOS fork error that might happen since macOS 10.13 High Sierra.
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.
The best way of talking about Ansible troubleshooting is to jump in a live demo to show you practically the macOS fork error and how to solve it!
objc: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. objc: +[__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
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
code with ❤️ in GitHub
Now you know better how to troubleshoot the macOS fork error and how to fix it. Subscribe to the YouTube channel, Medium, Website and Twitter to not miss the next episode of the Ansible Pilot.
Learn the Ansible automation technology with some real-life examples in my
My book Ansible By Examples: 100+ Automation Examples For Linux and Windows System Administrator and DevOps
Want to keep this project going? Please donate