libcrypto.so.1.1: cannot open shared object file: No such file or directory

Open
#15 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
aws, elixir
Domain
cloud

Research direction

Start by inspecting how the repository packages its crypto library and reproduce the hello_world startup failure under OTP 26. Trace why the runtime requests libcrypto.so.1.1 while version 1.0.0 is bundled; done means the AWS Lambda runtime starts without the reported crypto load error.

Written by the indexing model from the issue text.

Description

OTP 26 requires a different version of libcrypto.so. The repo includes version 1.0.0 while the OTP crypto library is looking for 1.1:

hello_world start
=ERROR REPORT==== 3-Aug-2023::23:28:44.813510 ===
Unable to load crypto library. Failed with error:
"load_failed, Failed to load NIF library /var/task/lib/crypto-5.2/priv/lib/crypto: 'libcrypto.so.1.1: cannot open shared object file: No such file or directory'"
OpenSSL might not be installed on this system.
=CRASH REPORT==== 3-Aug-2023::23:28:44.814044 ===
Dominant language
Elixir
Stars
129
Forks
31
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws-samples/aws-lambda-elixir-runtime

All issues in aws-samples/aws-lambda-elixir-runtime

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.