Lambda layer crashes when LambdaInsights is enabled.

[kitsunde]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/serverless

SDK Version

arn:aws:lambda:ap-southeast-1:943013980633:layer:SentryNodeServerlessSDK:92

Framework Version

node 14.x

Link to Sentry event

No response

Steps to Reproduce

Since #6093 was merged 22 days ago there has been new releases, but the issue seem to persists.

Given:

Layers: 
  - arn:aws:lambda:ap-southeast-1:943013980633:layer:SentryNodeServerlessSDK:92
  - arn:aws:lambda:ap-southeast-1:580247275435:layer:LambdaInsightsExtension:21

The lambda crashes with:

+ exec /opt/relay/relay run --mode=proxy --shutdown-timeout=2 --aws-runtime-api=127.0.0.1:9001
LOGS	Name: cloudwatch_lambda_agent	State: Subscribed	Types: [platform]
2022-11-24T15:42:47Z [relay::setup] INFO: launching relay without config folder
2022-11-24T15:42:47Z [relay::setup] INFO:   relay mode: proxy
2022-11-24T15:42:47Z [relay::setup] INFO:   relay id: -
2022-11-24T15:42:47Z [relay::setup] INFO:   public key: -
2022-11-24T15:42:47Z [relay::setup] INFO:   log level: INFO
2022-11-24T15:42:47Z [relay_server::actors::outcome] INFO: Configured to emit outcomes as client reports
2022-11-24T15:42:47Z [relay_server::actors::upstream] INFO: upstream relay started
2022-11-24T15:42:47Z [relay_server::actors::outcome] INFO: OutcomeProducer started.
2022-11-24T15:42:47Z [relay_server::actors::processor] INFO: starting 5 envelope processing workers
2022-11-24T15:42:47Z [relay_server::actors::envelopes] INFO: envelope manager started
2022-11-24T15:42:47Z [relay_server::actors::project_cache] INFO: project cache started
2022-11-24T15:42:47Z [relay_server::actors::relays] INFO: key cache started
2022-11-24T15:42:47Z [relay_aws_extension::aws_extension] INFO: AWS extension started
2022-11-24T15:42:47Z [relay_aws_extension::aws_extension] INFO: Registering AWS extension on http://127.0.0.1:9001/2020-01-01/extension
2022-11-24T15:42:47Z [relay_log::utils] ERROR: bind to interface failed
caused by: Address already in use (os error 98)
EXTENSION	Name: cloudwatch_lambda_agent	State: Ready	Events: [INVOKE,SHUTDOWN]
EXTENSION	Name: sentry-lambda-extension	State: Started	Events: []
+ exec /opt/relay/relay run --mode=proxy --shutdown-timeout=2 --aws-runtime-api=127.0.0.1:9001
LOGS	Name: cloudwatch_lambda_agent	State: Already subscribed	Types: [platform]
2022-11-24T15:42:48Z [relay::setup] INFO: launching relay without config folder
2022-11-24T15:42:48Z [relay::setup] INFO:   relay mode: proxy
2022-11-24T15:42:48Z [relay::setup] INFO:   relay id: -
2022-11-24T15:42:48Z [relay::setup] INFO:   public key: -
2022-11-24T15:42:48Z [relay::setup] INFO:   log level: INFO
2022-11-24T15:42:48Z [relay_server::actors::outcome] INFO: Configured to emit outcomes as client reports
2022-11-24T15:42:48Z [relay_server::actors::upstream] INFO: upstream relay started
2022-11-24T15:42:48Z [relay_server::actors::processor] INFO: starting 5 envelope processing workers
2022-11-24T15:42:48Z [relay_server::actors::outcome] INFO: OutcomeProducer started.
2022-11-24T15:42:48Z [relay_server::actors::envelopes] INFO: envelope manager started
2022-11-24T15:42:48Z [relay_server::actors::project_cache] INFO: project cache started
2022-11-24T15:42:48Z [relay_server::actors::relays] INFO: key cache started
2022-11-24T15:42:48Z [relay_aws_extension::aws_extension] INFO: AWS extension started
2022-11-24T15:42:48Z [relay_aws_extension::aws_extension] INFO: Registering AWS extension on http://127.0.0.1:9001/2020-01-01/extension
2022-11-24T15:42:48Z [relay_log::utils] ERROR: bind to interface failed
caused by: Address already in use (os error 98)
EXTENSION	Name: cloudwatch_lambda_agent	State: Ready	Events: [INVOKE,SHUTDOWN]
EXTENSION	Name: sentry-lambda-extension	State: Started	Events: []
START RequestId: 9ef8dc2d-cadf-4d9b-ac67-2a4febd4a485 Version: $LATEST
RequestId: 9ef8dc2d-cadf-4d9b-ac67-2a4febd4a485 Error: exit status 1
Extension.Crash
END RequestId: 9ef8dc2d-cadf-4d9b-ac67-2a4febd4a485
REPORT RequestId: 9ef8dc2d-cadf-4d9b-ac67-2a4febd4a485	Duration: 747.05 ms	Billed Duration: 748 ms	Memory Size: 8192 MB	Max Memory Used: 46 MB	
XRAY TraceId: 1-637f90f7-5ca344660b289c57346e416c	SegmentId: 640f190e2b15ad2f	Sampled: true	

If I remove layer:LambdaInsightsExtension the lambda now runs. The last known version that works in this configuration is sentry layer 68.

Expected Result

Not to crash

Actual Result

boom

[AbhiPrasad]

It seems that the LambdaInsightsExtension is using the same port - @antonpirker could you take a look?

[kitsunde]

To be clear, this is the same issue as mentioned before the port change in the lambda layer: #5752 (comment)

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[Lms24]

@sl0thentr0py Since Anton is still on vacation, would you mind taking a quick look at this as I think you already did once in #6093?

[sl0thentr0py]

the port is already changed, so this should be fine with latest layer

[kitsunde]

the port is already changed, so this should be fine with latest layer

I made the change 22 days after your release as mentioned above, at the time of writing this is using the latest layer following up on a different reported issue after the change went in.

Can you actually confirm it was in by the time that lambda layer was released, and that it works with lambda insights?

If you tell me sentry's layer runs fine with lambda insights, I will recheck this and reproduce it in a project for you.