Shared lib not found: libssl.so.1.1: cannot open shared object file
#1007
Comments
|
Alright, issue seems very similar to apollographql/router#2623 , and sure enough actions now run on Ubuntu 24. Old run was on 22.04.5, recent and failed run was on 24.04.1. |
alexpovel
added a commit
to alexpovel/srgn
that referenced
this issue
Sep 28, 2024
Fixes issue from foresterre/cargo-msrv#1007 which reads: --- Greetings! `cargo msrv` started failing recently, with the exact error message reading: ```text /home/runner/.cargo/bin/cargo-msrv: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory ``` in [this GitHub Actions run](https://github.com/alexpovel/srgn/actions/runs/11077412470/job/30782601329#step:5:9). There is a good chance this error is unrelated to `msrv` itself: - the last *successful* run was just [5 days ago](https://github.com/alexpovel/srgn/actions/runs/10998984127/job/30538156429#step:5:11), and in between then and the above failure yesterday... - `msrv` didn't have a release (looking at GitHub releases), `0.15.1` was used in both the [successful](https://github.com/alexpovel/srgn/actions/runs/10998984127/job/30538156429#step:4:49) and [failed](https://github.com/alexpovel/srgn/actions/runs/11077412470/job/30782601329#step:4:49) run - nothing in the repo changed (pipelines etc.) - however, it seems like the Ubuntu runner image had an [update](https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20240922.1) in the meantime though. Not sure that had any impact. It's one of the only things that changed between those runs anyway. The curious thing is that all other CI jobs remained successful, the `msrv` is the only failing one (well one other is failing but that's expected). That's why I'm opening an issue here. Would you happen to have any pointers on how that could be? Perhaps an issue with used dependencies? I'd guess libssl would be used by other jobs running in CI as well (but have no data on this), which were all successful. Alright, issue seems very similar to apollographql/router#2623 , and sure enough [actions now run on Ubuntu 24](https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/). Old [run was on 22.04.5](https://github.com/alexpovel/srgn/actions/runs/10998984127/job/30538156429#step:1:4), recent and [failed run was on 24.04.1](https://github.com/alexpovel/srgn/actions/runs/11077412470/job/30782601329#step:1:4).
|
Looks like the last stable release of 0.15.1 is quite old now, 2.5 years, and switching to the latest beta version of cargo-msrv 0.16.0-beta.25 fixes the issues. So probably some dependency bump in that time which helped. Leaving this issue open for visibility, but it's fixed on my side! |
|
Hi, thanks for the report! I'll have a look at this issue in the upcoming week. Concerning 0.16: I'm planning a 0.16.0 release in the upcoming week or the week thereafter, depending on available time. |
|
Is still an issue with 0.16.x? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Greetings!
cargo msrvstarted failing recently, with the exact error message reading:in this GitHub Actions run. There is a good chance this error is unrelated to
msrvitself:msrvdidn't have a release (looking at GitHub releases),0.15.1was used in both the successful and failed runThe curious thing is that all other CI jobs remained successful, the
msrvis the only failing one (well one other is failing but that's expected). That's why I'm opening an issue here.Would you happen to have any pointers on how that could be? Perhaps an issue with used dependencies? I'd guess libssl would be used by other jobs running in CI as well (but have no data on this), which were all successful.
The text was updated successfully, but these errors were encountered: