SqlServer on linux getting very slow The 2019 Stack Overflow Developer Survey Results Are In Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara Come Celebrate our 10 Year Anniversary!SQL Server Migration Assistant for OracleSQL Server 2008 - Error starting service - model.mdf not found?Problem with MS DTC on SQL2008 win server 2k8 with linked server from sql2000 win server 2kSQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1How to diagnose repeated “Starting up database '<dbname>'”Does SQL Server 2008 R2 lock memory pages by default?Login failed when SQL Server startsSQL Server express service is not startingMSDTC Errors: QueryInterface failed for “ITransactionDispenser”: 0x8004d01c(XACT_E_CONNECTION_DOWN)SQLServer 2008 R2 (also SP1/SP2) on Windows 10 within Virtualbox does not start
For what reasons would an animal species NOT cross a *horizontal* land bridge?
60's-70's movie: home appliances revolting against the owners
Does Parliament need to approve the new Brexit delay to 31 October 2019?
What's the point in a preamp?
Is there a writing software that you can sort scenes like slides in PowerPoint?
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
What can I do if neighbor is blocking my solar panels intentionally?
How did passengers keep warm on sail ships?
Why did Peik Lin say, "I'm not an animal"?
Why doesn't shell automatically fix "useless use of cat"?
The following signatures were invalid: EXPKEYSIG 1397BC53640DB551
A phrase ”follow into" in a context
Store Dynamic-accessible hidden metadata in a cell
Why are PDP-7-style microprogrammed instructions out of vogue?
Can withdrawing asylum be illegal?
Drawing vertical/oblique lines in Metrical tree (tikz-qtree, tipa)
Am I ethically obligated to go into work on an off day if the reason is sudden?
Was credit for the black hole image misappropriated?
How to politely respond to generic emails requesting a PhD/job in my lab? Without wasting too much time
Why can't wing-mounted spoilers be used to steepen approaches?
Can I visit the Trinity College (Cambridge) library and see some of their rare books
"... to apply for a visa" or "... and applied for a visa"?
How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?
Didn't get enough time to take a Coding Test - what to do now?
SqlServer on linux getting very slow
The 2019 Stack Overflow Developer Survey Results Are In
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
Come Celebrate our 10 Year Anniversary!SQL Server Migration Assistant for OracleSQL Server 2008 - Error starting service - model.mdf not found?Problem with MS DTC on SQL2008 win server 2k8 with linked server from sql2000 win server 2kSQL Server 08 Express error when connecting to localhost - “Timeout expired”. Works with ::1 or 127.0.0.1How to diagnose repeated “Starting up database '<dbname>'”Does SQL Server 2008 R2 lock memory pages by default?Login failed when SQL Server startsSQL Server express service is not startingMSDTC Errors: QueryInterface failed for “ITransactionDispenser”: 0x8004d01c(XACT_E_CONNECTION_DOWN)SQLServer 2008 R2 (also SP1/SP2) on Windows 10 within Virtualbox does not start
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
0
I have an Ubuntu 16.04 VPS and started to test SQL Server on it. Installation went flawlessly and I was using it for about a month without any problems. Then I did an apt update and it didn't start. Tbh it started with this kind of error (don't remember the exact error code):
Server is in script upgrade mode. Only administrator can connect at
this time.
I was in a hurry and managed to start it with a switch I found somewhere and it was running for one more week. But today it was eating 100% of CPU time and was so slow even an application at localhost couldn't work because of timeout errors.
This is a test server only so I thought that I remove and install sql server again. I did but that didn't help either. I have installed an express version but even the mssql-conf setup was working for ~1 hour before it has started and I still can not connect remotely with management studio, ad localhost connections are slow, too. It is using 1% of cpu time now tough.
I have deleted everything from /opt/mssql before reinstalling it. Removed everything even from /var/opt/mssql and it's working now. Why I can not connect? (timeout) What could have changed since it was working very well the first time?
My VPS is a cheap virtual server with a KVM host. the VPS has 4GB RAM and 4CPU "vCore". Last log is shown below but I think it doesn't say anything interesting. How can I get back the previous good configuration and reaction time? Or how can I determine what causes it's problem?
2019-04-08 12:55:50.40 Server Microsoft SQL Server 2017 (RTM-CU14) (KB4484710) - 14.0.3076.1 (X64)
Mar 12 2019 19:29:19
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2019-04-08 12:55:50.40 Server UTC adjustment: 0:00
2019-04-08 12:55:50.41 Server (c) Microsoft Corporation.
2019-04-08 12:55:50.41 Server All rights reserved.
2019-04-08 12:55:50.41 Server Server process ID is 28.
2019-04-08 12:55:50.41 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-04-08 12:55:50.41 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-04-08 12:55:50.42 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.
2019-04-08 12:55:50.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-04-08 12:55:50.43 Server Detected 3277 MB of RAM. This is an informational message; no user action is required.
2019-04-08 12:55:50.43 Server Using conventional memory in the memory manager.
2019-04-08 12:55:50.54 Server Buffer pool extension is already disabled. No action is necessary.
2019-04-08 12:55:50.64 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-04-08 12:55:50.64 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-04-08 12:55:50.65 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-04-08 12:55:50.69 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-04-08 12:55:50.69 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-04-08 12:55:50.70 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-04-08 12:55:50.71 Server In-Memory OLTP initialized on lowend machine.
2019-04-08 12:55:50.75 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.
2019-04-08 12:55:50.76 Server Query Store settings initialized with enabled = 1,
2019-04-08 12:55:50.77 spid7s Starting up database 'master'.
2019-04-08 12:55:50.77 Server Software Usage Metrics is disabled.
2019-04-08 12:55:51.00 spid7s 10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.03 spid7s 1 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.04 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.51 Server Failed to verify the Authenticode signature of 'C:binnsecforwarder.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-04-08 12:55:51.58 spid7s SQL Trace ID 1 was started by login "sa".
2019-04-08 12:55:51.82 spid7s Server name is 'vs2558'. This is an informational message only. No user action is required.
2019-04-08 12:55:51.83 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-04-08 12:55:51.84 spid22s 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-04-08 12:55:51.84 spid7s Starting up database 'msdb'.
2019-04-08 12:55:51.84 spid10s Starting up database 'mssqlsystemresource'.
2019-04-08 12:55:51.84 spid10s The resource database build version is 14.00.3076. This is an informational message only. No user action is required.
2019-04-08 12:55:51.87 spid10s Starting up database 'model'.
2019-04-08 12:55:52.19 spid18s A self-generated certificate was successfully loaded for encryption.
2019-04-08 12:55:52.19 spid10s Polybase feature disabled.
2019-04-08 12:55:52.19 spid10s Clearing tempdb database.
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv6> 1433].
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv4> 1433].
2019-04-08 12:55:52.21 spid18s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated ad
ministrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-04-08 12:55:52.22 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-04-08 12:55:52.40 spid10s Starting up database 'tempdb'.
2019-04-08 12:55:52.60 spid22s The Service Broker endpoint is in disabled or stopped state.
2019-04-08 12:55:52.60 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2019-04-08 12:55:52.61 spid22s Service Broker manager has started.
2019-04-08 12:55:52.90 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-04-08 13:01:45.81 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-04-08 13:01:45.85 spid52 Using 'xplog70.dll' version '2017.140.3076' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
ubuntu sql-server vps
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
0
I have an Ubuntu 16.04 VPS and started to test SQL Server on it. Installation went flawlessly and I was using it for about a month without any problems. Then I did an apt update and it didn't start. Tbh it started with this kind of error (don't remember the exact error code):
Server is in script upgrade mode. Only administrator can connect at
this time.
I was in a hurry and managed to start it with a switch I found somewhere and it was running for one more week. But today it was eating 100% of CPU time and was so slow even an application at localhost couldn't work because of timeout errors.
This is a test server only so I thought that I remove and install sql server again. I did but that didn't help either. I have installed an express version but even the mssql-conf setup was working for ~1 hour before it has started and I still can not connect remotely with management studio, ad localhost connections are slow, too. It is using 1% of cpu time now tough.
I have deleted everything from /opt/mssql before reinstalling it. Removed everything even from /var/opt/mssql and it's working now. Why I can not connect? (timeout) What could have changed since it was working very well the first time?
My VPS is a cheap virtual server with a KVM host. the VPS has 4GB RAM and 4CPU "vCore". Last log is shown below but I think it doesn't say anything interesting. How can I get back the previous good configuration and reaction time? Or how can I determine what causes it's problem?
2019-04-08 12:55:50.40 Server Microsoft SQL Server 2017 (RTM-CU14) (KB4484710) - 14.0.3076.1 (X64)
Mar 12 2019 19:29:19
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2019-04-08 12:55:50.40 Server UTC adjustment: 0:00
2019-04-08 12:55:50.41 Server (c) Microsoft Corporation.
2019-04-08 12:55:50.41 Server All rights reserved.
2019-04-08 12:55:50.41 Server Server process ID is 28.
2019-04-08 12:55:50.41 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-04-08 12:55:50.41 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-04-08 12:55:50.42 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.
2019-04-08 12:55:50.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-04-08 12:55:50.43 Server Detected 3277 MB of RAM. This is an informational message; no user action is required.
2019-04-08 12:55:50.43 Server Using conventional memory in the memory manager.
2019-04-08 12:55:50.54 Server Buffer pool extension is already disabled. No action is necessary.
2019-04-08 12:55:50.64 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-04-08 12:55:50.64 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-04-08 12:55:50.65 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-04-08 12:55:50.69 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-04-08 12:55:50.69 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-04-08 12:55:50.70 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-04-08 12:55:50.71 Server In-Memory OLTP initialized on lowend machine.
2019-04-08 12:55:50.75 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.
2019-04-08 12:55:50.76 Server Query Store settings initialized with enabled = 1,
2019-04-08 12:55:50.77 spid7s Starting up database 'master'.
2019-04-08 12:55:50.77 Server Software Usage Metrics is disabled.
2019-04-08 12:55:51.00 spid7s 10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.03 spid7s 1 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.04 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.51 Server Failed to verify the Authenticode signature of 'C:binnsecforwarder.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-04-08 12:55:51.58 spid7s SQL Trace ID 1 was started by login "sa".
2019-04-08 12:55:51.82 spid7s Server name is 'vs2558'. This is an informational message only. No user action is required.
2019-04-08 12:55:51.83 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-04-08 12:55:51.84 spid22s 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-04-08 12:55:51.84 spid7s Starting up database 'msdb'.
2019-04-08 12:55:51.84 spid10s Starting up database 'mssqlsystemresource'.
2019-04-08 12:55:51.84 spid10s The resource database build version is 14.00.3076. This is an informational message only. No user action is required.
2019-04-08 12:55:51.87 spid10s Starting up database 'model'.
2019-04-08 12:55:52.19 spid18s A self-generated certificate was successfully loaded for encryption.
2019-04-08 12:55:52.19 spid10s Polybase feature disabled.
2019-04-08 12:55:52.19 spid10s Clearing tempdb database.
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv6> 1433].
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv4> 1433].
2019-04-08 12:55:52.21 spid18s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated ad
ministrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-04-08 12:55:52.22 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-04-08 12:55:52.40 spid10s Starting up database 'tempdb'.
2019-04-08 12:55:52.60 spid22s The Service Broker endpoint is in disabled or stopped state.
2019-04-08 12:55:52.60 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2019-04-08 12:55:52.61 spid22s Service Broker manager has started.
2019-04-08 12:55:52.90 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-04-08 13:01:45.81 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-04-08 13:01:45.85 spid52 Using 'xplog70.dll' version '2017.140.3076' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
ubuntu sql-server vps
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42
add a comment |
0
0
0
I have an Ubuntu 16.04 VPS and started to test SQL Server on it. Installation went flawlessly and I was using it for about a month without any problems. Then I did an apt update and it didn't start. Tbh it started with this kind of error (don't remember the exact error code):
Server is in script upgrade mode. Only administrator can connect at
this time.
I was in a hurry and managed to start it with a switch I found somewhere and it was running for one more week. But today it was eating 100% of CPU time and was so slow even an application at localhost couldn't work because of timeout errors.
This is a test server only so I thought that I remove and install sql server again. I did but that didn't help either. I have installed an express version but even the mssql-conf setup was working for ~1 hour before it has started and I still can not connect remotely with management studio, ad localhost connections are slow, too. It is using 1% of cpu time now tough.
I have deleted everything from /opt/mssql before reinstalling it. Removed everything even from /var/opt/mssql and it's working now. Why I can not connect? (timeout) What could have changed since it was working very well the first time?
My VPS is a cheap virtual server with a KVM host. the VPS has 4GB RAM and 4CPU "vCore". Last log is shown below but I think it doesn't say anything interesting. How can I get back the previous good configuration and reaction time? Or how can I determine what causes it's problem?
2019-04-08 12:55:50.40 Server Microsoft SQL Server 2017 (RTM-CU14) (KB4484710) - 14.0.3076.1 (X64)
Mar 12 2019 19:29:19
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2019-04-08 12:55:50.40 Server UTC adjustment: 0:00
2019-04-08 12:55:50.41 Server (c) Microsoft Corporation.
2019-04-08 12:55:50.41 Server All rights reserved.
2019-04-08 12:55:50.41 Server Server process ID is 28.
2019-04-08 12:55:50.41 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-04-08 12:55:50.41 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-04-08 12:55:50.42 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.
2019-04-08 12:55:50.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-04-08 12:55:50.43 Server Detected 3277 MB of RAM. This is an informational message; no user action is required.
2019-04-08 12:55:50.43 Server Using conventional memory in the memory manager.
2019-04-08 12:55:50.54 Server Buffer pool extension is already disabled. No action is necessary.
2019-04-08 12:55:50.64 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-04-08 12:55:50.64 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-04-08 12:55:50.65 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-04-08 12:55:50.69 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-04-08 12:55:50.69 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-04-08 12:55:50.70 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-04-08 12:55:50.71 Server In-Memory OLTP initialized on lowend machine.
2019-04-08 12:55:50.75 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.
2019-04-08 12:55:50.76 Server Query Store settings initialized with enabled = 1,
2019-04-08 12:55:50.77 spid7s Starting up database 'master'.
2019-04-08 12:55:50.77 Server Software Usage Metrics is disabled.
2019-04-08 12:55:51.00 spid7s 10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.03 spid7s 1 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.04 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.51 Server Failed to verify the Authenticode signature of 'C:binnsecforwarder.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-04-08 12:55:51.58 spid7s SQL Trace ID 1 was started by login "sa".
2019-04-08 12:55:51.82 spid7s Server name is 'vs2558'. This is an informational message only. No user action is required.
2019-04-08 12:55:51.83 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-04-08 12:55:51.84 spid22s 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-04-08 12:55:51.84 spid7s Starting up database 'msdb'.
2019-04-08 12:55:51.84 spid10s Starting up database 'mssqlsystemresource'.
2019-04-08 12:55:51.84 spid10s The resource database build version is 14.00.3076. This is an informational message only. No user action is required.
2019-04-08 12:55:51.87 spid10s Starting up database 'model'.
2019-04-08 12:55:52.19 spid18s A self-generated certificate was successfully loaded for encryption.
2019-04-08 12:55:52.19 spid10s Polybase feature disabled.
2019-04-08 12:55:52.19 spid10s Clearing tempdb database.
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv6> 1433].
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv4> 1433].
2019-04-08 12:55:52.21 spid18s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated ad
ministrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-04-08 12:55:52.22 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-04-08 12:55:52.40 spid10s Starting up database 'tempdb'.
2019-04-08 12:55:52.60 spid22s The Service Broker endpoint is in disabled or stopped state.
2019-04-08 12:55:52.60 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2019-04-08 12:55:52.61 spid22s Service Broker manager has started.
2019-04-08 12:55:52.90 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-04-08 13:01:45.81 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-04-08 13:01:45.85 spid52 Using 'xplog70.dll' version '2017.140.3076' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
ubuntu sql-server vps
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have an Ubuntu 16.04 VPS and started to test SQL Server on it. Installation went flawlessly and I was using it for about a month without any problems. Then I did an apt update and it didn't start. Tbh it started with this kind of error (don't remember the exact error code):
Server is in script upgrade mode. Only administrator can connect at
this time.
I was in a hurry and managed to start it with a switch I found somewhere and it was running for one more week. But today it was eating 100% of CPU time and was so slow even an application at localhost couldn't work because of timeout errors.
This is a test server only so I thought that I remove and install sql server again. I did but that didn't help either. I have installed an express version but even the mssql-conf setup was working for ~1 hour before it has started and I still can not connect remotely with management studio, ad localhost connections are slow, too. It is using 1% of cpu time now tough.
I have deleted everything from /opt/mssql before reinstalling it. Removed everything even from /var/opt/mssql and it's working now. Why I can not connect? (timeout) What could have changed since it was working very well the first time?
My VPS is a cheap virtual server with a KVM host. the VPS has 4GB RAM and 4CPU "vCore". Last log is shown below but I think it doesn't say anything interesting. How can I get back the previous good configuration and reaction time? Or how can I determine what causes it's problem?
2019-04-08 12:55:50.40 Server Microsoft SQL Server 2017 (RTM-CU14) (KB4484710) - 14.0.3076.1 (X64)
Mar 12 2019 19:29:19
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2019-04-08 12:55:50.40 Server UTC adjustment: 0:00
2019-04-08 12:55:50.41 Server (c) Microsoft Corporation.
2019-04-08 12:55:50.41 Server All rights reserved.
2019-04-08 12:55:50.41 Server Server process ID is 28.
2019-04-08 12:55:50.41 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-04-08 12:55:50.41 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-04-08 12:55:50.42 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.
2019-04-08 12:55:50.42 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-04-08 12:55:50.43 Server Detected 3277 MB of RAM. This is an informational message; no user action is required.
2019-04-08 12:55:50.43 Server Using conventional memory in the memory manager.
2019-04-08 12:55:50.54 Server Buffer pool extension is already disabled. No action is necessary.
2019-04-08 12:55:50.64 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2019-04-08 12:55:50.64 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2019-04-08 12:55:50.65 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-04-08 12:55:50.69 Server The maximum number of dedicated administrator connections for this instance is '1'
2019-04-08 12:55:50.69 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-04-08 12:55:50.70 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-04-08 12:55:50.71 Server In-Memory OLTP initialized on lowend machine.
2019-04-08 12:55:50.75 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.
2019-04-08 12:55:50.76 Server Query Store settings initialized with enabled = 1,
2019-04-08 12:55:50.77 spid7s Starting up database 'master'.
2019-04-08 12:55:50.77 Server Software Usage Metrics is disabled.
2019-04-08 12:55:51.00 spid7s 10 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.03 spid7s 1 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2019-04-08 12:55:51.04 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.45 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-04-08 12:55:51.51 Server Failed to verify the Authenticode signature of 'C:binnsecforwarder.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-04-08 12:55:51.58 spid7s SQL Trace ID 1 was started by login "sa".
2019-04-08 12:55:51.82 spid7s Server name is 'vs2558'. This is an informational message only. No user action is required.
2019-04-08 12:55:51.83 spid22s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2019-04-08 12:55:51.84 spid22s 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-04-08 12:55:51.84 spid7s Starting up database 'msdb'.
2019-04-08 12:55:51.84 spid10s Starting up database 'mssqlsystemresource'.
2019-04-08 12:55:51.84 spid10s The resource database build version is 14.00.3076. This is an informational message only. No user action is required.
2019-04-08 12:55:51.87 spid10s Starting up database 'model'.
2019-04-08 12:55:52.19 spid18s A self-generated certificate was successfully loaded for encryption.
2019-04-08 12:55:52.19 spid10s Polybase feature disabled.
2019-04-08 12:55:52.19 spid10s Clearing tempdb database.
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv6> 1433].
2019-04-08 12:55:52.20 spid18s Server is listening on [ 'any' <ipv4> 1433].
2019-04-08 12:55:52.21 spid18s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated ad
ministrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2019-04-08 12:55:52.22 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-04-08 12:55:52.40 spid10s Starting up database 'tempdb'.
2019-04-08 12:55:52.60 spid22s The Service Broker endpoint is in disabled or stopped state.
2019-04-08 12:55:52.60 spid22s The Database Mirroring endpoint is in disabled or stopped state.
2019-04-08 12:55:52.61 spid22s Service Broker manager has started.
2019-04-08 12:55:52.90 spid7s Recovery is complete. This is an informational message only. No user action is required.
2019-04-08 13:01:45.81 spid52 Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
2019-04-08 13:01:45.85 spid52 Using 'xplog70.dll' version '2017.140.3076' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
ubuntu sql-server vps
ubuntu sql-server vps
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 13:19
PerrierPerrier
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Apr 8 at 13:19
PerrierPerrier
1013
asked Apr 8 at 13:19
PerrierPerrier
1013
1013
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Perrier is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42
add a comment |
1
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42
1
1
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Perrier is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962027%2fsqlserver-on-linux-getting-very-slow%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Perrier is a new contributor. Be nice, and check out our Code of Conduct.
draft saved
draft discarded
Perrier is a new contributor. Be nice, and check out our Code of Conduct.
Perrier is a new contributor. Be nice, and check out our Code of Conduct.
Perrier is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f962027%2fsqlserver-on-linux-getting-very-slow%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Did you back up the db and the system configurations? If not you are probably out of luck. When the system reported the DB was in "script upgrade mode" and you forced it to come back up with specific flags, you took a big chance. When performance was bad, you started removing and reinstalling software to try and fix it; this probably destroyed any logs or indications of what went wrong before. Now you want us to figure out why it doesn't work? The problem is you keep making changes without understanding what exactly went wrong, you're poking at the system hoping it works properly again.
– 0xSheepdog
Apr 8 at 14:43
@0xSheepdog Yes I should have tried harder to find a proper solution to that problem instead of removing everything. But it was working very well (to this vps) and as this is just a test server so it did cost much less to reinstall than to find a solution to the problem. The second (current) issue is that after a full reinstall of sqlserver it is still not working as before. What can explain this? Bad update? Some hidden configuration file I haven't noticed? My vps host "fine tuned" something that causes this vps to be unable to run sqlserver properly?
– Perrier
Apr 8 at 18:42