I cannot run mssql immediately following an apt-get update. Is this due to a bad script (below:
The file "C:\Install\SqlTraceCollect.dtsx" does not exist)? Any suggestions on a fix? I'm at a loss.
sudo systemctl start mssql-server sudo systemctl status mssql-server ● mssql-server.service - Microsoft SQL Server Database Engine Loaded: loaded (/lib/systemd/system/mssql-server.service; enabled; vendor preset: enabled) Active: active (running) ... sudo systemctl status mssql-server ● mssql-server.service - Microsoft SQL Server Database Engine Loaded: loaded (/lib/systemd/system/mssql-server.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Wed 2018-03-21 22:46:15 PDT; 1min 27s ago Docs: https://learn.microsoft.com/en-us/sql/linux Process: 2977 ExecStart=/opt/mssql/bin/sqlservr (code=exited, status=255) Main PID: 2977 (code=exited, status=255) ... sudo cat /var/opt/mssql/log/errorlog 2018-03-21 22:36:24.19 Server Microsoft SQL Server 2017 (RTM-CU5) (KB4092643) - 14.0.3023.8 (X64) ... 2018-03-21 22:36:35.90 spid6s Creating SSIS folders... ... 2018-03-21 22:36:35.91 spid6s Creating procedure [dbo].[sp_syscollector_upload_instmdw]... 2018-03-21 22:36:35.92 spid6s Uploading data collector package from disk: C:\Install\SqlTraceCollect.dtsx 2018-03-21 22:36:35.92 spid6s Uploading data collector package from disk: C:\Install\SqlTraceCollect.dtsx 2018-03-21 22:36:35.93 spid6s Error: 4860, Severity: 16, State: 1. 2018-03-21 22:36:35.93 spid6s Cannot bulk load. The file "C:\Install\SqlTraceCollect.dtsx" does not exist or you don't have file access rights. 2018-03-21 22:36:35.93 spid6s Error: 912, Severity: 21, State: 2. 2018-03-21 22:36:35.93 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 2018-03-21 22:36:35.95 spid6s Error: 3417, Severity: 21, State: 3. 2018-03-21 22:36:35.95 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online. 2018-03-21 22:36:35.96 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.