Skip to content

Instantly share code, notes, and snippets.

@chasetb
Created November 23, 2016 16:37
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save chasetb/098376f934dbb90b1f038677e0f12b27 to your computer and use it in GitHub Desktop.
Save chasetb/098376f934dbb90b1f038677e0f12b27 to your computer and use it in GitHub Desktop.
RDS Error log after Bit9 installer begins to create database tables
2016-11-21 12:09:55.61 Server Microsoft SQL Server 2014 - 12.0.4422.0 (X64)
Jul 27 2015 16:56:19
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2016-11-21 12:09:55.61 Server UTC adjustment: -7:00
2016-11-21 12:09:55.61 Server (c) Microsoft Corporation.
2016-11-21 12:09:55.61 Server All rights reserved.
2016-11-21 12:09:55.61 Server Server process ID is 3816.
2016-11-21 12:09:55.61 Server System Manufacturer: 'Xen', System Model: 'HVM domU'.
2016-11-21 12:09:55.61 Server Authentication mode is MIXED.
2016-11-21 12:09:55.61 Server Logging SQL Server messages in file 'D:\RDSDBDATA\Log\ERROR'.
2016-11-21 12:09:55.61 Server The service account is 'WORKGROUP\EC2AMAZ-J7SAKSM$'. This is an informational message; no user action is required.
2016-11-21 12:09:55.61 Server Registry startup parameters:
-d D:\RDSDBDATA\DATA\master.mdf
-e D:\RDSDBDATA\Log\ERROR
-l D:\RDSDBDATA\DATA\mastlog.ldf
-k 20.000000
-T 3226
-T 7806
2016-11-21 12:09:55.61 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2016-11-21 12:09:55.82 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.
2016-11-21 12:09:55.82 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-11-21 12:09:55.82 Server Detected 4095 MB of RAM. This is an informational message; no user action is required.
2016-11-21 12:09:55.82 Server Using conventional memory in the memory manager.
2016-11-21 12:09:55.89 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2016-11-21 12:09:55.93 Server The maximum number of dedicated administrator connections for this instance is '1'
2016-11-21 12:09:55.93 Server This instance of SQL Server last reported using a process ID of 3264 at 11/21/2016 12:09:55 PM (local) 11/21/2016 7:09:55 PM (UTC). This is an informational message only; no user action is required.
2016-11-21 12:09:55.93 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.
2016-11-21 12:09:55.93 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.
2016-11-21 12:09:55.96 Server Software Usage Metrics is disabled.
2016-11-21 12:09:55.96 spid10s Starting up database 'master'.
2016-11-21 12:09:56.04 Server CLR version v4.0.30319 loaded.
2016-11-21 12:09:56.05 spid10s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2016-11-21 12:09:56.05 spid10s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2016-11-21 12:09:56.07 spid10s SQL Trace ID 1 was started by login "sa".
2016-11-21 12:09:56.07 spid10s Server name is 'EC2AMAZ-J7SAKSM'. This is an informational message only. No user action is required.
2016-11-21 12:09:56.10 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2016-11-21 12:09:56.19 spid16s A new instance of the full-text filter daemon host process has been successfully started.
2016-11-21 12:09:56.33 spid10s Starting up database 'msdb'.
2016-11-21 12:09:56.33 spid12s Starting up database 'mssqlsystemresource'.
2016-11-21 12:09:56.34 spid12s The resource database build version is 12.00.4422. This is an informational message only. No user action is required.
2016-11-21 12:09:56.35 spid12s Starting up database 'model'.
2016-11-21 12:09:56.37 spid12s Clearing tempdb database.
2016-11-21 12:09:56.48 spid12s Starting up database 'tempdb'.
2016-11-21 12:09:56.52 spid19s The Service Broker endpoint is in disabled or stopped state.
2016-11-21 12:09:56.52 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2016-11-21 12:09:56.53 spid19s Service Broker manager has started.
2016-11-21 12:09:56.54 spid10s Launched startup procedure 'rds_startup_tasks'.
2016-11-21 12:09:56.58 spid27s Error: 50000, Severity: 15, State: 1.
2016-11-21 12:09:56.58 spid27s Access to tempdb was not granted because a master login was not found.
2016-11-21 12:09:56.74 spid27s Error: 50000, Severity: 15, State: 1.
2016-11-21 12:09:56.74 spid27s Access to tempdb was not granted because a master login was not found.
2016-11-21 12:10:11.06 spid15s The certificate [Cert Hash(sha1) "3D0BE22185223F72D22B5AC288A88E74A95EB174"] was successfully loaded for encryption.
2016-11-21 12:10:11.07 spid15s Server is listening on [ (IP OMITTED) <ipv4> 1433].
2016-11-21 12:10:11.07 spid15s Server is listening on [ 127.0.0.1 <ipv4> 1433].
2016-11-21 12:10:11.07 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2016-11-21 12:10:11.07 spid15s Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2016-11-21 12:10:11.07 Server Server is listening on [ ::1 <ipv6> 1434].
2016-11-21 12:10:11.07 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2016-11-21 12:10:11.07 Server Dedicated admin connection support was established for listening locally on port 1434.
2016-11-21 12:10:11.07 spid15s Recovery is complete. This is an informational message only. No user action is required.
2016-11-21 12:10:11.07 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2016-11-21 12:10:11.07 spid15s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-11-21 12:10:11.07 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/EC2AMAZ-J7SAKSM ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2016-11-21 12:10:11.95 spid51 Starting up database 'rdsadmin'.
2016-11-21 12:12:59.79 spid82 I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 12:12:59.79 spid83 I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 12:12:59.79 spid84 I/O is frozen on database rdsadmin. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 12:12:59.79 spid85 I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 12:13:09.40 spid83 I/O was resumed on database msdb. No user action is required.
2016-11-21 12:13:09.40 spid84 I/O was resumed on database rdsadmin. No user action is required.
2016-11-21 12:13:09.40 spid85 I/O was resumed on database master. No user action is required.
2016-11-21 12:13:09.40 spid82 I/O was resumed on database model. No user action is required.
2016-11-21 13:45:53.24 spid82 Starting up database 'das'.
2016-11-21 13:45:53.47 spid82 Setting database option RECOVERY to SIMPLE for database 'das'.
2016-11-21 13:46:00.02 spid53 Starting up database 'das'.
2016-11-21 13:46:00.11 spid53 Setting database option RECOVERY to FULL for database 'das'.
2016-11-21 13:46:00.12 spid52 Setting database option AUTO_CLOSE to OFF for database 'das'.
2016-11-21 13:46:28.23 spid82 Setting database option SINGLE_USER to ON for database 'das'.
2016-11-21 13:46:28.43 spid82 Starting up database 'das'.
2016-11-21 13:46:28.56 spid82 Setting database option RECOVERY to SIMPLE for database 'das'.
2016-11-21 13:47:30.24 spid88 Starting up database 'das'.
2016-11-21 13:47:30.53 spid84 I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 13:47:30.53 spid86 I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 13:47:30.53 spid85 I/O is frozen on database rdsadmin. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 13:47:30.53 spid88 I/O is frozen on database das. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 13:47:30.53 spid87 I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 13:47:40.14 spid86 I/O was resumed on database msdb. No user action is required.
2016-11-21 13:47:40.14 spid84 I/O was resumed on database model. No user action is required.
2016-11-21 13:47:40.14 spid87 I/O was resumed on database master. No user action is required.
2016-11-21 13:47:40.14 spid88 I/O was resumed on database das. No user action is required.
2016-11-21 13:47:40.14 spid85 I/O was resumed on database rdsadmin. No user action is required.
2016-11-21 13:47:40.81 spid84 Starting up database 'das'.
2016-11-21 13:50:26.14 spid82 Starting up database 'das'.
2016-11-21 13:50:26.24 spid82 Setting database option SINGLE_USER to ON for database 'das'.
2016-11-21 13:50:26.39 spid82 Starting up database 'das'.
2016-11-21 13:50:26.58 spid82 Setting database option RECOVERY to SIMPLE for database 'das'.
2016-11-21 13:51:00.01 spid54 Starting up database 'das'.
2016-11-21 13:51:00.12 spid54 Setting database option RECOVERY to FULL for database 'das'.
2016-11-21 13:51:00.13 spid53 Setting database option AUTO_CLOSE to OFF for database 'das'.
2016-11-21 14:02:56.16 spid82 I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 14:02:56.16 spid84 I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 14:02:56.16 spid85 I/O is frozen on database rdsadmin. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 14:02:56.16 spid86 I/O is frozen on database das. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 14:02:56.16 spid87 I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2016-11-21 14:03:05.77 spid86 I/O was resumed on database das. No user action is required.
2016-11-21 14:03:05.77 spid84 I/O was resumed on database msdb. No user action is required.
2016-11-21 14:03:05.77 spid87 I/O was resumed on database master. No user action is required.
2016-11-21 14:03:05.77 spid85 I/O was resumed on database rdsadmin. No user action is required.
2016-11-21 14:03:05.77 spid82 I/O was resumed on database model. No user action is required.
2016-11-21 14:57:30.43 spid82 Setting database option SINGLE_USER to ON for database 'das'.
2016-11-21 14:57:30.67 spid82 Starting up database 'das'.
2016-11-21 14:57:30.82 spid82 Setting database option RECOVERY to SIMPLE for database 'das'.
@anithasakaray
Copy link

Hi, I am able to see the similar type of logs in amazon console. What will be the root cause for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment