Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error after upgrading from Ubuntu 20.04 to Ubuntu 22.04 #54

Closed
Banjer opened this issue Apr 25, 2022 · 7 comments
Closed

Error after upgrading from Ubuntu 20.04 to Ubuntu 22.04 #54

Banjer opened this issue Apr 25, 2022 · 7 comments
Labels
bug Something isn't working

Comments

@Banjer
Copy link
Contributor

Banjer commented Apr 25, 2022

Since updating my server from ubuntu 20.04 to 22.04 i'm getting an error when running the radarr sync. The sonarr sync seems to run fine.
If you need more information, please let me know.

[ERR] An exception occurred during git operations on path: /home/bas/.config/trash-updater/repo
LibGit2Sharp.LibGit2SharpException: could not load ssl libraries
at LibGit2Sharp.Core.Ensure.HandleError(Int32 result) in //LibGit2Sharp/Core/Ensure.cs:line 154
at LibGit2Sharp.Core.Ensure.ZeroResult(Int32 result) in /
/LibGit2Sharp/Core/Ensure.cs:line 172
at LibGit2Sharp.Core.Proxy.git_clone(String url, String workdir, GitCloneOptions& opts) in //LibGit2Sharp/Core/Proxy.cs:line 275
at LibGit2Sharp.Repository.Clone(String sourceUrl, String workdirPath, CloneOptions options) in /
/LibGit2Sharp/Repository.cs:line 793
at VersionControl.Wrappers.LibGit2SharpRepositoryStaticWrapper.Clone(String sourceUrl, String workdirPath, CloneOptions options) in D:\a\trash-updater\trash-updater\src\VersionControl\Wrappers\LibGit2SharpRepositoryStaticWrapper.cs:line 8
at VersionControl.GitRepositoryFactory.DeleteAndCloneRepo(String repoUrl, String repoPath, String branch) in D:\a\trash-updater\trash-updater\src\VersionControl\GitRepositoryFactory.cs:line 42
at VersionControl.GitRepositoryFactory.CreateAndCloneIfNeeded(String repoUrl, String repoPath, String branch) in D:\a\trash-updater\trash-updater\src\VersionControl\GitRepositoryFactory.cs:line 27
at TrashLib.Radarr.CustomFormat.Guide.LocalRepoCustomFormatJsonParser.CheckoutAndUpdateRepo() in D:\a\trash-updater\trash-updater\src\TrashLib\Radarr\CustomFormat\Guide\LocalRepoCustomFormatJsonParser.cs:line 68
[INF] Deleting local git repo and retrying git operation...
[1] 257872 segmentation fault (core dumped) ./trash radarr

@rcdailey
Copy link
Member

Are you running 32 or 64-bit Ubuntu? And which version and architecture of Trash Updater did you download and run? Also please post the debug logs (you can find instructions here).

@rcdailey rcdailey added the bug Something isn't working label Apr 25, 2022
@Banjer
Copy link
Contributor Author

Banjer commented Apr 25, 2022

I'm running Ubuntu 64-bit and i'm using trash-linux-x64 (version 1.8.2)
I've also removed the ~/.config/trashupdater folder to clean the local cache to see if that fixed it.

trash_2022-04-25_22-16-21.log

@Banjer
Copy link
Contributor Author

Banjer commented Apr 25, 2022

Did some research and as far as i can see it might be related to the move from openssl 1.1 to openssl 3 Ubuntu made with 22.04

@Banjer
Copy link
Contributor Author

Banjer commented Apr 25, 2022

"fixed" the problem by installing the libssl package from Ubuntu 21.10 (https://packages.ubuntu.com/impish-updates/libssl1.1)
After installing that package the updater ran as expected, removing the package broke trash-updater again.
So far no other effects observed, but i don't think this is the best solution. Hope LibGit2Sharp will get updated to support libssl3.0

@rcdailey
Copy link
Member

Thanks a ton for researching this for me. I did about 5 minutes of Googling but I didn't come up with anything. I had a feeling it was something specific to SSL on Ubuntu 22, but I was going to set up a VirtualBox instance with it to verify. Looks like you saved me a lot of trouble, though!

I'm going to leave this issue open until some updates happen to the Troubleshooting wiki page. I'd like to document this issue for others that run into it.

@ghost
Copy link

ghost commented Apr 26, 2022

This also happens to me on Fedora Server 36. Same fix, had to install openssl1.1

@rcdailey
Copy link
Member

Since #56 is merged, I will go ahead and close this out. Thanks for the PR @Banjer!

@rcdailey rcdailey mentioned this issue May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants