Failed to start Microsoft SQL Server Database Engine

L9dson

New Member
Joined
Nov 9, 2022
Messages
1
Reaction score
0
Credits
35
Hello people, I'm just installed my vanilla Arch linux, I was using an Arch distro pre-built ( comes with programs, packages, etc ), the good thing is that I was able to start and enable mssql-server fine, without any problem, but when I did my installation of arch by myself and install all the necessary packages to install mssql-server, msodbcsql, mssql-tools it fails to start, IDK why.

This is what I get when the installation of mssql-server done:



This program has encountered a fatal error and cannot continue running at Wed Nov 9 00:50:42 2022
The following diagnostic information is available:
Reason: 0x00000001
Signal: SIGSEGV - Segmentation fault (11)
Stack:
IP Function
---------------- --------------------------------------
000055d4dfe6cccc <unknown>
000055d4dfe6c712 <unknown>
000055d4dfe93046 <unknown>
000055d4dfe15fab <unknown>
00007f207044ca00 __sigaction+0x50
0000000000000000 <unknown>
000055d4dfe1e4ae <unknown>
000055d4dfe12254 <unknown>
000055d4dfe12079 <unknown>
Process: 12850 - sqlservr
Thread: 12973 (application thread 0x208)
Instance Id: edbf95e1-2003-46eb-8c32-c2303baef33a
Crash Id: 2db9c43d-a3af-4032-a619-c1f35d8171e7
Build stamp: f16f9a0c0de9e451372b68d715395767a0605312e847c4dccce5b2784118cab9
Distribution: Arch Linux
Processors: 4
Total Memory: 16731717632 bytes
Timestamp: Wed Nov 9 00:50:42 2022


----------------
I got all these other messages when I try to start it:

× mssql-server.service - Microsoft SQL Server Database Engine
Loaded: loaded (/usr/lib/systemd/system/mssql-server.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2022-11-09 01:40:18 AST; 3min 20s ago
Duration: 15.605s
Docs: https://docs.microsoft.com/en-us/sql/linux
Process: 34417 ExecStart=/opt/mssql/bin/sqlservr (code=exited, status=1/FAILURE)
Main PID: 34417 (code=exited, status=1/FAILURE)
CPU: 2min 39.780s

nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 33490 (sh) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 33491 (tar) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 33492 (bzip2) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 34415 (sh) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 34416 (tar) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 34418 (bzip2) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 35346 (sh) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 35347 (tar) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: mssql-server.service: Unit process 35348 (bzip2) remains running after unit stopped.
nov 09 01:40:30 arch-pc systemd[1]: Failed to start Microsoft SQL Server Database Engine.

YAML:
Configuring SQL Server...

This program has encountered a fatal error and cannot continue running at Wed Nov  9 00:50:42 2022
The following diagnostic information is available:

         Reason: 0x00000001
         Signal: SIGSEGV - Segmentation fault (11)
          Stack:
                 IP               Function
                 ---------------- --------------------------------------
                 000055d4dfe6cccc <unknown>
                 000055d4dfe6c712 <unknown>
                 000055d4dfe93046 <unknown>
                 000055d4dfe15fab <unknown>
                 00007f207044ca00 __sigaction+0x50
                 0000000000000000 <unknown>
                 000055d4dfe1e4ae <unknown>
                 000055d4dfe12254 <unknown>
                 000055d4dfe12079 <unknown>
        Process: 12850 - sqlservr
         Thread: 12973 (application thread 0x208)
    Instance Id: edbf95e1-2003-46eb-8c32-c2303baef33a
       Crash Id: 2db9c43d-a3af-4032-a619-c1f35d8171e7
    Build stamp: f16f9a0c0de9e451372b68d715395767a0605312e847c4dccce5b2784118cab9
   Distribution: Arch Linux
     Processors: 4
   Total Memory: 16731717632 bytes
      Timestamp: Wed Nov  9 00:50:42 2022
Capturing a dump of 12850
Successfully captured dump: /var/opt/mssql/log/core.sqlservr.11_9_2022_0_50_42.12850
Executing: /opt/mssql/bin/handle-crash.sh with parameters
     handle-crash.sh
     /opt/mssql/bin/sqlservr
     12850
     /opt/mssql/bin
     /var/opt/mssql/log/
    
     edbf95e1-2003-46eb-8c32-c2303baef33a
     2db9c43d-a3af-4032-a619-c1f35d8171e7
    
     /var/opt/mssql/log/core.sqlservr.11_9_2022_0_50_42.12850

Arch Linux
Capturing core dump and information to /var/opt/mssql/log...
dmesg: read kernel buffer failed: Operation not permitted
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
mié 09 nov 2022 00:50:44 AST Capturing program information
Dump already generated: /var/opt/mssql/log/core.sqlservr.11_9_2022_0_50_42.12850, moving to /var/opt/mssql/log/core.sqlservr.12850.temp/core.sqlservr.12850.gdmp
Moving logs to /var/opt/mssql/log/core.sqlservr.12850.temp/log/paldumper-debug.log
mié 09 nov 2022 00:50:44 AST Capturing program binaries
/usr/bin/find: ‘/usr/share/polkit-1/rules.d’: Permission denied
mié 09 nov 2022 00:50:49 AST Compressing the dump files
Core dump and information are being compressed in the background. When
complete, they can be found in the following location:
  /var/opt/mssql/log/core.sqlservr.11_09_2022_00_50_43.12850.tbz2
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
 

Members online


Top