SIGABRT - Aborted (6) - Ubuntu 24.04 host and sqlserver preview 2022/ ubuntu 20.04

[AlexandreHGuerra]

hi

im aware that there were some issues with kernel 6.8 with sql server, reported on the other distributions, that seems solved... but , im curious about which kernel interfaces may still have issues with ubuntu 24.04 / 22.04.03

very standard docker run command still fails on ubuntu 24.04

root@xx-desktop:~# uname -a Linux xx-desktop 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux root@xx-desktop:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS"

docker run -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=Pxxxxxxxx" -e "MSSQL_PID=Evaluation" -p 1433:1433 --name sqlpreview --hostname sqlpreview -d mcr.microsoft.com/mssql/server:2022-preview-ubuntu-22.04

root@xxx-desktop:~# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 3c047db268ec mcr.microsoft.com/mssql/server:2022-preview-ubuntu-22.04 "/opt/mssql/bin/perm…" 10 hours ago Exited (1) 10 hours ago sqlpreview

docker logs sqlpreview

This container is running as user mssql. To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216. This program has encountered a fatal error and cannot continue running at Thu May 16 04:19:24 2024 The following diagnostic information is available:

     Reason: 0x00000001
     Signal: SIGABRT - Aborted (6)
      Stack:
             IP               Function
             ---------------- --------------------------------------
             0000584fc9507301 std::__1::bad_function_call::~bad_function_call()+0x964b1
             0000584fc9506cc6 std::__1::bad_function_call::~bad_function_call()+0x95e76
             0000584fc950624f std::__1::bad_function_call::~bad_function_call()+0x953ff
             0000705c18964520 __sigaction+0x50
             0000705c189b8a7c pthread_kill+0x12c
             0000705c18964476 raise+0x16
             0000705c1894a7f3 abort+0xd3
             0000584fc94d8566 std::__1::bad_function_call::~bad_function_call()+0x67716
             0000584fc9514bd4 std::__1::bad_function_call::~bad_function_call()+0xa3d84
             0000584fc9542938 std::__1::bad_function_call::~bad_function_call()+0xd1ae8
             0000584fc954271a std::__1::bad_function_call::~bad_function_call()+0xd18ca
             0000584fc94de9da std::__1::bad_function_call::~bad_function_call()+0x6db8a
             0000584fc94de650 std::__1::bad_function_call::~bad_function_call()+0x6d800
    Process: 9 - sqlservr
     Thread: 120 (application thread 0x1d4)
Instance Id: b311627b-c10d-4ca9-ad6c-42e5ac48771e
   Crash Id: 39b6166e-284b-40b4-b328-88a40aa8b86e
Build stamp: cfa79b44134f84a9294d1b40dd338f1160bb96647794fa288061980597e6189d

Distribution: Ubuntu 22.04.3 LTS Processors: 16 Total Memory: 33579151360 bytes Timestamp: Thu May 16 04:19:24 2024 Last errno: 2 Last errno text: No such file or directory Capturing a dump of 9 Successfully captured dump: /var/opt/mssql/log/core.sqlservr.5_16_2024_4_19_24.9 Executing: /opt/mssql/bin/handle-crash.sh with parameters handle-crash.sh /opt/mssql/bin/sqlservr 9 /opt/mssql/bin /var/opt/mssql/log/

 b311627b-c10d-4ca9-ad6c-42e5ac48771e
 39b6166e-284b-40b4-b328-88a40aa8b86e

 /var/opt/mssql/log/core.sqlservr.5_16_2024_4_19_24.9

Ubuntu 22.04.3 LTS Capturing core dump and information to /var/opt/mssql/log... /bin/cat: /proc/9/maps: Permission denied cat: /proc/9/environ: Permission denied find: '/proc/9/task/9/fdinfo': Permission denied find: '/proc/9/task/11/fdinfo': Permission denied find: '/proc/9/task/12/fdinfo': Permission denied find: '/proc/9/task/13/fdinfo': Permission denie

[halida]

similar issue, sqlserver cannot run under ubuntu 24.04

[ceari]

mcr.microsoft.com/mssql/server:2022-CU13-ubuntu-22.04 and mcr.microsoft.com/mssql/server:2022-latest both work for me on a Ubuntu 24.04 host.

[martynas-m]

the problem is general in any linux distro with latest kernel (lts is working), and as far as sql server itself, I think they fixed this issue maybe 4 or 5 months ago, so it seems that only thing is needed to repack docker image with latest version of sql server... Also people write that with 2017 version it is fixed both in plain and docker versions, but apparently for Microsoft team to build new docker image 5 months is a bit to complex work to complete...

[BuriedStPatrick]

This kernel-problem keeps popping up with every kernel release and it undermines the portable aspect of running this containerized. Does anyone know if there are plans to fix the underlying problem for good or if it's even possible? I haven't experienced this problem with any other Docker image I've used through the years.

It has quite a large knock-on effect in that upgrading our CI build agents will result in broken integration tests. And not at all transparent to the end-user what the problem is.