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.

demo

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!

• 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 only

export "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES"

• fix — for all future sessions

echo "OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES" >> .bash_profile