Disable aws-lc-sys jitter entropy to avoid startup SIGABRT - #6776
Merged
Conversation
CPU Jitter Entropy's health check can fail on freshly-started VMs/containers (timing signal too regular in the first seconds of process life), which aws-lc treats as fatal and abort()s with no stderr output. This has been crashing pipelines and coordinators seconds after startup during the first TLS handshake (#1845), matching aws-lc-rs#1072. Set AWS_LC_SYS_NO_JITTER_ENTROPY=1 in .cargo/config.toml for CI/local builds, and explicitly in the pipeline compiler's cargo invocation, which env_clear()s and needs it forwarded separately since it builds the pipeline binary that actually hits the abort. Fixes: feldera/cloud#1845 Signed-off-by: Ben Pfaff <blp@feldera.com>
mihaibudiu
approved these changes
Jul 30, 2026
Contributor
|
thanks this makes sense, I was thinking we should also try to upgrade since the latest fips module finally can be linked dynamically so we dont need to build it ourselves we can do it in a follow up PR |
Member
Author
It doesn't make sense that Amazon, a company that famously rents VMs, would build a library that tends to fail in VMs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CPU Jitter Entropy's health check can fail on freshly-started VMs/containers (timing signal too regular in the first seconds of process life), which aws-lc treats as fatal and abort()s with no stderr output. This has been crashing pipelines and coordinators seconds after startup during the first TLS handshake, matching aws-lc-rs#1072.
Set AWS_LC_SYS_NO_JITTER_ENTROPY=1 in .cargo/config.toml for CI/local builds, and explicitly in the pipeline compiler's cargo invocation, which env_clear()s and needs it forwarded separately since it builds the pipeline binary that actually hits the abort.
Fixes: https://github.com/feldera/cloud/issues/1845