Closed AnalogJ closed 7 months ago
Newrelic instrumented lambdas are failing with /lib64/libc.so.6: version `GLIBC_2.34' not found
2024-02-14T11:34:04.262-08:00 START RequestId: af74f517-4c8b-41e6-8998-6bfab44fdcd2 Version: $LATEST 2024-02-14T11:34:04.265-08:00 RequestId: af74f517-4c8b-41e6-8998-6bfab44fdcd2 Error: exit status 1 Extension.Crash 2024-02-14T11:34:04.265-08:00 END RequestId: af74f517-4c8b-41e6-8998-6bfab44fdcd2 2024-02-14T11:34:04.265-08:00 REPORT RequestId: af74f517-4c8b-41e6-8998-6bfab44fdcd2 Duration: 8.29 ms Billed Duration: 9 ms Memory Size: 1024 MB Max Memory Used: 3 MB 2024-02-14T11:34:04.370-08:00 /opt/extensions/newrelic-lambda-extension: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by /opt/extensions/newrelic-lambda-extension) 2024-02-14T11:34:04.370-08:00 /opt/extensions/newrelic-lambda-extension: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by /opt/extensions/newrelic-lambda-extension) 2024-02-14T11:34:04.370-08:00 EXTENSION Name: newrelic-lambda-extension State: Started Events: [] 2024-02-14T11:34:04.370-08:00 INIT_REPORT Init Duration: 5.51 ms Phase: invoke Status: error Error Type: Extension.Crash
serverless-newrelic-lambda-layers: ^5.0.0 runtime: provided.al2
Run without a crash during startup.
See above.
serverless-newrelic-lambda-layers: ^5.0.0 runtime: provided.al2 arn:aws:lambda:us-east-1:451483290750:layer:NewRelicLambdaExtension:35
Locking to arn:aws:lambda:us-east-1:451483290750:layer:NewRelicLambdaExtension:34 fixes the issue.
This is a duplicate of https://github.com/newrelic/newrelic-lambda-extension/issues/196. I'm closing and can follow the work in that issue
Newrelic instrumented lambdas are failing with /lib64/libc.so.6: version `GLIBC_2.34' not found
Description
serverless-newrelic-lambda-layers: ^5.0.0 runtime: provided.al2
Steps to Reproduce
Expected Behaviour
Run without a crash during startup.
Relevant Logs / Console output
See above.
Your Environment
serverless-newrelic-lambda-layers: ^5.0.0 runtime: provided.al2 arn:aws:lambda:us-east-1:451483290750:layer:NewRelicLambdaExtension:35
Additional context
Locking to arn:aws:lambda:us-east-1:451483290750:layer:NewRelicLambdaExtension:34 fixes the issue.