Mssql-conf tool fails if IPV6 is disabled on the Linux system

Applies to: SQL Server in VM - LinuxSQL Server 2017 Developer LinuxSQL Server 2017 Enterprise Core Linux

Symptoms


Assume that you try to install Microsoft SQL Server 2019 on a Linux operating system such as Redhat or Ubuntu. If IPv6 is disabled at the OS kernel level, and you try to configure SQL Server by using the "sudo /opt/mssql/bin/mssql-conf setup" command, you receive the following messages in the Linux console and SQL Server error log. Additionally, the configuration may fail.

Linux console:
 
The licensing PID was successfully processed. The new edition is [Enterprise Evaluation Edition].
ForceFlush is enabled for this instance.
ForceFlush feature is enabled for log durability.
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
 
SQL Server error log:
 
DateTimeAndSpid     Clearing tempdb database.​
DateTimeAndSpid     [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.​
DateTimeAndSpid     Starting up database 'tempdb'.​
DateTimeAndSpid     The tempdb database has 1 data file(s).​
DateTimeAndSpid     The Service Broker endpoint is in disabled or stopped state.​
DateTimeAndSpid     The Database Mirroring endpoint is in disabled or stopped state.​
DateTimeAndSpid     Service Broker manager has started.​
DateTimeAndSpid      Database 'msdb' running the upgrade step from version VersionNum to version VersionNum.​
DateTimeAndSpid      Database 'msdb' running the upgrade step from version VersionNum to version VersionNum.​
DateTimeAndSpid     Error: 26024, Severity: 16, State: 1.​
DateTimeAndSpid     Server failed to listen on 'any' <ipv6> 1433. Error: 0x2742. To proceed, notify your system administrator.​
DateTimeAndSpid     Error: 17182, Severity: 16, State: 1.​
DateTimeAndSpid     TDSSNIClient initialization failed with error 0x2742, status code 0xa. Reason: Unable to initialize the TCP/IP listener. A socket operation encountered a dead network.​
DateTimeAndSpid     Error: 17182, Severity: 16, State: 1.​
DateTimeAndSpid     TDSSNIClient initialization failed with error 0x2742, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. A socket operation encountered a dead network.​
DateTimeAndSpid     Error: 39002, Severity: 16, State: 1.​
DateTimeAndSpid     SQL failed to boot extensibility for error code 0x80070005.​
DateTimeAndSpid     Error: 17826, Severity: 18, State: 3.​
DateTimeAndSpid     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.​
DateTimeAndSpid     Error: 17120, Severity: 16, State: 1.​
DateTimeAndSpid     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

Resolution


Workaround


To work around the issue, run the following command:
 
sudo MSSQL_IP_ADDRESS=0.0.0.0 /opt/mssql/bin/mssql-conf setup

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References


Learn about the terminology that Microsoft uses to describe software updates.