The transaction log for database 'master' is full due to 'NOTHING' during Updade

Question

Hello,

I am using the SQL Server docker image from Docker Hub: microsoft/mssql-server-linux:2017-GA.

I am able to run this image locally (using Docker for Mac).  But on our Jenkins linux vm, I am seeing the following errors:

Starting up database 'master'.
The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
Converting database 'master' from version 862 to the current version 869.
Database 'master' running the upgrade step from version 862 to version 863.
Database 'master' running the upgrade step from version 863 to version 864.

Error: 17053, Severity: 16, State: 1.

/var/opt/mssql/data/mastlog.ldf: Operating system error 31(A device attached to the system is not functioning.) encountered.

Error: 928, Severity: 20, State: 1.

During upgrade, database raised exception 9002, severity 17, state 0, address 0000000484D726DE. Use the exception number to determine the cause.

Error: 9002, Severity: 17, State: 0.

The transaction log for database 'master' is full due to 'NOTHING'.

The server has HD space, and I have yet to do anything short of connecting to the new database from the image.  Can anyone help?

Colin

Answer 1

Not sure about error 17053 & 928. Except 17053 appears to be some kind of hardware issue with the drive.

Regarding error 9002, when you run sp_helpfile in master db context, does it show 'unlimited' for both data & log files of maxsize column?

HTH,

---

Phil Streiff, MCDBA, MCITP, MCSA

Answer 2

Hi Phil,

Yes, both the mdf and ldf maxsize are set to "Unlimted".

Colin

Answer 3

Hello,

I've faced exactly the same issue. Did you already solve it?

Answer 4

Try to disable the job which is filling the log until the job properly investigated. read here for more detail: http://www.sqlserverlogexplorer.com/error-9002-transaction-full/

Answer 5

Hi Teige,

This issue is happening on the docker image from docker hub: https://hub.docker.com/r/microsoft/mssql-server-linux/

I don't know how I can implement any of these changes, since the error happens the first time I connect via sqlcmd.  So I am not sure how I can make the suggested configuration changes without connecting to the database.

16:29:58 2017-10-19 23:29:58.54 Server      Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
16:29:58 
2017-10-19 23:29:58.81 Server      Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
16:29:58 
2017-10-19 23:29:58.84 Server      Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
16:29:58 
2017-10-19 23:29:58.90 Server      Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
16:29:58 
2017-10-19 23:29:58.97 Server      Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
16:29:59 
2017-10-19 23:29:59.06 Server      Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
16:29:59 
2017-10-19 23:29:59.53 Server      Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64) 
16:29:59 
	Aug 22 2017 17:04:49 
16:29:59 
	Copyright (C) 2017 Microsoft Corporation
16:29:59 
	Developer Edition (64-bit) on Linux (Ubuntu 16.04.3 LTS)
16:29:59 
2017-10-19 23:29:59.57 Server      UTC adjustment: 0:00
16:29:59 
2017-10-19 23:29:59.58 Server      (c) Microsoft Corporation.
16:29:59 
2017-10-19 23:29:59.58 Server      All rights reserved.
16:29:59 
2017-10-19 23:29:59.59 Server      Server process ID is 4120.
16:29:59 
2017-10-19 23:29:59.59 Server      Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
16:29:59 
2017-10-19 23:29:59.61 Server      Registry startup parameters: 
16:29:59 
	 -d /var/opt/mssql/data/master.mdf
16:29:59 
	 -l /var/opt/mssql/data/mastlog.ldf
16:29:59 
	 -e /var/opt/mssql/log/errorlog
