Python crashes when running role about ansible-node-exporter HOT 9 CLOSED

I was able to resolve this by exporting the OBJC_DISABLE_INITIALIZE_FORK_SAFETY variable to YES.

Via ansible/ansible#31869 (comment).

from ansible-node-exporter.

Sure! I use node_exporter to monitor the hosts in my home lab. I'm starting to migrate over to Ansible as a configuration management tool and wanted to avoid re-inventing the wheel, so I came across this role.

from ansible-node-exporter.

Great to see that you solved it! Out of curiosity, may I ask what are you using this role for?

from ansible-node-exporter.

Updated: Running the export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES command on my local machine before running the ansible-playbook fixes this.

I'm seeing similar results on Ubuntu 16 LTS:

[..]
TASK [node-exporter : Gather variables for each operating system] ****************************************************************************************
ok: [x.x.x.x] => (item=/Users/[..]/vendor/roles/node-exporter/vars/debian.yml)

TASK [node-exporter : Naive assertion of proper listen address] ******************************************************************************************
ok: [x.x.x.x] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [node-exporter : Fail on unsupported init systems] **************************************************************************************************
skipping: [x.x.x.x]

TASK [node-exporter : Check collectors] ******************************************************************************************************************

TASK [node-exporter : Get checksum list from github] *****************************************************************************************************
objc[69118]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[69118]: +[__NSPlaceholderDate 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.

from ansible-node-exporter.

@lekkerduidelijk this looks like some ansible or python related issue. There is a similar issue in ansible: ansible/ansible#32499

from ansible-node-exporter.

@paulfantom Yeah, also setting the env variable feels a bit 'hacky' to me.

One thing I discovered later on, is that the ansible-node-exporter playbook runs commands on localhost. Like unzip, untar etc. I'm accustomed to those commands being run on the remote host, so I needed to install some stuff locally first. Like brew install gnu-tar.

from ansible-node-exporter.

Yes, we run those commands to speed up deployment with large number of target hosts and all requirements should be specified in readme, but somehow I see no gnu-tar so this should be fixed.

from ansible-node-exporter.

Ok, makes sense. 👍

When running the playbook with the ENV in place I got:

Make sure the required command to extract the file is installed. Command "/usr/bin/tar" detected as tar type bsd. GNU tar required. Command "/usr/bin/unzip" could not handle archive.

The binaries for /usr/bin/tar and /usr/bin/unzip both existed. This is on MacOS Mojave 10.14.
Adding gnu-tar fixed it for me.

Also, I forgot to mention: thanks for your great work on the Ansible playbooks for the Prometheus stack. Huge time savers! 😎

from ansible-node-exporter.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

from ansible-node-exporter.