Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checksuming fails #49

Open
tuxpeople opened this issue Nov 11, 2020 · 3 comments
Open

Checksuming fails #49

tuxpeople opened this issue Nov 11, 2020 · 3 comments

Comments

@tuxpeople
Copy link

It get killed while trying to get the checksums for server and client:

TASK [atosatto.minio : Get the Minio server checksum for amd64 architecture] ***********************************
objc[27057]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[27057]: +[__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.
ERROR! A worker was found in a dead state
TASK [atosatto.minio : Get the Minio client checksum for amd64 architecture] **********************************************************************************************************************************
objc[27916]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[27916]: +[__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.
ERROR! A worker was found in a dead state

@hadret
Copy link

hadret commented Nov 19, 2020

This doesn’t look like Ansible but rather Python error. Can you try to export the following and try again?

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

@lksnmnn
Copy link

lksnmnn commented Mar 3, 2021

I encountered this as well. Seems to be an issue with Ansible: ansible/ansible#49207

@tuxpeople
Copy link
Author

This doesn’t look like Ansible but rather Python error. Can you try to export the following and try again?

export OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES

Long time no see (I'm sorry!). Problem still exists, but the export helps. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants