patternsqlMinor
initdata: No memory for kernel buffers
Viewed 0 times
buffersformemoryinitdatakernel
Problem
I recently upgraded my SQL Server 2017 Developer Edition on RedHat Enterprise Linux 7.6 to SQL Server 2019 CTP 3.0.
The mssql-server service will no longer start. /var/opt/mssql/log/errorlog shows the following:
2019-06-12 09:36:31.98 Server Microsoft SQL Server 2019 (CTP3.0) - 15.0.1600.8 (X64)
May 17 2019 00:56:19
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Linux (Red Hat Enterprise Linux)
2019-06-12 09:36:32.04 Server UTC adjustment: -5:00
2019-06-12 09:36:32.05 Server (c) Microsoft Corporation.
2019-06-12 09:36:32.07 Server All rights reserved.
2019-06-12 09:36:32.08 Server Server process ID is 32.
2019-06-12 09:36:32.09 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-06-12 09:36:32.10 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-06-12 09:36:32.15 Server Command Line Startup Parameters:
--accept-eula
2019-06-12 09:36:32.18 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-06-12 09:36:32.20 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-06-12 09:36:32.23 Server Detected 7856 MB of RAM. This is an informational message; no user action is required.
2019-06-12 09:36:32.24 Server Using conventional memory in the memory manager.
2019-06-12 09:36:32.28 Server Buffer pool extension is not supported on Linux platform.
2019-06-12 09:36:32.29 Server Error: 17128, Severity: 16, State: 1.
2019-06-12 09:36:32.29 Server initdata: No memory for
The mssql-server service will no longer start. /var/opt/mssql/log/errorlog shows the following:
2019-06-12 09:36:31.98 Server Microsoft SQL Server 2019 (CTP3.0) - 15.0.1600.8 (X64)
May 17 2019 00:56:19
Copyright (C) 2019 Microsoft Corporation
Developer Edition (64-bit) on Linux (Red Hat Enterprise Linux)
2019-06-12 09:36:32.04 Server UTC adjustment: -5:00
2019-06-12 09:36:32.05 Server (c) Microsoft Corporation.
2019-06-12 09:36:32.07 Server All rights reserved.
2019-06-12 09:36:32.08 Server Server process ID is 32.
2019-06-12 09:36:32.09 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2019-06-12 09:36:32.10 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-06-12 09:36:32.15 Server Command Line Startup Parameters:
--accept-eula
2019-06-12 09:36:32.18 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2019-06-12 09:36:32.20 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-06-12 09:36:32.23 Server Detected 7856 MB of RAM. This is an informational message; no user action is required.
2019-06-12 09:36:32.24 Server Using conventional memory in the memory manager.
2019-06-12 09:36:32.28 Server Buffer pool extension is not supported on Linux platform.
2019-06-12 09:36:32.29 Server Error: 17128, Severity: 16, State: 1.
2019-06-12 09:36:32.29 Server initdata: No memory for
Solution
So, being the smarty-pants I am, I thought it would be easier to just login to my RHEL system as root, then I wouldn't need to
Turns out that was a mistake.
I was able to fix my install by logging in using my "normal" Linux account, then run sudo commands per the docs to remove and re-install SQL Server binaries from the Microsoft repo. I also needed to run the following commands to reset ownership and group-membership for filesystem objects for my existing /var/opt/mssql/* folders:
Moral of the story, don't shoot yourself in the foot. It hurts. Oh well, I guess I've got another small chapter for my book:
Adventures in Linux, AKA, It's NEVER going to be the year of Linux on the desktop.
sudo every time.Turns out that was a mistake.
I was able to fix my install by logging in using my "normal" Linux account, then run sudo commands per the docs to remove and re-install SQL Server binaries from the Microsoft repo. I also needed to run the following commands to reset ownership and group-membership for filesystem objects for my existing /var/opt/mssql/* folders:
chown -R mssql /var/opt/mssql/*
chgrp -R mssql /var/opt/mssql/*Moral of the story, don't shoot yourself in the foot. It hurts. Oh well, I guess I've got another small chapter for my book:
Adventures in Linux, AKA, It's NEVER going to be the year of Linux on the desktop.
Code Snippets
chown -R mssql /var/opt/mssql/*
chgrp -R mssql /var/opt/mssql/*Context
StackExchange Database Administrators Q#240756, answer score: 2
Revisions (0)
No revisions yet.