安装部署遇到奇怪问题

1: 0xcb2ef7 node::Assert(node::AssertionInfo const&) [node]
2: 0xd33b3e node::WorkerThreadsTaskRunner::WorkerThreadsTaskRunner(int) [node]
3: 0xd33c1c node::NodePlatform::NodePlatform(int, v8::TracingController*, v8::PageAllocator*) [node]
4: 0xc64b8c [node]
5: 0xc660f4 node::Start(int, char**) [node]
6: 0x7f50236e524a [/lib/x86_64-linux-gnu/libc.so.6]
7: 0x7f50236e5305 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
8: 0xbb614e _start [node]

node[1]: std::unique_ptr node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start() at …/src/node_platform.cc:68

Assertion failed: (0) == (uv_thread_create(t.get(), start_thread, this))

使用docker-compose部署发现这个问题,请问各位大佬有没有遇到过

在docker-compose.yml文件,给Nodejs服务增加进程数限制
pids_limit

1 Like

该问题通常是由于系统资源或环境限制导致的,例如内存不足、CPU 负载过高,或者容器设置了 pids-limit or memory limit.

1 Like

感谢,已经解决

是的,谢谢,已经解决