mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[GH-ISSUE #142] meta_main start failed ,the meta_main service coredump #79
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#79
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @xiaoyaoyouyue on GitHub (Mar 11, 2025).
Original GitHub issue: https://github.com/deepseek-ai/3FS/issues/142
Issue Report
问题描述
程序在运行时崩溃，并生成了coredump文件。崩溃发生在meta_main进程中，信号为SIGABRT（Aborted）。
环境信息
操作系统: ubuntu 22.04
库文件路径: /lib/x86_64-linux-gnu/libthread_db.so.1
程序路径: /opt/3fs/bin/meta_main
配置文件路径: /opt/3fs/etc/meta_main_launcher.toml
崩溃信息
信号: SIGABRT
线程ID: 0x7f68a6046c80 (LWP 65878)
调用栈信息
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140087438634112) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=140087438634112) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=140087438634112, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007f68a82ae476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007f68a82947f3 in __GI_abort () at ./stdlib/abort.c:79
#5 0x000055819ca0b3d1 in folly::LogCategory::admitMessage (this=0x7f68a582cb20, message=...) at /root/3fs/3fs/third_party/folly/folly/logging/LogCategory.cpp:71
#6 0x000055819ca0a887 in folly::LogStreamProcessor::logNow (this=) at /root/3fs/3fs/third_party/folly/folly/logging/LogStreamProcessor.cpp:190
#7 0x000055819ca0aada in folly::LogStreamVoidify::operator& (this=, stream=...)
at /root/3fs/3fs/third_party/folly/folly/logging/LogStreamProcessor.cpp:222
#8 0x000055819d2f7503 in hf3fs::TwoPhaseApplicationhf3fs::meta::server::MetaServer::initApplication (this=0x7fffead69a90)
at /root/3fs/3fs/src/common/app/TwoPhaseApplication.h:59
#9 0x000055819c7362d7 in hf3fs::ApplicationBase::run (this=0x7fffead69a90, argc=1, argv=0x7fffead83ab8) at /root/3fs/3fs/src/common/app/ApplicationBase.cc:65
#10 0x000055819d2f4314 in main (argc=5, argv=0x7fffead83a98) at /root/3fs/3fs/src/meta/meta.cpp:7
详细信息
崩溃点: folly::LogCategory::admitMessage 函数中
相关代码路径:
/root/3fs/3fs/third_party/folly/folly/logging/LogCategory.cpp:71
/root/3fs/3fs/third_party/folly/folly/logging/LogStreamProcessor.cpp:190
/root/3fs/3fs/third_party/folly/folly/logging/LogStreamProcessor.cpp:222
/root/3fs/3fs/src/common/app/TwoPhaseApplication.h:59
/root/3fs/3fs/src/common/app/ApplicationBase.cc:65
/root/3fs/3fs/src/meta/meta.cpp:7
可能的原因
日志处理问题: 崩溃发生在日志处理相关的函数中，可能是由于日志消息处理不当或日志级别配置错误导致。
初始化失败: hf3fs::TwoPhaseApplicationhf3fs::meta::server::MetaServer::initApplication 方法可能在初始化过程中遇到了错误。
重现步骤
启动 meta_main 进程，使用配置文件 /opt/3fs/etc/meta_main_launcher.toml。
观察进程是否崩溃并生成coredump文件。
@huww98 commented on GitHub (Mar 11, 2025):
可以查看崩溃前的日志。
@xiaoyaoyouyue commented on GitHub (Mar 12, 2025):
看着有点像端口冲突，我只用了一个节点，而且是虚拟机，总是有网络路由问题