合 MSSQL创建容器报错This program has encountered a fatal error and cannot continue running

2023年6月9日  

0    359    1

Tags： 故障处理MSSQLSQL ServerDocker

👉 本文共约222个字，系统预计阅读时间或需1分钟。

显示/隐藏全文目录

目录

• 现象
• 分析
• 解决

现象

SQL SERVER 2022使用docker创建数据库，发现闪退，报错信息：

[root@lhrdb ~]# docker logs -f mssql2022 /opt/mssql/bin/permissions_check.sh: line 4: [: : integer expression expected /opt/mssql/bin/permissions_check.sh: line 59: [: : integer expression expected SQL Server 2022 will run as non-root by default. 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 Wed Jun 7 12:09:30 2023 The following diagnostic information is available: Reason: 0x00000001 Signal: SIGABRT - Aborted (6) Stack: IP Function ---------------- -------------------------------------- 000055bf505c65b2 <unknown> 000055bf505c5fd0 <unknown> 000055bf505c566f <unknown> 00007f3d98171090 killpg+0x40 00007f3d9817100b gsignal+0xcb 00007f3d98150859 abort+0x12b 000055bf5056bf76 <unknown> 000055bf505f6eba <unknown> Process: 9 - sqlservr Thread: 14 (application thread 0x8) Instance Id: dd6337d2-bf51-4157-855a-c8a383dce222 Crash Id: 95aed7be-431e-4dd8-9bb2-6569adf8ec8a Build stamp: d81e9b6de06534e649bd57dd609aa3050f5e380f361b7f8a80a80eeb71e7422c Distribution: Ubuntu 20.04.5 LTS Processors: 16 Total Memory: 67385356288 bytes Timestamp: Wed Jun 7 12:09:30 2023 Last errno: 2 Last errno text: No such file or directory Capturing a dump of 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/ dd6337d2-bf51-4157-855a-c8a383dce222 95aed7be-431e-4dd8-9bb2-6569adf8ec8a FAILED to capture a dump. Details in paldumper log. Ubuntu 20.04.5 LTS Capturing core dump and information to /var/opt/mssql/log... /bin/cat: /proc/9/maps: Permission denied /bin/cat: /proc/9/environ: Permission denied /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted dmesg: read kernel buffer failed: Operation not permitted /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory Wed Jun 7 12:09:32 CST 2023 Capturing program information Wed Jun 7 12:09:32 CST 2023 Attempting to capture a dump with paldumper for pid 9 WARNING: Capture attempt failure detected Attempting to capture a filtered dump with paldumper for pid 9 WARNING: Attempt to capture dump failed. Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details Wed Jun 7 12:09:32 CST 2023 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.9.temp/log/gdb.log Wed Jun 7 12:09:32 CST 2023 Capturing program binaries Wed Jun 7 12:09:32 CST 2023 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d [root@lhrdb ~]# [root@lhrdb ~]# [root@lhrdb ~]# find / -name paldumper-debug.log find: ‘/proc/3235025’: No such file or directory find: ‘/proc/3235084’: No such file or directory find: ‘/proc/3235089’: No such file or directory find: ‘/proc/3235121’: No such file or directory /var/lib/docker/overlay2/e55af81b8aae6d753b16525898d0f6fb2a97343a9d954bdd1b491748188ae2ca/diff/var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d/log/paldumper-debug.log [root@lhrdb ~]# more /var/lib/docker/overlay2/e55af81b8aae6d753b16525898d0f6fb2a97343a9d954bdd1b491748188ae2ca/diff/var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d/log/paldumper-debug.log 06/07/2023 12:09:32.418600096 Info [paldumper] <0000000220/0x00000000> Executing PalDumper against PID: 9 06/07/2023 12:09:32.418742204 Info [paldumper] <0000000220/0x00000000> Dump type: miniplus 06/07/2023 12:09:32.418756319 Info [paldumper] <0000000220/0x00000000> Stopping target 06/07/2023 12:09:32.418779248 Info [paldumper] <0000000220/0x00000000> Target stopped 06/07/2023 12:09:32.418793778 Info [paldumper] <0000000220/0x00000000> Attaching to target threads 06/07/2023 12:09:32.418826386 Warning [paldumper] <0000000220/0x00000000> Yama PTRACE mode: 0-Classic 06/07/2023 12:09:32.418894704 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=9 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418908466 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418930591 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=11 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418942186 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418963879 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=12 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418975706 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418997736 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=13 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.419009303 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419031142 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=14 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.419042699 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419063472 Error [paldumper] <0000000220/0x00000000> Attempt to trace target failed. 06/07/2023 12:09:32.419075338 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419175522 Error [paldumper] <0000000220/0x00000000> Reference previous log messages. 06/07/2023 12:09:32.419189622 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438196076 Info [paldumper] <0000000222/0x00000000> Executing PalDumper against PID: 9 06/07/2023 12:09:32.438366302 Info [paldumper] <0000000222/0x00000000> Dump type: filtered 06/07/2023 12:09:32.438378529 Info [paldumper] <0000000222/0x00000000> Stopping target 06/07/2023 12:09:32.438397424 Info [paldumper] <0000000222/0x00000000> Target stopped 06/07/2023 12:09:32.438409790 Info [paldumper] <0000000222/0x00000000> Attaching to target threads 06/07/2023 12:09:32.438439384 Warning [paldumper] <0000000222/0x00000000> Yama PTRACE mode: 0-Classic 06/07/2023 12:09:32.438499231 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=9 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438510701 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438529534 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=11 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438539925 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438558645 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=12 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438568678 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438587233 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=13 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438597193 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438615681 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=14 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438625561 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438652088 Error [paldumper] <0000000222/0x00000000> Attempt to trace target failed. 06/07/2023 12:09:32.438662675 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438672966 Error [paldumper] <0000000222/0x00000000> Reference previous log messages. 06/07/2023 12:09:32.438682981 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117

