Речь про SQL Server 2019 последний, сейчас это CTP 3.2
Почему именно Docker глючит, потому что этот сиквел крашится в докере на xenial, и работает в докере на trusty. а других ОС с докером нет в travis-ci.org.
Краш где то в string allocator
$ docker logs sql-2019-for-tests || true
This program has encountered a fatal error and cannot continue running at Mon Jul 29 17:58:09 2019
The following diagnostic information is available:
This is an evaluation version. There are [173] days left in the evaluation period.
Reason: 0x00000003
Status: 0x00000001
Message: (*__errno_location ()) == 28 || (*__errno_location ()) == 22 || (*__errno_location ()) == 38
Stack:
IP Function
---------------- --------------------------------------
000056004c8fb3aa std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c8faea9 std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c8403ee std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c8db923 std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c8d72f1 std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c8d7e6f std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c83c79b std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > std::__1::operator+<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > c
000056004c82e645 <unknown>
00007f8e512ed830 __libc_start_main+0xf0
000056004c82b029 <unknown>
Process: 8 - sqlservr
Thread: 8
Instance Id: dcc4d00f-a198-4057-be69-a76b10c13025
Crash Id: ec5ae3da-8dd4-4ee3-bb1f-56fb877472e5
Build stamp: e7cecc1663d059f8a4c7f4e379339d34261f68cfceb977a62c34ac7bccbb72af
Distribution: Ubuntu 16.04.6 LTS
Processors: 2
Total Memory: 7836004352 bytes
Timestamp: Mon Jul 29 17:58:09 2019
Last errno: 1
Last errno text: Operation not permitted
dmesg: read kernel buffer failed: Operation not permitted
No journal files were found.
No journal files were found.
/opt/mssql/bin/crash-support-functions.sh: line 215: 199 Aborted (core dumped) $program_dir/paldumper $dokill -p $pid -d $paldumper_dump_type_str -o $dump_filename.gdmp > $paldumper_debuglog_filename 2>&1
Ubuntu 16.04.6 LTS
Capturing core dump and information to /var/opt/mssql/log...
Mon Jul 29 17:58:09 UTC 2019 Capturing program information
Mon Jul 29 17:58:09 UTC 2019 Attempting to capture a dump with paldumper
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper
Captured a filtered dump with paldumper
Mon Jul 29 17:58:10 UTC 2019 Capturing program binaries
Mon Jul 29 17:58:11 UTC 2019 Compressing the dump files
The command "docker logs sql-2019-for-tests || true" exited with 0.
Воспроизводится и с докером 18.06 (предустановленный в travis-ci.org) и с 19.03 (последний стабильный) докером. Воспроизводится — в смысле крашится в докере на xenail и работает в trusty.
Может что то надо доустановить или хитрую опцию передать в SQL 2019?
Запускаю как обычно:
docker run -d --privileged --name sql-2019-for-tests -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=Str@ngPassw0rd' -p 1435:1433 mcr.microsoft.com/mssql/server:2019-CTP3.2-ubuntu
если --privileged убрать то нет никакой разницы, я просто его добавил посмотрев на ошибку
Почему я тут пишу — потому что нужен xenial, ибо какашечная Microsoft перестала тестить .NET Core на trusty, хотя каноникал свою trusty еще 3 года за деньги официально саппортит.
Недавно вышел SQL 2019 RC1. Он прекрасно работает на travis-ci.org в свежем линуксе. Никаких крашей:
$ docker logs sql-2019-for-tests | head -9999 || true
SQL Server 2019 will run as non-root by default.
This container is running as user root.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
This is an evaluation version. There are [112] days left in the evaluation period.
2019-10-27 13:03:56.65 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2019-10-27 13:03:56.73 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2019-10-27 13:03:56.74 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2019-10-27 13:03:56.74 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2019-10-27 13:03:56.77 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2019-10-27 13:03:56.80 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2019-10-27 13:03:56.84 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2019-10-27 13:03:56.85 Server Setup step is copying system data file 'C:\templatedata\model_replicatedmaster.mdf' to '/var/opt/mssql/data/model_replicatedmaster.mdf'.
2019-10-27 13:03:56.86 Server Setup step is copying system data file 'C:\templatedata\model_replicatedmaster.ldf' to '/var/opt/mssql/data/model_replicatedmaster.ldf'.
2019-10-27 13:03:56.87 Server Setup step is copying system data file 'C:\templatedata\model_msdbdata.mdf' to '/var/opt/mssql/data/model_msdbdata.mdf'.
2019-10-27 13:03:56.90 Server Setup step is copying system data file 'C:\templatedata\model_msdblog.ldf' to '/var/opt/mssql/data/model_msdblog.ldf'.
2019-10-27 13:03:57.04 Server Microsoft SQL Server 2019 (RC1) - 15.0.1900.25 (X64)
Aug 16 2019 14:20:53
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS) <X64>
2019-10-27 13:03:57.04 Server UTC adjustment: 0:00
2019-10-27 13:03:57.04 Server (c) Microsoft Corporation.
2019-10-27 13:03:57.04 Server All rights reserved.
2019-10-27 13:03:57.04 Server Server process ID is 32.
2019-10-27 13:03:57.04 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-10-27 13:03:57.04 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2019-10-27 13:03:57.06 Server SQL Server detected 1 sockets with 1 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-10-27 13:03:57.06 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-10-27 13:03:57.06 Server Detected 5978 MB of RAM. This is an informational message; no user action is required.
2019-10-27 13:03:57.06 Server Using conventional memory in the memory manager.
2019-10-27 13:03:57.07 Server Page exclusion bitmap is enabled.
2019-10-27 13:03:57.11 Server Buffer pool extension is not supported on Linux platform.
2019-10-27 13:03:57.12 Server Buffer Pool: Allocating 1048576 bytes for 883685 hashPages.
2019-10-27 13:03:57.40 Server Buffer pool extension is already disabled. No action is necessary.
2019-10-27 13:03:57.68 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are ['1.0 1.1 1.2']. Allowed TLS ciphers are ['ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA'].
2019-10-27 13:03:57.71 Server Query Store settings initialized with enabled = 1,
2019-10-27 13:03:57.75 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-10-27 13:03:57.75 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2019-10-27 13:03:57.78 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2019-10-27 13:03:57.80 Server In-Memory OLTP initialized on lowend machine.
2019-10-27 13:03:57.88 Server [INFO] Created Extended Events session 'hkenginexesession'
2019-10-27 13:03:57.89 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
ForceFlush is enabled for this instance.
2019-10-27 13:03:57.92 Server Total Log Writer threads: 1. This is an informational message; no user action is required.
2019-10-27 13:03:57.95 Server clflush is selected for pmem flush operation.
2019-10-27 13:03:57.97 Server Software Usage Metrics is disabled.
2019-10-27 13:03:57.98 spid7s [1]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-10-27 13:03:57.98 spid7s Starting up database 'master'.
2019-10-27 13:03:58.12 Server CLR version v4.0.30319 loaded.
ForceFlush feature is enabled for log durability.
2019-10-27 13:03:58.58 spid7s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 2560 bytes at offset 427520 in file /var/opt/mssql/data/mastlog.ldf will be written.
2019-10-27 13:03:58.89 spid7s Converting database 'master' from version 897 to the current version 904.
2019-10-27 13:03:58.90 spid7s Database 'master' running the upgrade step from version 897 to version 898.
2019-10-27 13:03:58.93 spid7s Database 'master' running the upgrade step from version 898 to version 899.
2019-10-27 13:03:59.01 spid7s Database 'master' running the upgrade step from version 899 to version 900.
2019-10-27 13:03:59.07 spid7s Database 'master' running the upgrade step from version 900 to version 901.
2019-10-27 13:03:59.09 spid7s Database 'master' running the upgrade step from version 901 to version 902.
2019-10-27 13:03:59.11 spid7s Database 'master' running the upgrade step from version 902 to version 903.
2019-10-27 13:03:59.13 spid7s Database 'master' running the upgrade step from version 903 to version 904.
2019-10-27 13:03:59.42 Server Common language runtime (CLR) functionality initialized.
2019-10-27 13:03:59.68 spid7s Resource governor reconfiguration succeeded.
2019-10-27 13:03:59.69 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-10-27 13:03:59.69 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-10-27 13:03:59.83 spid7s SQL Trace ID 1 was started by login "sa".
2019-10-27 13:03:59.86 spid7s Server name is '38cbb71446b5'. This is an informational message only. No user action is required.
2019-10-27 13:03:59.92 spid26s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-10-27 13:03:59.92 spid11s [32767]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-10-27 13:03:59.93 spid26s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2019-10-27 13:03:59.94 spid7s [4]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-10-27 13:03:59.94 spid11s Starting up database 'mssqlsystemresource'.
2019-10-27 13:03:59.95 spid23s Password policy update was successful.
2019-10-27 13:03:59.95 spid7s Starting up database 'msdb'.
2019-10-27 13:03:59.96 spid11s The resource database build version is 15.00.1900. This is an informational message only. No user action is required.
2019-10-27 13:04:00.05 spid11s [3]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-10-27 13:04:00.06 spid11s Starting up database 'model'.
2019-10-27 13:04:00.38 Server Failed to verify the Authenticode signature of 'C:\binn\secforwarder.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-10-27 13:04:00.70 spid7s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 50176 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2019-10-27 13:04:00.75 spid23s A self-generated certificate was successfully loaded for encryption.
2019-10-27 13:04:00.75 spid11s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 73216 in file /var/opt/mssql/data/modellog.ldf will be written.
2019-10-27 13:04:00.78 spid23s Server is listening on [ 'any' <ipv6> 1433].
2019-10-27 13:04:00.79 spid23s Server is listening on [ 'any' <ipv4> 1433].
2019-10-27 13:04:00.81 Server Server is listening on [ ::1 <ipv6> 1434].
2019-10-27 13:04:00.81 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2019-10-27 13:04:00.81 Server Dedicated admin connection support was established for listening locally on port 1434.
2019-10-27 13:04:00.84 spid7s Converting database 'msdb' from version 897 to the current version 904.
2019-10-27 13:04:00.84 spid7s Database 'msdb' running the upgrade step from version 897 to version 898.
2019-10-27 13:04:00.84 spid23s Server is listening on [ ::1 <ipv6> 1431].
2019-10-27 13:04:00.85 spid23s Server is listening on [ 127.0.0.1 <ipv4> 1431].
2019-10-27 13:04:00.85 spid23s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-10-27 13:04:00.90 spid11s Converting database 'model' from version 897 to the current version 904.
2019-10-27 13:04:00.91 spid11s Database 'model' running the upgrade step from version 897 to version 898.
2019-10-27 13:04:00.91 spid7s Database 'msdb' running the upgrade step from version 898 to version 899.
2019-10-27 13:04:00.94 spid11s Database 'model' running the upgrade step from version 898 to version 899.
2019-10-27 13:04:00.99 spid7s Database 'msdb' running the upgrade step from version 899 to version 900.
2019-10-27 13:04:01.03 spid11s Database 'model' running the upgrade step from version 899 to version 900.
2019-10-27 13:04:01.06 spid7s Database 'msdb' running the upgrade step from version 900 to version 901.
2019-10-27 13:04:01.07 spid11s Database 'model' running the upgrade step from version 900 to version 901.
2019-10-27 13:04:01.08 spid7s Database 'msdb' running the upgrade step from version 901 to version 902.
2019-10-27 13:04:01.09 spid11s Database 'model' running the upgrade step from version 901 to version 902.
2019-10-27 13:04:01.11 spid11s Database 'model' running the upgrade step from version 902 to version 903.
2019-10-27 13:04:01.13 spid11s Database 'model' running the upgrade step from version 903 to version 904.
2019-10-27 13:04:01.25 spid11s Clearing tempdb database.
2019-10-27 13:04:01.32 Server Failed to verify the Authenticode signature of 'C:\binn\msoledbsql.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-10-27 13:04:01.94 spid11s [2]. Feature Status: PVS: 0. CTR: 0. ConcurrentPFSUpdate: 1.
2019-10-27 13:04:01.94 spid11s Starting up database 'tempdb'.
2019-10-27 13:04:02.27 spid11s The tempdb database has 1 data file(s).
2019-10-27 13:04:02.28 spid28s The Service Broker endpoint is in disabled or stopped state.
2019-10-27 13:04:02.28 spid28s The Database Mirroring endpoint is in disabled or stopped state.
2019-10-27 13:04:02.30 spid28s Service Broker manager has started.
2019-10-27 13:04:02.34 spid7s Database 'msdb' running the upgrade step from version 902 to version 903.
2019-10-27 13:04:02.36 spid7s Database 'msdb' running the upgrade step from version 903 to version 904.
2019-10-27 13:04:02.53 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-10-27 13:04:02.55 spid26s The default language (LCID 0) has been set for engine and full-text services.
2019-10-27 13:04:02.79 spid26s The tempdb database has 2 data file(s).
