[BUG] Futex error crashing/restarting application
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- debian, docker, javascript, kubernetes, nodejs
调研方向
从 issue #421 中的环境和崩溃详情开始，比较报告的 Node.js 18 和 22 运行情况，以及 Debian 12 和 Ubuntu 24 镜像。使用 Kubernetes 节点 futex trace 作为初始诊断证据；完成标准是找到可复现的触发条件，或确认原因并提供可执行的修复，因为该报告目前没有复现模式。
由索引模型根据 Issue 内容生成。
描述
Describe your system
odbcPackage Version:- ODBC Driver: node-odbc
- Database Name: db2
- Database Version: db2 for ibmi level 25
- Database OS: IBMI V7R4
- Node.js Version: 18.20.4
- Node.js OS: debian 12
Describe the bug
We are running a nodejs application inside a debian 12 container with the latest ibm-iaccess DB2 odbc (version 1.1.0.28-1.0) debian package installed in a Kubernetes cluster.
Since months, randomly, the application crashes (and restart) with the following error message : The futex facility returned an unexpected error code.
These are some technical specifications :
-
Kubernetes :
-
Kubernetes version :
1.27.16 -
Installation : Our Kubernetes cluster is not managed and we have full control of our nodes configuration
-
-
Application runtime :
-
The application Docker image is a custom image created by ourselves. However it is mainly based on : node:18.20-bookworm-slim (available on docker hub , debian 12 based)
-
Node version currently used is :
18.20.4 -
The nodejs library used to interact with the odbc is : odbc in version
2.4.9
-
The crash seems not related to any resources (CPU/RAM etc …) problem.
We also did upgrade to node 22 and either change docker image to Ubuntu 24.
We also tried to increase the logs level on application side (like node options --trace-uncaught --abort-on-uncaught-exception --report-uncaught-exception ) but it didn’t work. The crash seems to come from between Kubernetes and the container itself. I succeeded to catch some logs on the Kubernetes node when the application crashes:
trace: Process 505065 attached
futex(0xdaf4e8, FUTEX_WAIT_PRIVATE, 0, NULL) = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=505115, si_uid=0, si_status=134, si_utime=0, si_stime=0} ---
futex(0xdde380, FUTEX_WAKE_PRIVATE, 1) = 1
rt_sigreturn({mask=~[HUP INT QUIT ILL TRAP ABRT BUS FPE KILL USR1 SEGV PIPE TERM STKFLT CHLD STOP URG PROF SYS RTMIN RT_1 RT_2]}) = 202
futex(0xdaf4e8, FUTEX_WAIT_PRIVATE, 0, NULL) = ?
+++ exited with 0 +++
Expected behavior
Futex error not happening
To Reproduce
Unfortunately , we didn't success to find the pattern to reproduce the issue, this one seems very random
Questions
-
Did you already encountered this kind of issue in the past ?
-
Do you have an idea of how to troubleshoot this ?
Thanks a lot for your help
- 主要语言
- JavaScript
- 星标
- 159
- 派生
- 92
- 平均合并
- 5 小时 59 分钟
- 30 天内合并 PR
- 3
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
IBM/node-odbc 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
-
security
难度 3/5 1-2 天 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 48/100
-
难度 4/5 3-5 天 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 38/100
相似的 Issue
-
[APP/MODULE]未关闭enhancement
难度 2/5 1-3 小时 新手友好度 68/100
awesome-android-root/awesome-android-root#195 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
subhranshudash13-dotcom/Contribo#74 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
qq15725/modern-screenshot#174 ·
-
难度 1/5 1 小时以内 新手友好度 67/100
ThatGuySam/doesitarm#1114 ·