You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crashes with the error: No usable version of libssl was found
[opc@almalinux-arm64-devtest azure-pipelines]$ ./config.sh
___ ______ _ _ _
/ _ \ | ___ (_) | (_)
/ /_\ \_____ _ _ __ ___ | |_/ /_ _ __ ___| |_ _ __ ___ ___
| _ |_ / | | | '__/ _ \ | __/| | '_ \ / _ \ | | '_ \ / _ \/ __|
| | | |/ /| |_| | | | __/ | | | | |_) | __/ | | | | | __/\__ \
\_| |_/___|\__,_|_| \___| \_| |_| .__/ \___|_|_|_| |_|\___||___/
| |
agent v2.204.0 |_| (commit 166abe8)
>> End User License Agreements:
Building sources from a TFVC repository requires accepting the Team Explorer Everywhere End User License Agreement. This step is not required for building sources from Git repositories.
A copy of the Team Explorer Everywhere license agreement can be found at:
/home/opc/azure-pipelines/license.html
Enter (Y/N) Accept the Team Explorer Everywhere license agreement now? (press enter for N) > y
>> Connect:
Enter server URL > https://dev.azure.com/quokka-code
Enter authentication type (press enter for PAT) >
Enter personal access token > ****************************************************
No usable version of libssl was found
./config.sh: line 86: 174765 Aborted (core dumped) ./bin/Agent.Listener configure "$@"
Hi @BenWibking, the reason may be is that Agent is still using .Net Core 3.1, which requires OpenSSL 1.1 - #3834 (comment)
Could you check if libssl 1.1 is present on your machine?
Agent Version and Platform
Version of your agent? v2.204.0
OS of the machine running the agent? Linux (AlmaLinux 9.0)
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server? dev.azure.com
If dev.azure.com, what is your organization name? https://dev.azure.com/quokka-code
What's not working?
Crashes with the error:
No usable version of libssl was found
Agent and Worker's Diagnostic Logs
Agent_20220718-013126-utc.log
The text was updated successfully, but these errors were encountered: