Arch Linux User Repository

This current package is MSSQLServer2022.

For anyone who needs to set the compatibility level of a db to migrate to an older version, see this article:

https://learn.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=sql-server-ver16

NOTES ON libldap 2.4:

Yes there is a newer version in the official repos but the binaries do not run without this version which is listed in the dependencies by Microsoft.

If you have a problem compiling libldapV2.4, go and ask on that package page, not here.

You can get libldap V2.4 here from this AUR package:

https://aur.archlinux.org/packages/libldap24

@doctorzeus: I tested - I recomplied ldap2.4 package and reinstall mssql. I have still the same problem:

an 24 11:40:13 sqlservr[75525]: The following diagnostic information is available:
Jan 24 11:40:13 sqlservr[75525]:          Reason: 0x00000001
Jan 24 11:40:13 sqlservr[75525]:          Signal: SIGABRT - Aborted (6)
Jan 24 11:40:13 sqlservr[75525]:           Stack:
Jan 24 11:40:13 sqlservr[75525]:                  IP               Function
Jan 24 11:40:13 sqlservr[75525]:                  ---------------- --------------------------------------
Jan 24 11:40:13 sqlservr[75525]:                  00005cba5cb3c071 std::__1::bad_function_call::~bad_function_call()+0x4e361
Jan 24 11:40:13 sqlservr[75525]:                  00005cba5cb3ba36 std::__1::bad_function_call::~bad_function_call()+0x4dd26
Jan 24 11:40:13 sqlservr[75525]:                  00005cba5cb3afbf std::__1::bad_function_call::~bad_function_call()+0x4d2af
Jan 24 11:40:13 sqlservr[75525]:                  00007d3d473f4710 __sigaction+0x50
Jan 24 11:40:13 sqlservr[75525]:                  00007d3d4744483c pthread_key_delete+0x14c
Jan 24 11:40:13 sqlservr[75525]:                  00007d3d473f4668 raise+0x18
Jan 24 11:40:13 sqlservr[75525]:                  00007d3d473dc4b8 abort+0xd7
Jan 24 11:40:13 sqlservr[75525]:                  00005cba5cac3926 malloc_usable_size+0x95a6
Jan 24 11:40:13 sqlservr[75525]:         Process: 75525 - sqlservr
Jan 24 11:40:13 sqlservr[75525]:          Thread: 75881 (application thread 0x274)
Jan 24 11:40:13 sqlservr[75525]:     Instance Id: c52b62cb-06de-447e-99b4-7004d62e9798
Jan 24 11:40:13 sqlservr[75525]:        Crash Id: 2ff8c9c4-5eb6-474d-855e-86c5cde2000e
Jan 24 11:40:13 sqlservr[75525]:     Build stamp: a0f40cc5a7930f5bc46977fe25bd42d8ef3df957ea121387d5d0d11efb8b8bd

I tested that if I rollback kernel to 6.6x it works. I believe that problem is not in your package, but in mssql itself.

@BenekDlugonogi Currently on kernel 6.7 with latest packages and everything seems to be working correctly..

There was an error with the libldap24 package linking a few weeks ago but they fixed it so try recompiling and install.

@doctorzeus @jorgemota in my opinion mssql-server has problems with kernel 6.7. I even tried run sqlserver via docker - has the same result - crashes.

I had to downgrade kernel to 6.6.X series.

@doctorzeus I update libldap24 and mssql server and got same error, same trace error, Tried to downgrade mssql server and libldap24 without success, on log this is asking for dpkg, I installed and this is used to compress (maybe) log info, but cannot start mssql-server,

@topslick Yes you are meant to be using the updated libldap24 package.

Hi. There is an update of the libldap24 (AUR) package available (2.4.59-2) which can't be installed due to the dependency of mssql-server package. Would this updated libldap24 package be compatible?

I've got two kernels installed: kernel 6.6.11-2 and kernel 6.7.arch3.1. When booting on the same machine with kernel 6.6.11-2, mssql-server starts correctly. When booting to kernel 6.7.arch3.1, mssql-server refuses to boot.