[root@lhrdb ~]# docker logs -f mssql2022 /opt/mssql/bin/permissions_check.sh: line 4: [: : integer expression expected /opt/mssql/bin/permissions_check.sh: line 59: [: : integer expression expected SQL Server 2022 will run as non-root by default. 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 Wed Jun  7 12:09:30 2023 The following diagnostic information is available:            Reason: 0x00000001          Signal: SIGABRT - Aborted (6)           Stack:                  IP               Function                  ---------------- --------------------------------------                  000055bf505c65b2 <unknown>                  000055bf505c5fd0 <unknown>                  000055bf505c566f <unknown>                  00007f3d98171090 killpg+0x40                  00007f3d9817100b gsignal+0xcb                  00007f3d98150859 abort+0x12b                  000055bf5056bf76 <unknown>                  000055bf505f6eba <unknown>         Process: 9 - sqlservr          Thread: 14 (application thread 0x8)     Instance Id: dd6337d2-bf51-4157-855a-c8a383dce222        Crash Id: 95aed7be-431e-4dd8-9bb2-6569adf8ec8a     Build stamp: d81e9b6de06534e649bd57dd609aa3050f5e380f361b7f8a80a80eeb71e7422c    Distribution: Ubuntu 20.04.5 LTS      Processors: 16    Total Memory: 67385356288 bytes       Timestamp: Wed Jun  7 12:09:30 2023      Last errno: 2 Last errno text: No such file or directory Capturing a dump of 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/        dd6337d2-bf51-4157-855a-c8a383dce222      95aed7be-431e-4dd8-9bb2-6569adf8ec8a   FAILED to capture a dump. Details in paldumper log.   Ubuntu 20.04.5 LTS Capturing core dump and information to /var/opt/mssql/log... /bin/cat: /proc/9/maps: Permission denied /bin/cat: /proc/9/environ: Permission denied /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted /usr/bin/find: '/proc/9/map_files': Operation not permitted dmesg: read kernel buffer failed: Operation not permitted /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory /usr/bin/timeout: failed to run command '/bin/journalctl': No such file or directory Wed Jun  7 12:09:32 CST 2023 Capturing program information Wed Jun  7 12:09:32 CST 2023 Attempting to capture a dump with paldumper for pid 9 WARNING: Capture attempt failure detected Attempting to capture a filtered dump with paldumper for pid 9 WARNING: Attempt to capture dump failed.  Reference /var/opt/mssql/log/core.sqlservr.9.temp/log/paldumper-debug.log for details Wed Jun  7 12:09:32 CST 2023 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.9.temp/log/gdb.log Wed Jun  7 12:09:32 CST 2023 Capturing program binaries Wed Jun  7 12:09:32 CST 2023 Not compressing the dump files, moving instead to: /var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d [root@lhrdb ~]# [root@lhrdb ~]# [root@lhrdb ~]# find / -name paldumper-debug.log find: ‘/proc/3235025’: No such file or directory find: ‘/proc/3235084’: No such file or directory find: ‘/proc/3235089’: No such file or directory find: ‘/proc/3235121’: No such file or directory /var/lib/docker/overlay2/e55af81b8aae6d753b16525898d0f6fb2a97343a9d954bdd1b491748188ae2ca/diff/var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d/log/paldumper-debug.log [root@lhrdb ~]# more /var/lib/docker/overlay2/e55af81b8aae6d753b16525898d0f6fb2a97343a9d954bdd1b491748188ae2ca/diff/var/opt/mssql/log/core.sqlservr.06_07_2023_12_09_30.9.d/log/paldumper-debug.log 06/07/2023 12:09:32.418600096 Info [paldumper] <0000000220/0x00000000> Executing PalDumper against PID: 9 06/07/2023 12:09:32.418742204 Info [paldumper] <0000000220/0x00000000>                       Dump type: miniplus 06/07/2023 12:09:32.418756319 Info [paldumper] <0000000220/0x00000000> Stopping target 06/07/2023 12:09:32.418779248 Info [paldumper] <0000000220/0x00000000> Target stopped 06/07/2023 12:09:32.418793778 Info [paldumper] <0000000220/0x00000000> Attaching to target threads 06/07/2023 12:09:32.418826386 Warning [paldumper] <0000000220/0x00000000> Yama PTRACE mode: 0-Classic 06/07/2023 12:09:32.418894704 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=9 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418908466 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418930591 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=11 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418942186 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418963879 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=12 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.418975706 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.418997736 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=13 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.419009303 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419031142 Error [paldumper] <0000000220/0x00000000> Attempt to execute ptrace command (16) for pid=14 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.419042699 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419063472 Error [paldumper] <0000000220/0x00000000> Attempt to trace target failed. 06/07/2023 12:09:32.419075338 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.419175522 Error [paldumper] <0000000220/0x00000000> Reference previous log messages. 06/07/2023 12:09:32.419189622 Error [paldumper] <0000000220/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438196076 Info [paldumper] <0000000222/0x00000000> Executing PalDumper against PID: 9 06/07/2023 12:09:32.438366302 Info [paldumper] <0000000222/0x00000000>                       Dump type: filtered 06/07/2023 12:09:32.438378529 Info [paldumper] <0000000222/0x00000000> Stopping target 06/07/2023 12:09:32.438397424 Info [paldumper] <0000000222/0x00000000> Target stopped 06/07/2023 12:09:32.438409790 Info [paldumper] <0000000222/0x00000000> Attaching to target threads 06/07/2023 12:09:32.438439384 Warning [paldumper] <0000000222/0x00000000> Yama PTRACE mode: 0-Classic 06/07/2023 12:09:32.438499231 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=9 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438510701 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438529534 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=11 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438539925 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438558645 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=12 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438568678 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438587233 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=13 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438597193 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438615681 Error [paldumper] <0000000222/0x00000000> Attempt to execute ptrace command (16) for pid=14 failed - EPERM process cannot be traced. 06/07/2023 12:09:32.438625561 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438652088 Error [paldumper] <0000000222/0x00000000> Attempt to trace target failed. 06/07/2023 12:09:32.438662675 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001 06/07/2023 12:09:32.438672966 Error [paldumper] <0000000222/0x00000000> Reference previous log messages. 06/07/2023 12:09:32.438682981 Error [paldumper] <0000000222/0x00000000> errno: 0x00000001

分析

该镜像在其它OS都可以使用，几经搜索无效，，，

本人提供Oracle(OCP、OCM)、MySQL(OCP)、PostgreSQL(PGCA、PGCE、PGCM)等数据库的培训和考证业务，私聊QQ646634621或微信dbaup66，谢谢！

后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！

验证码：

获取验证码： 请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。

相关文章

• SSMS配置错误，导致 SELECT 失败，因为下列 SET 选项的设置不正确: 'QUOTED_IDENTIFIER, ANSI_PADDING'。请确保 SET 选项正确无误，可以用于 计算列上的索引视图和/或索引和/或筛选的索引和/或查询通知和/或 XML 数据类型方法和/或空间索引操作。。
• MSSQL一次重建索引未成功中途强制重启引起的故障
• 不允许对索引 'xxx' 显式地使用 DROP INDEX。该索引正用于 PRIMARY KEY 约束的强制执行
• MSSQL数据库中对自增列的插入时，提示：当 IDENTITY_INSERT 设置为 OFF 时，不能为表 't_xxx' 中的标识列插入显式值
• MSSQL查询表报错“SQL Server 检测到基于一致性的逻辑 I/O 错误 校验和不正确”
• 数据库“tempdb”的事务日志已满，原因为“ACTIVE_TRANSACTION” 解决方法
• MSSQL导入示例数据库AdventureWorks报错 出现大容量加载数据转换错误(类型不匹配或者字符对于指定的代码页无效)。
• MSSQL数据库一直显示“正在恢复”或“可疑”的解决办法
• 设备XXX上的文件 ID 1 的格式不正确，无法读取
• Navicat连接SQL Server报错 未发现数据源名称并且未指定默认驱动程序
• 在Docker中快速使用SQL Server 2022环境
• 在Docker中快速使用SQL Server各个版本（MSSQL）的数据库
• MSSQL执行差异备份报错：无法执行数据库 "LHRDB" 的差异备份，因为不存在当前数据库备份。请去掉WITH DIFFERENTIAL 选项后重新发出BACKUP DATABASE 以执行数据库的完整备份。
• MSSQL中的幽灵数据删除进程、虚影清除进程（ghost cleanup）
• MSSQL删除tempdb的数据文件
• MSSQL中的等待事件SQLTRACE_FILE_BUFFER说明
• MSSQL的数据库快照
• MSSQL 2014新功能之延迟事务持续性(Delayed Transaction Durability)--延迟提交
• MSSQL中的实时查询统计
• MSSQL中查询索引的创建时间和删除时间

打赏赞(1)分享

标签： 故障处理MSSQLSQL ServerDocker

小麦苗

学习或考证，均可联系麦老师，请加微信db_bao或QQ646634621

• 下一篇 Windows系统怎么重启explorer.exe(Windows资源管理器)
• 上一篇 虚拟化介绍

您可能还喜欢...

• 0

  MSSQL数据库中对自增列的插入时，提示：当 IDENTITY_INSERT 设置为 OFF 时，不能为表 't_xxx' 中的标识列插入显式值

  2023年11月28日

   由 小麦苗 · Published 2023年11月28日

   

  0    272    1
• 0

  【DB宝29】使用Docker搭建Oracle 11g的DG环境

  2021年6月21日

   由 小麦苗 · Published 2021年6月21日 · Last modified 2022年7月12日

  · 已更新 2022年7月12日  

  0    5008    6
• 0

  MSSQL变更数据捕获（CDC）和 更改跟踪（Chang Tracking）介绍

  2023年4月28日

   由 小麦苗 · Published 2023年4月28日 · Last modified 2024年4月26日

  · 已更新 2024年4月26日  

  0    113    1