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

OSX Catalina: 'cfn init' terminated by signal SIGABRT (Abort) #49

Closed
benbridts opened this issue Nov 20, 2019 · 3 comments
Closed

OSX Catalina: 'cfn init' terminated by signal SIGABRT (Abort) #49

benbridts opened this issue Nov 20, 2019 · 3 comments
Labels
documentation no fix planned For some issues, no fix is feasible. Please see issue itself for the discussion

Comments

@benbridts
Copy link
Contributor

I'm not sure if this belongs here, as it's an OSX Catalina / homebrew python issue. I assume people will look here when they run into this error, so maybe it's something to document.

If you run cfn init outside of a virtualernv on OSX Catalina with python3.7 (installed via homebrew), you get this behaviour and error:

~$: cfn init --verbose
Initializing new project
What's the name of your resource type?
(Organization::Service::Resource)
>> MyOrg::Foo::Bar
Select a language for code generation:
[1] python36
[2] python37
(enter an integer):
>> 2
fish: 'cfn init --verbose' terminated by signal SIGABRT (Abort)

Looking at the error report that is generated, this seems to be an issue related to pyhton3 and libcrypto:

Application Specific Information:
/usr/lib/libcrypto.dylib
abort() called
Invalid dylib load. Clients should not load the unversioned libcrypto dylib as it does not have a stable ABI.

I googled for a solution and I there is a clean workaround (besides running cfn in a virtualenv:

# Install openssl, if it's not installed already
brew install openssl
# Use the openssl libraries
DYLD_LIBRARY_PATH=/usr/local/opt/openssl/lib:$DYLD_LIBRARY_PATH cfn init
@tobywf
Copy link
Contributor

tobywf commented Nov 23, 2019

ouch, good trouble-shooting! doesn't seem like anything we can work around in the code, but definitely worth adding to the README

@tobywf tobywf pinned this issue Nov 23, 2019
@tobywf tobywf added the no fix planned For some issues, no fix is feasible. Please see issue itself for the discussion label Nov 25, 2019
@benkehoe
Copy link

Could this situation at least be detected and reported, so that the user knows what action to take?

@tobywf
Copy link
Contributor

tobywf commented Dec 19, 2019

none of us are running Catalina, so it's hard to reproduce and test. loads of people are hitting this though in all kinds of situations:

particularly, the first and last issue seem to indicate upgrading the asn1crypto package helped. problem is, we don't pull that in directly or indirectly. i assume this is why you don't hit this in a virtual environment. and hacking around broken system dependencies is a bit out of scope. it's unlikely we'll address this any further than pinning and keeping the issue open (for now).

@ammokhov ammokhov closed this as completed Oct 5, 2020
@ammokhov ammokhov unpinned this issue Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation no fix planned For some issues, no fix is feasible. Please see issue itself for the discussion
Projects
None yet
Development

No branches or pull requests

4 participants