Proxmox 9 Microsoft SQL Server bug

R

rozir

New Member
Nov 17, 2025
1
0
1
Hello,
I recently updated my PVE to version 9, and two Microsoft SQL Server services that I have hosted are not starting correctly.
Tests I’ve already done:


  1. I used the services on version 7 and they worked
  2. I updated the same PVE directly to version 8 without formatting and it worked
  3. I updated the same PVE directly to version 9 without formatting and it stopped working
  4. I formatted, installed version 9, and it didn’t work

These made me believe that version 9 is what is causing all of this.


I use the command /opt/mssql/bin/sqlservr $>/dev/null & to start the service, and when it works it doesn’t return an error, but in the new version it returns the following error: “another instance of the application is already running.”
 
Do you have any more detailed information? I am currently trying to install mssql on Ubuntu 22.04 and 24.04 lxc and I am getting the same error. I will try testing the VM version, as it works normally in hyperv.

Code: 
Configuring SQL Server...

This program has encountered a fatal error and cannot continue running at Tue Nov 18 19:02:17 2025
The following diagnostic information is available:

         Reason: 0x00000004
        Message: ASSERT: Expression=(NT_SUCCESS(status)) File=LibOS\Windows\Kernel\DRtl\sqlpalstubs.cpp Line=886
    Stack Trace:
                 file://package6/windows/system32/sqlpal.dll+0x000000000000A5F2
                 file://package6/windows/system32/sqlpal.dll+0x0000000000009925
                 file://package6/windows/system32/sqlpal.dll+0x0000000000005584
                 file://package6/windows/system32/sqlpal.dll+0x0000000000005412
                 file://package6/windows/system32/sqlpal.dll+0x00000000000E85B4
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AA761
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AAE14
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AA35A
                 file://package6/windows/system32/sqlpal.dll+0x00000000000AC780
                 file://package6/windows/system32/sqlpal.dll+0x0000000000006FDC
                 file://package6/windows/system32/sqlpal.dll+0x00000000000065CE
                 file://package6/windows/system32/sqlpal.dll+0x0000000000006A69
                 file://package6/windows/system32/sqlpal.dll+0x0000000000121971
        Process: 14210 - sqlservr
         Thread: 14216 (application thread 0x8)
    Instance Id: bc9c6e89-6207-4e3a-9752-221f3a0880c3
       Crash Id: a8fe9830-4fee-4c31-af64-bf52496ab73e
    Build stamp: 68fb651789e5eaff8dbeb34fba53539d76bf4fc3c91a43b61b127ec2a166ab3c
   Distribution: Ubuntu 22.04.5 LTS
     Processors: 2
   Total Memory: 16505700352 bytes
      Timestamp: Tue Nov 18 19:02:17 2025
     Last errno: 22
Last errno text: Invalid argument
Capturing a dump of 14210
FAILED to capture a dump. Details in paldumper log.
Executing: /opt/mssql/bin/handle-crash.sh with parameters
     handle-crash.sh
     /opt/mssql/bin/sqlservr
     14210
     /opt/mssql/bin
     /var/opt/mssql/log/
    
     bc9c6e89-6207-4e3a-9752-221f3a0880c3
     a8fe9830-4fee-4c31-af64-bf52496ab73e
    
    

Ubuntu 22.04.5 LTS
Capturing core dump and information to /var/opt/mssql/log...
Capture info: Kernel Version
Capture info: OS release
Capture info: System memory information
Capture info: Command line
Capture info: Start Time
Capture info: Process limits
Capture info: Thread list
Capture info: Processor topology
Capture info: Process mounts
Capture info: Process statistics
Capture info: Process status
Capture info: Process memory maps
Capture info: Process memory maps (detailed)
Capture info: Core Dump filter
Capture info: Process CGroup information
cat: /sys/fs/cgroup/user.slice/user-999.slice/session-1817.scope/memory.reclaim: Permission denied
Capture info: Process scheduler information
Capture info: Process list
Capture info: Process handle information
Capture info: Process environment variables
Capture info: System package list (dpkg)
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' 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' can see all messages.
      Pass -q to turn off this notice.
No journal files were opened due to insufficient permissions.
tail: cannot open '/var/log/syslog' for reading: Permission denied
Capture info: Current application configuration
Tue Nov 18 19:02:18 CET 2025 Capturing program information
Tue Nov 18 19:02:18 CET 2025 Attempting to capture a dump with paldumper for pid 14210
WARNING: Capture attempt failure detected
Attempting to capture a filtered dump with paldumper for pid 14210
WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.14210.temp/log/paldumper-debug.log for details
Tue Nov 18 19:02:18 CET 2025 Attempting to capture a dump with gdb
WARNING: Unable to capture crash dump with GDB. You may need to
allow ptrace debugging, enable the CAP_SYS_PTRACE capability, or
run as root. See log in: /var/opt/mssql/log/core.sqlservr.14210.temp/log/gdb.log
Tue Nov 18 19:02:18 CET 2025 Capturing program binaries
Tue Nov 18 19:02:18 CET 2025 Compressing the dump files
Core dump and information are being compressed (bzip2) in
the background. When complete, they can be found in the following location:
  /var/opt/mssql/log/core.sqlservr.11_18_2025_19_02_17.14210.tbz2
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
 
You must log in or register to reply here.
Top Bottom