16:29:59 
2017-10-19 23:29:59.65 Server      SQL Server detected 8 sockets with 1 cores per socket and 1 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
16:29:59 
2017-10-19 23:29:59.70 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
16:29:59 
2017-10-19 23:29:59.72 Server      Detected 25741 MB of RAM. This is an informational message; no user action is required.
16:29:59 
2017-10-19 23:29:59.72 Server      Using conventional memory in the memory manager.
16:29:59 
2017-10-19 23:29:59.74 Server      Large Page Allocated: 32MB 
16:30:00 
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
16:30:00 Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
16:30:00 Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
16:30:00 Error connecting to sql server.
16:30:00 2017-10-19 23:30:00.91 Server      Buffer pool extension is already disabled. No action is necessary. 
16:30:01 
2017-10-19 23:30:01.47 Server      InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
16:30:01 
2017-10-19 23:30:01.48 Server      Implied authentication manager initialization failed. Implied authentication will be disabled.
16:30:01 
2017-10-19 23:30:01.50 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'].
16:30:01 
2017-10-19 23:30:01.58 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
16:30:01 
2017-10-19 23:30:01.59 Server      The maximum number of dedicated administrator connections for this instance is '1'
16:30:01 
2017-10-19 23:30:01.69 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.
16:30:01 
2017-10-19 23:30:01.72 Server      In-Memory OLTP initialized on standard machine.
16:30:01 
2017-10-19 23:30:01.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.
16:30:01 
2017-10-19 23:30:01.96 Server      Query Store settings initialized with enabled = 1, 
16:30:02 
2017-10-19 23:30:02.00 spid4s      Starting up database 'master'.
16:30:02 
2017-10-19 23:30:02.03 Server      Software Usage Metrics is disabled.
16:30:03 
2017-10-19 23:30:03.60 spid4s      The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
16:30:04 
2017-10-19 23:30:04.18 spid4s      Converting database 'master' from version 862 to the current version 869.
16:30:04 
2017-10-19 23:30:04.19 spid4s      Database 'master' running the upgrade step from version 862 to version 863.
16:30:04 
2017-10-19 23:30:04.36 spid4s      Database 'master' running the upgrade step from version 863 to version 864.
16:30:04 
2017-10-19 23:30:04.49 spid4s      Error: 17053, Severity: 16, State: 1.
16:30:04 
2017-10-19 23:30:04.49 spid4s      /var/opt/mssql/data/mastlog.ldf: Operating system error 31(A device attached to the system is not functioning.) encountered.
16:30:05 
2017-10-19 23:30:05.51 spid4s      Error: 928, Severity: 20, State: 1.
16:30:05 
2017-10-19 23:30:05.51 spid4s      During upgrade, database raised exception 9002, severity 17, state 0, address 0000000484D726DE. Use the exception number to determine the cause.
16:30:05 
2017-10-19 23:30:05.55 spid4s      Error: 9002, Severity: 17, State: 0.
16:30:05 
2017-10-19 23:30:05.55 spid4s      The transaction log for database 'master' is full due to 'NOTHING'.

<style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Monaco} span.s1 {text-decoration: underline} </style>

Answer 6

Hi Colin,

Based on my searching, some people have also met this problem, I'm still consulting with the product team and will give you an update as soon as possible.

Best Regards,

Teige

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 7

I ran into the same issue:

/var/opt/mssql/data/mastlog.ldf: Operating system error 31(A device attached to the system is not functioning.) encountered.
16:30:05 

I use Vagrant + Docker VM on VirtualBox

How to fix it ?

Answer 8

I am getting the same issue with the latest update of the SQL 2017 image from the Docker Store. 

I use a mapped drive to allow my databases to be stored on my host drive instead of inside the docker container.  I mapped a local host folder to /var/opt/mssql.  That got the error above.  

This was working fine before my last update.  I also just updated to the latest version of Docker for Windows.  Is it possible that docker changed something that is causing this to break?

I switched it to map another folder (/var/opt/data to a local host folder) in which I placed my database data and log files.  Then I was able to start the container, connect to it via SSMS and attach the databases from the /var/opt/data folder.  That seemed to work just fine.

--Stewart McGuire

---

Stewart McGuire

Answer 9

Same issue on Windows and has occurred only in the past week.  e.g., unable to restore database to folder mapped to local host, but can restore them to a local folder, detach, move to the host folder and successfully attach.

Problem is also manifesting itself in problems with the tempdb which is also in the host mapped folder.  The tempdb will not auto expand, so getting the error  "The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'".  Have manually added a second log file for the tempdb and problem is currently worked around.

Answer 10

Same error here, also reported in github page

Answer 11

I let you a partial hack here, it works for me.

Answer 12

An active issue on github is  github.com/Microsoft/mssql-docker/issues/180

On that thread new release reported as working again to create databases on external volumes.  Personally I successfully ran quick test that had been failing for last 5 months.