MS SQL Server 2017 on Linux Has Released
-
Looks like it is listening.
[jbusch@sql ~]$ netstat -tulpn (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:1431 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:1433 0.0.0.0:* LISTEN - tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 ::1:1431 :::* LISTEN - tcp6 0 0 :::1433 :::* LISTEN - udp 0 0 0.0.0.0:68 0.0.0.0:* - udp 0 0 127.0.0.1:323 0.0.0.0:* - udp6 0 0 ::1:323 :::* - [jbusch@sql ~]$ -
Firewall is definitely open, right?
-
@scottalanmiller said in MS SQL Server 2017 on Linux Has Released:
Firewall is definitely open, right?
Yes, but SELinux was running, as expected. Just disabled and rebooting.
-
My first test of it was on Fedora too, no issues, but that was a bit ago on Fedora 27
-
@flaxking said in MS SQL Server 2017 on Linux Has Released:
My first test of it was on Fedora too, no issues, but that was a bit ago on Fedora 27
SQL 2017 will not install on Fedora 29 because it said OpenSSL < 1.something was not available.
-
[jbusch@sql ~]$ sudo sestatus [sudo] password for jbusch: SELinux status: disabled [jbusch@sql ~]$ sudo firewall-cmd --list-ports 1433/tcp [jbusch@sql ~]$[jbusch@sql ~]$ sudo systemctl status mssql-server ● mssql-server.service - Microsoft SQL Server Database Engine Loaded: loaded (/usr/lib/systemd/system/mssql-server.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2018-11-08 17:53:12 CST; 3min 53s ago Docs: https://docs.microsoft.com/en-us/sql/linux Main PID: 645 (sqlservr) Tasks: 113 Memory: 1.6G CGroup: /system.slice/mssql-server.service ├─645 /opt/mssql/bin/sqlservr └─792 /opt/mssql/bin/sqlservr Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [62B blob data] Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [61B blob data] Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [389B blob data] Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [96B blob data] Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [66B blob data] Nov 08 17:53:18 sql.jaredbusch.com sqlservr[645]: [79B blob data] Nov 08 17:53:19 sql.jaredbusch.com sqlservr[645]: [96B blob data] Nov 08 17:53:19 sql.jaredbusch.com sqlservr[645]: [100B blob data] Nov 08 17:53:19 sql.jaredbusch.com sqlservr[645]: [71B blob data] Nov 08 17:53:19 sql.jaredbusch.com sqlservr[645]: [124B blob data]Same error.
[jbusch@sql ~]$ sqlcmd -S localhost -U SA -P 'BNA$upport710' Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : TCP Provider: Error code 0x2746. Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : Client unable to establish connection.I'm not worried about this working, but I was pleasantly surprised.
-
exact same VM config with CentOS 7 fails because of CentOS uses and reports memory differently.
KVM settings specified 2048 RAM for both the Fedora 29 system and the CentOS 7 system..
-
Upped it to 3072 RAM and SQL setup completed normally.
-
Does it allow odd number processors yet or do I still have to disable one if I don't have an even number?
-
@tonyshowoff said in MS SQL Server 2017 on Linux Has Released:
Does it allow odd number processors yet or do I still have to disable one if I don't have an even number?
Even only for licensing, I believe. No change there.