** fail on kernel 6.7.arch3.1: systemctl status** jan 15 20:30:37 sqlservr[959]: Successfully captured dump: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808 jan 15 20:30:37 sqlservr[959]: Executing: /opt/mssql/bin/handle-crash.sh with parameters jan 15 20:30:37 sqlservr[959]: /opt/mssql/bin/sqlservr jan 15 20:30:37 sqlservr[959]: /opt/mssql/bin jan 15 20:30:37 sqlservr[959]: /var/opt/mssql/log/ jan 15 20:30:37 sqlservr[959]: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808 jan 15 20:30:38 sqlservr[959]: Capturing core dump and information to /var/opt/mssql/log… jan 15 20:30:38 sqlservr[959]: /opt/mssql/bin/crash-support-functions.sh: line 536: hash: dpkg: not found jan 15 20:30:40 sqlservr[959]: Dump already generated: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808, moving to /var/opt/mssql/log/core.sqlservr.2808.temp/core.sqlservr.2808.gdmp jan 15 20:30:40 sqlservr[959]: Moving logs to /var/opt/mssql/log/core.sqlservr.2808.temp/log/paldumper-debug.log jan 15 20:32:33 sqlservr[959]: /var/opt/mssql/log/core.sqlservr.01_15_2024_20_30_38.2808.tbz2 jan 15 20:32:33 systemd[1]: mssql-server.service: Main process exited, code=exited, status=1/FAILURE jan 15 20:32:33 systemd[1]: mssql-server.service: Failed with result ‘exit-code’. jan 15 20:32:33 systemd[1]: mssql-server.service: Unit process 4419 (handle-crash.sh) remains running after unit stopped. jan 15 20:32:33 systemd[1]: mssql-server.service: Unit process 2808 (sqlservr) remains running after unit stopped. jan 15 20:32:33 systemd[1]: mssql-server.service: Consumed 6.653s CPU time, 2.2G memory peak, 0B memory swap peak. jan 15 20:32:33 systemd[1]: mssql-server.service: Scheduled restart job, restart counter is at 1. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4419 (sh) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4420 (tar) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4422 (bzip2) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:35 sqlservr[4425]: 2024-01-15 20:32:35.40 Server Setup step is FORCE copying system data file ‘C:\templatedata\model_replicatedmaster.mdf’ to '/var/opt/mssql/data/model_replicatedmaste> jan 15 20:32:35 sqlservr[4425]: [178B blob data] jan 15 20:32:35 sqlservr[4425]: [162B blob data] jan 15 20:32:35 sqlservr[4425]: [160B blob data] jan 15 20:32:37 sqlservr[4425]: [102B blob data] jan 15 20:32:37 sqlservr[4425]: [43B blob data] jan 15 20:32:37 sqlservr[4425]: [44B blob data] jan 15 20:32:37 sqlservr[4425]: [40B blob data] jan 15 20:32:37 sqlservr[4425]: [152B blob data] jan 15 20:32:38 sqlservr[4423]: Successfully captured dump: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_32_38.4425 jan 15 20:32:38 sqlservr[4423]: Executing: /opt/mssql/bin/handle-crash.sh with parameters jan 15 20:32:38 sqlservr[4423]: /opt/mssql/bin/sqlservr jan 15 20:32:38 sqlservr[4423]: /opt/mssql/bin jan 15 20:32:38 sqlservr[4423]: /var/opt/mssql/log/ jan 15 20:32:38 sqlservr[4423]: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_32_38.4425 jan 15 20:32:38 sqlservr[4423]: Capturing core dump and information to /var/opt/mssql/log… jan 15 20:32:38 sqlservr[4423]: /opt/mssql/bin/crash-support-functions.sh: line 536: hash: dpkg: not found jan 15 20:32:39 sqlservr[4423]: Dump already generated: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_32_38.4425, moving to /var/opt/mssql/log/core.sqlservr.4425.temp/core.sqlservr.4425.gdmp jan 15 20:32:39 sqlservr[4423]: Moving logs to /var/opt/mssql/log/core.sqlservr.4425.temp/log/paldumper-debug.log jan 15 20:32:39 sqlservr[4423]: /var/opt/mssql/log/core.sqlservr.01_15_2024_20_32_38.4425.tbz2 jan 15 20:32:39 systemd[1]: mssql-server.service: Main process exited, code=exited, status=1/FAILURE

