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

sqlserver on linux core dump with Docker 1.13 but nothing logged #23

Closed
mi-hol opened this issue Jan 22, 2017 · 1 comment
Closed

sqlserver on linux core dump with Docker 1.13 but nothing logged #23

mi-hol opened this issue Jan 22, 2017 · 1 comment

Comments

@mi-hol
Copy link

mi-hol commented Jan 22, 2017

after upgrading docker from 1.12 to 1.13 and sqlserver image for linux from 14.0.1.246 (X64)
to 14.0.100.187 (X64)

container log shows below error but the file names reported to contain relevant informant have size of 0 byte for '/var/opt/mssql/log/core.sqlservr.01_20_2017_17_27_03.11.log' and the core dump does not exist ' /var/opt/mssql/log/core.sqlservr.01_20_2017_17_27_03.11'

docker version:
Server:
Version: 1.13.0
API version: 1.25 (minimum version 1.12)
Go version: go1.7.3
Git commit: 49bf474
Built: Wed Jan 18 16:20:26 2017
OS/Arch: linux/amd64
Experimental: false

This is an evaluation version. There are [144] days left in the evaluation period.
2017-01-20 17:20:34.71 Server Microsoft SQL Server vNext (CTP1.1) - 14.0.100.187 (X64)
Dec 10 2016 02:51:11
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
on Linux (Ubuntu 16.04.1 LTS)
2017-01-20 17:20:34.72 Server UTC adjustment: 0:00
2017-01-20 17:20:34.72 Server (c) Microsoft Corporation.
2017-01-20 17:20:34.72 Server All rights reserved.
2017-01-20 17:20:34.72 Server Server process ID is 4116.
2017-01-20 17:20:34.72 Server Logging SQL Server messages in file 'C:\var\opt\mssql\log\errorlog'.
2017-01-20 17:20:34.72 Server Registry startup parameters:
-d C:\var\opt\mssql\data\master.mdf
-l C:\var\opt\mssql\data\mastlog.ldf
-e C:\var\opt\mssql\log\errorlog
2017-01-20 17:20:35.07 Server SQL Server detected 1 sockets with 2 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.
2017-01-20 17:20:35.07 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-01-20 17:20:35.08 Server Detected 3541 MB of RAM. This is an informational message; no user action is required.
2017-01-20 17:20:35.08 Server Using conventional memory in the memory manager.
2017-01-20 17:20:36.74 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2017-01-20 17:20:41.45 Server Buffer pool extension is already disabled. No action is necessary.
2017-01-20 17:20:47.89 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2017-01-20 17:20:47.89 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2017-01-20 17:20:48.64 Server The maximum number of dedicated administrator connections for this instance is '1'
2017-01-20 17:20:48.65 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.
2017-01-20 17:20:48.68 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.
2017-01-20 17:20:48.68 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.
2017-01-20 17:20:48.69 Server Query Store settings initialized with enabled = 1,
2017-01-20 17:20:48.72 spid4s Starting up database 'master'.
2017-01-20 17:20:48.73 Server In-Memory OLTP initialized on lowend machine.
2017-01-20 17:20:50.86 Server Software Usage Metrics is disabled.
2017-01-20 17:20:52.93 spid4s 4 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2017-01-20 17:20:53.20 spid4s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2017-01-20 17:20:53.21 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2017-01-20 17:20:54.23 spid4s Buffer pool extension is already disabled. No action is necessary.
2017-01-20 17:20:54.23 spid4s Resource governor reconfiguration succeeded.
2017-01-20 17:20:54.23 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2017-01-20 17:20:54.25 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2017-01-20 17:20:56.19 spid4s SQL Trace ID 1 was started by login "sa".
2017-01-20 17:20:56.24 spid4s Server name is '6efa3aef6ecf'. This is an informational message only. No user action is required.
2017-01-20 17:20:56.28 spid20s Starting up database 'msdb'.
2017-01-20 17:20:56.28 spid6s Starting up database 'mssqlsystemresource'.
2017-01-20 17:20:56.29 spid21s Starting up database 'testdb'.
2017-01-20 17:20:56.32 spid6s The resource database build version is 14.00.100. This is an informational message only. No user action is required.
2017-01-20 17:20:56.41 spid6s Starting up database 'model'.
2017-01-20 17:21:02.80 spid21s Parallel redo is started for database 'testdb' with worker pool size [1].
2017-01-20 17:21:03.53 spid6s Polybase feature disabled.
2017-01-20 17:21:03.53 spid6s Clearing tempdb database.
2017-01-20 17:21:03.90 spid4s Recovery completed for database msdb (database ID 4) in 2 second(s) (analysis 27 ms, redo 740 ms, undo 480 ms.) This is an informational message only. No user action is required.
2017-01-20 17:21:04.59 spid21s 66 transactions rolled forward in database 'testdb' (5:0). This is an informational message only. No user action is required.
2017-01-20 17:21:04.77 spid4s 0 transactions rolled back in database 'testdb' (5:0). This is an informational message only. No user action is required.
2017-01-20 17:21:04.78 spid4s Recovery completed for database testdb (database ID 5) in 3 second(s) (analysis 87 ms, redo 1705 ms, undo 123 ms.) This is an informational message only. No user action is required.
2017-01-20 17:21:04.80 spid4s Parallel redo is shutdown for database 'testdb' with worker pool size [1].
2017-01-20 17:21:15.64 spid17s A self-generated certificate was successfully loaded for encryption.
2017-01-20 17:21:16.11 spid17s Server is listening on [ 0.0.0.0 1433].
2017-01-20 17:21:16.12 Server Server is listening on [ 127.0.0.1 1434].
2017-01-20 17:21:16.12 Server Dedicated admin connection support was established for listening locally on port 1434.
2017-01-20 17:21:16.13 spid17s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-01-20 17:21:18.32 spid6s Starting up database 'tempdb'.
2017-01-20 17:21:21.61 spid6s The tempdb database has 1 data file(s).
2017-01-20 17:21:21.82 spid22s The Service Broker endpoint is in disabled or stopped state.
2017-01-20 17:21:21.82 spid22s The Database Mirroring endpoint is in disabled or stopped state.
DBSTARTUP (testdb, 5): FCBOpenTime took 2390 ms
DBSTARTUP (testdb, 5): FCBHeaderReadTime took 1512 ms
DBSTARTUP (testdb, 5): FileMgrPreRecoveryTime took 3125 ms
DBSTARTUP (testdb, 5): MasterFilesScanTime took 1029 ms
DBSTARTUP (testdb, 5): AnalysisRecTime took 231 ms
DBSTARTUP (testdb, 5): RedoRecTime took 1705 ms
DBSTARTUP (testdb, 5): PhysicalRecoveryTime took 1941 ms
DBSTARTUP (testdb, 5): StartupInDatabaseTime took 17068 ms
2017-01-20 17:21:22.03 spid22s Service Broker manager has started.
DBSTARTUP (msdb, 4): FCBOpenTime took 2340 ms
DBSTARTUP (msdb, 4): FCBHeaderReadTime took 1436 ms
DBSTARTUP (msdb, 4): FileMgrPreRecoveryTime took 2996 ms
DBSTARTUP (msdb, 4): MasterFilesScanTime took 960 ms
DBSTARTUP (msdb, 4): RedoRecTime took 740 ms
DBSTARTUP (msdb, 4): PhysicalRecoveryTime took 768 ms
DBSTARTUP (msdb, 4): RecoveryCompletionTime took 281 ms
DBSTARTUP (msdb, 4): StartupInDatabaseTime took 17741 ms
2017-01-20 17:21:22.45 spid4s Recovery is complete. This is an informational message only. No user action is required.
2017-01-20 17:25:50.40 spid51 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2017-01-20 17:25:52.47 spid51 Using 'xplog70.dll' version '2016.140.100' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
sqlservr: ObjectWaitContext.cpp:533: void ObjectWaitContext::Wait(const PLONG64): Assertion `m_state == State::Signaled' failed.
Capturing core dump and information for sqlservr (pid 11)...
cat: core.sqlservr.11.temp/log/debug.log: No such file or directory
dmesg: read kernel buffer failed: Operation not permitted
No journal files were found.
No journal files were found.
ls: cannot access '/var/opt/mssql/log/log/errorlog*': No such file or directory
ls: cannot access '/var/opt/mssql/log/log/exception.log': No such file or directory
ls: cannot access '/var/opt/mssql/log/log/SQLDu*.txt': No such file or directory
ls: cannot access '/var/opt/mssql/log/log/SQLDu*.mdmp': No such file or directory
ls: cannot access '/var/opt/mssql/log/log/system_health*': No such file or directory
Packaging core dump and information into compressed files.
Core dump and information will be written to /var/opt/mssql/log/core.sqlservr.01_20_2017_17_27_03.11 and logs in /var/opt/mssql/log/core.sqlservr.01_20_2017_17_27_03.11.log

@mi-hol mi-hol changed the title linux core dump with Docker 1.13 but nothing logged sqlserver on linux core dump with Docker 1.13 but nothing logged Jan 24, 2017
@mi-hol
Copy link
Author

mi-hol commented Jan 24, 2017

Microsoft SQL Server vNext (CTP1.2) - 14.0.200.24 (X64) solved this issue

@mi-hol mi-hol closed this as completed Jan 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant