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

While installing/running mssql-conf setup showing Error: cannot find libcrypto.so #56

Open
tango4567 opened this issue Mar 21, 2023 · 0 comments
Labels

Comments

@tango4567
Copy link
Owner

tango4567 commented Mar 21, 2023

OS: Ubuntu 22.04.2 LTS

Terminal Output
sudo /opt/mssql/bin/mssql-conf setup
Locale en_IN not supported. Using en_US.
Choose an edition of SQL Server:
  1) Evaluation (free, no production use rights, 180-day limit)
  2) Developer (free, no production use rights)
  3) Express (free)
  4) Web (PAID)
  5) Standard (PAID)
  6) Enterprise (PAID) - CPU core utilization restricted to 20 physical/40 hyperthreaded
  7) Enterprise Core (PAID) - CPU core utilization up to Operating System Maximum
  8) I bought a license through a retail sales channel and have a product key to enter.
  9) Standard (Billed through Azure) - Use pay-as-you-go billing through Azure.
 10) Enterprise Core (Billed through Azure) - Use pay-as-you-go billing through Azure.

Details about editions can be found at
https://go.microsoft.com/fwlink/?LinkId=2109348

Use of PAID editions of this software requires separate licensing through a
Microsoft Volume Licensing program.
By choosing a PAID edition, you are verifying that you have the appropriate
number of licenses in place to install and run this software.
By choosing an edition billed Pay-As-You-Go through Azure, you are verifying 
that the server and SQL Server will be connected to Azure by installing the 
management agent and Azure extension for SQL Server.

Enter your edition(1-10): 3
The license terms for this product can be found in
/usr/share/doc/mssql-server or downloaded from:
https://go.microsoft.com/fwlink/?LinkId=2104294

The privacy statement can be viewed at:
https://go.microsoft.com/fwlink/?LinkId=853010


Choose the language for SQL Server:
(1) English
(2) Deutsch
(3) Español
(4) Français
(5) Italiano
(6) 日本語
(7) 한국어
(8) Português
(9) Руѝѝкий
(10) 中文 – 简体
(11) 中文 (繝体)
Enter Option 1-11: 1
Enter the SQL Server system administrator password: 
Confirm the SQL Server system administrator password: 
Configuring SQL Server...

Error: cannot find libcrypto.so in any system library search paths. Ensure that a file or symbolic link named 'libcrypto.so' exists in the system library search paths. To resolve this error, a symbolic link to the 'libcrypto.so' library can be placed in the '/opt/mssql/lib/' directory.
Error: cannot find libssl.so in any system library search paths. Ensure that a file or symbolic link named 'libssl.so' exists in the system library search paths. To resolve this error, a symbolic link to the 'libssl.so' library can be placed in the '/opt/mssql/lib/' directory.
/opt/mssql/bin/sqlservr: PAL initialization failed. Error: 102

Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
Log /var/opt/mssql/log
03-21 12:39:41,424:INFO:mssql-conf: Trying to make owner and group of the log files at /var/opt/mssql/log/mssql-conf mssql.
2023-03-21 12:39:41,424:INFO:mssql-conf: Found user ID (999) and group ID (999) for user mssql.
2023-03-21 12:39:41,424:INFO:mssql-conf: Trying chown the directory.
2023-03-21 12:39:41,424:INFO:mssql-conf: Succesfully chown'd the directory.
2023-03-21 12:39:41,425:INFO:mssql-conf: Trying to set ownership for file /var/opt/mssql/log/mssql-conf/mssql-conf.log.
2023-03-21 12:39:41,425:INFO:mssql-conf: Successfully set ownership for file.
2023-03-21 12:39:41,425:INFO:mssql-conf: Changing the permissions of the file to 660.
2023-03-21 12:39:41,425:INFO:mssql-conf: Changed the permissions of the file.
2023-03-21 12:39:41,425:INFO:mssql-conf: Successfully changed ownership for the directory /var/opt/mssql/log/mssql-conf and all files in that directory.
2023-03-21 12:39:41,425:INFO:mssql-conf: Added shutdown hook to ensure ownership on the log files is correct.
2023-03-21 12:39:41,425:INFO:mssql-conf: Logging has been fully configured.
2023-03-21 12:39:41,425:INFO:mssql-conf: Executing command: [setup]
2023-03-21 12:39:41,426:INFO:mssql-conf: Running script: [/opt/mssql/lib/mssql-conf/checkinstall.sh]
2023-03-21 12:39:41,433:INFO:mssql-conf: Script gave output: [usermod: no changes
]
2023-03-21 12:39:41,433:INFO:mssql-conf: Running script: [/opt/mssql/lib/mssql-conf/checkrunninginstance.sh]
2023-03-21 12:39:41,448:INFO:mssql-conf: Script gave output: []
2023-03-21 12:39:48,530:INFO:mssql-conf: Changing setting with name [azurebilling] in section [licensing] to value [false].
2023-03-21 12:39:48,531:INFO:mssql-conf: Writing configuration to file: [/var/opt/mssql/mssql.conf]
2023-03-21 12:39:48,531:INFO:mssql-conf: Successfully changed setting.
2023-03-21 12:39:50,294:INFO:mssql-conf: Writing configuration to file: [/var/opt/mssql/mssql.conf]
2023-03-21 12:39:50,294:INFO:mssql-conf: Running script: [/opt/mssql/lib/mssql-conf/checkrunninginstance.sh]
2023-03-21 12:39:50,313:INFO:mssql-conf: Script gave output: []
2023-03-21 12:39:59,256:INFO:mssql-conf: Trying to make owner and group of the log files at /var/opt/mssql/log/mssql-conf mssql.
2023-03-21 12:39:59,256:INFO:mssql-conf: Found user ID (999) and group ID (999) for user mssql.
2023-03-21 12:39:59,256:INFO:mssql-conf: Trying chown the directory.
2023-03-21 12:39:59,256:INFO:mssql-conf: Succesfully chown'd the directory.
2023-03-21 12:39:59,256:INFO:mssql-conf: Trying to set ownership for file /var/opt/mssql/log/mssql-conf/mssql-conf.log.
2023-03-21 12:39:59,257:INFO:mssql-conf: Successfully set ownership for file.
2023-03-21 12:39:59,257:INFO:mssql-conf: Changing the permissions of the file to 660.
2023-03-21 12:39:59,257:INFO:mssql-conf: Changed the permissions of the file.
2023-03-21 12:39:59,257:INFO:mssql-conf: Successfully changed ownership for the directory /var/opt/mssql/log/mssql-conf and all files in that directory.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant