Parseable not running starting 2.5.4 and also with 2.5.5 now

[imagdy83]

I've been running pareasble v2.5.3 without issues and since v2.5.4 I've been getting this error

thread 'main' (1394759) panicked at /home/runner/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustls-0.23.35/src/crypto/mod.rs:249:14:

Could not automatically determine the process-level CryptoProvider from Rustls crate features.
Call CryptoProvider::install_default() before this point to select a provider manually, or make sure exactly one of the 'aws-lc-rs' and 'ring' features is enabled.
See the documentation of the CryptoProvider type for more information.

I'm running parseable on ubuntu 24.04

[nitisht]

Thanks for reporting @imagdy83 - did you see exact same error in 2.5.4 also?

[imagdy83]

Thanks for reporting @imagdy83 - did you see exact same error in 2.5.4 also?

Yes it started happening with 2.5.4, we reverted back to version 2.5.3 thinking the issue would be fixed with 2.5.5 but unfortunately the issue is still there

[parmesant]

Hey @imagdy83
Could you help me reproduce this issue? I tried running the 2.5.5 binary on a Ubuntu 24.04 machine and it ran just fine. Please share the specifics of your setup-
local store or s3 store
Standalone or distributed mode
Any specific env vars that you've set

We can continue the conversation on slack if you want-
https://logg.ing/community

[imagdy83]

Hey @imagdy83 Could you help me reproduce this issue? I tried running the 2.5.5 binary on a Ubuntu 24.04 machine and it ran just fine. Please share the specifics of your setup- local store or s3 store Standalone or distributed mode Any specific env vars that you've set

We can continue the conversation on slack if you want- https://logg.ing/community

We are running a standalone s3 store setup, the env vars we are currently using are

P_S3_URL=
P_S3_BUCKET=
P_S3_ACCESS_KEY=
P_S3_SECRET_KEY=
P_S3_REGION=
P_STAGING_DIR=
P_S3_CHECKSUM=
P_USERNAME=
P_PASSWORD=
P_ADDR=0.0.0.0:9876
P_TLS_CERT_PATH=
P_TLS_KEY_PATH=
overwrite_staging=true
P_OIDC_CLIENT_ID=
P_OIDC_CLIENT_SECRET=
P_OIDC_ISSUER=
P_ORIGIN_URI=

And we run parseable using the command "nohup /usr/local/bin/parseable s3-store"

Let me know if there's any more information you need.

[parmesant]

@imagdy83 would you be open to a call regarding this issue?

[imagdy83]

@imagdy83 would you be open to a call regarding this issue?

Yes

[parmesant]

Great
Please reach out to me (anant vindal) on our slack

[imagdy83]

I do not have slack, would teams work?

[parmesant]

In that case kindly reach out to me via email at- anant@parseable.com

[parmesant]

Hey @imagdy83
We want to resolve this issue ASAP. How would you like to connect?

[imagdy83]

Hey @imagdy83 We want to resolve this issue ASAP. How would you like to connect?

I am available now, since I do not have slack, how would you like to connect?

[parmesant]

Fell free to book a session here-
https://cal.com/anant-vindal-kwqzz7

Or if you want to connect some other way, let me know

[parmesant]

@imagdy83 we have identified the issue and are able to reproduce it. We're working on a fix for the same