fail on kernel 6.7.arch3.1: journalctl jan 15 20:30:37 sqlservr[959]: Successfully captured dump: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808 jan 15 20:30:37 sqlservr[959]: Executing: /opt/mssql/bin/handle-crash.sh with parameters jan 15 20:30:37 sqlservr[959]: /opt/mssql/bin/sqlservr jan 15 20:30:37 sqlservr[959]: /opt/mssql/bin jan 15 20:30:37 sqlservr[959]: /var/opt/mssql/log/ jan 15 20:30:37 sqlservr[959]: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808 jan 15 20:30:38 sqlservr[959]: Capturing core dump and information to /var/opt/mssql/log… jan 15 20:30:38 sqlservr[959]: /opt/mssql/bin/crash-support-functions.sh: line 536: hash: dpkg: not found jan 15 20:30:40 sqlservr[959]: Dump already generated: /var/opt/mssql/log/core.sqlservr.1_15_2024_20_30_36.2808, moving to /var/opt/mssql/log/core.sqlservr.2808.temp/core.sqlservr.2808.gdmp jan 15 20:30:40 sqlservr[959]: Moving logs to /var/opt/mssql/log/core.sqlservr.2808.temp/log/paldumper-debug.log jan 15 20:32:33 sqlservr[959]: /var/opt/mssql/log/core.sqlservr.01_15_2024_20_30_38.2808.tbz2 jan 15 20:32:33 systemd[1]: mssql-server.service: Main process exited, code=exited, status=1/FAILURE jan 15 20:32:33 systemd[1]: mssql-server.service: Failed with result ‘exit-code’. jan 15 20:32:33 systemd[1]: mssql-server.service: Unit process 4419 (handle-crash.sh) remains running after unit stopped. jan 15 20:32:33 systemd[1]: mssql-server.service: Unit process 2808 (sqlservr) remains running after unit stopped. jan 15 20:32:33 systemd[1]: mssql-server.service: Consumed 6.653s CPU time, 2.2G memory peak, 0B memory swap peak. jan 15 20:32:33 systemd[1]: mssql-server.service: Scheduled restart job, restart counter is at 1. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4419 (sh) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4420 (tar) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:33 systemd[1]: mssql-server.service: Found left-over process 4422 (bzip2) in control group while starting unit. Ignoring. jan 15 20:32:33 systemd[1]: mssql-server.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. jan 15 20:32:35 sqlservr[4425]: 2024-01-15 20:32:35.40 Server Setup step is FORCE copying system data file ‘C:\templatedata\model_replicatedmaster.mdf’ to ‘/var/opt/mssql/data/model_replicatedmaster.mdf’. jan 15 20:32:35 sqlservr[4425]: [178B blob data] jan 15 20:32:35 sqlservr[4425]: [162B blob data] jan 15 20:32:35 sqlservr[4425]: [160B blob data] jan 15 20:32:37 sqlservr[4425]: [102B blob data] jan 15 20:32:37 sqlservr[4425]: [43B blob data] jan 15 20:32:37 sqlservr[4425]: [44B blob data] jan 15 20:32:37 sqlservr[4425]: [40B blob data] jan 15 20:32:37 sqlservr[4425]: [152B blob data]

** success on kernel 6.6.11-2 : systemctl status ** ● mssql-server.service - Microsoft SQL Server Database Engine Loaded: loaded (/usr/lib/systemd/system/mssql-server.service; enabled; pre> Active: active (running) since Mon 2024-01-15 21:04:51 CET; 11min ago Docs: https://docs.microsoft.com/en-us/sql/linux Main PID: 956 (sqlservr) Tasks: 288 Memory: 2.4G (peak: 2.4G) CPU: 34.328s CGroup: /system.slice/mssql-server.service ├─ 956 /opt/mssql/bin/sqlservr └─2798 /opt/mssql/bin/sqlservr

jan 15 21:07:23 sqlservr[2798]: [59B blob data] jan 15 21:07:23 sqlservr[2798]: [58B blob data] jan 15 21:07:23 sqlservr[2798]: [56B blob data] jan 15 21:07:23 sqlservr[2798]: [57B blob data] jan 15 21:07:23 sqlservr[2798]: [53B blob data] jan 15 21:07:23 sqlservr[2798]: [124B blob data] jan 15 21:10:45 sqlservr[2798]: [76B blob data] jan 15 21:10:45 sqlservr[2798]: [75B blob data] jan 15 21:12:41 sqlservr[2798]: [156B blob data] jan 15 21:12:42 sqlservr[2798]: [195B blob data]

can you depend on libldap24 instead of libldap?

I cant install the software anymore it says:

No AUR package found for libldap<=2.4.59 -> could not find all required packages: libldap <=2.4.59

A non-blocking warning is showed when building the package (16.0.4065.3-1).

==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
strip: ./opt/mssql/bin/paldumper.ds92ei[.gnu.build.attributes.hot]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/paldumper.ds92ei[.gnu.build.attributes.unlikely]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/paldumper.ds92ei[.gnu.build.attributes.startup]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/paldumper.ds92ei[.gnu.build.attributes.exit]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/sqlservr.hbrknu[.gnu.build.attributes.hot]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/sqlservr.hbrknu[.gnu.build.attributes.unlikely]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/sqlservr.hbrknu[.gnu.build.attributes.startup]: error: failed to locate merged notes: cause of error unknown
strip: ./opt/mssql/bin/sqlservr.hbrknu[.gnu.build.attributes.exit]: error: failed to locate merged notes: cause of error unknown
  -> Compressing man and info pages...

Not sure if this is an issue, or if this can be ignored.

@SL_Pirate There is a post-install message that says you need to run "/opt/mssql/bin/mssql-conf setup" if this is your first time setup.