[Bug]: Connection error caused by: ConnectionError(Connection error caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7ffff94f1900>: Failed to establish a new connection: [Errno 111] Connection refused))
Is there an existing issue for the same bug?
- [X] I have checked the existing issues.
Branch name
main
Commit ID
54342ae
Other environment information
ERROR: Elasticsearch exited unexpectedly, with exit code 137
2024-09-13 17:56:12 Sep 13, 2024 8:26:12 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
2024-09-13 17:56:12 WARNING: COMPAT locale provider will be removed in a future release
2024-09-13 17:56:13 {"@timestamp":"2024-09-13T12:26:13.105Z", "log.level": "WARN", "message":"unable to install syscall filter: ", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.JNANatives","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster","error.type":"java.lang.UnsupportedOperationException","error.message":"seccomp unavailable: CONFIG_SECCOMP not compiled into kernel, CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER are needed","error.stack_trace":"java.lang.UnsupportedOperationException: seccomp unavailable: CONFIG_SECCOMP not compiled into kernel, CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER are needed\n\tat [email protected]/org.elasticsearch.bootstrap.SystemCallFilter.linuxImpl(SystemCallFilter.java:331)\n\tat [email protected]/org.elasticsearch.bootstrap.SystemCallFilter.init(SystemCallFilter.java:622)\n\tat [email protected]/org.elasticsearch.bootstrap.JNANatives.tryInstallSystemCallFilter(JNANatives.java:251)\n\tat [email protected]/org.elasticsearch.bootstrap.Natives.tryInstallSystemCallFilter(Natives.java:102)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initializeNatives(Elasticsearch.java:291)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:167)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:72)\n"}
Actual behavior
ERROR: Elasticsearch exited unexpectedly, with exit code 137
2024-09-13 17:56:12 Sep 13, 2024 8:26:12 PM sun.util.locale.provider.LocaleProviderAdapter
Expected behavior
No response
Steps to reproduce
ERROR: Elasticsearch exited unexpectedly, with exit code 137
2024-09-13 17:56:12 Sep 13, 2024 8:26:12 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
2024-09-13 17:56:12 WARNING: COMPAT locale provider will be removed in a future release
2024-09-13 17:56:13 {"@timestamp":"2024-09-13T12:26:13.105Z", "log.level": "WARN", "message":"unable to install syscall filter: ", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.JNANatives","elasticsearch.node.name":"es01","elasticsearch.cluster.name":"docker-cluster","error.type":"java.lang.UnsupportedOperationException","error.message":"seccomp unavailable: CONFIG_SECCOMP not compiled into kernel, CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER are needed","error.stack_trace":"java.lang.UnsupportedOperationException: seccomp unavailable: CONFIG_SECCOMP not compiled into kernel, CONFIG_SECCOMP and CONFIG_SECCOMP_FILTER are needed\n\tat [email protected]/org.elasticsearch.bootstrap.SystemCallFilter.linuxImpl(SystemCallFilter.java:331)\n\tat [email protected]/org.elasticsearch.bootstrap.SystemCallFilter.init(SystemCallFilter.java:622)\n\tat [email protected]/org.elasticsearch.bootstrap.JNANatives.tryInstallSystemCallFilter(JNANatives.java:251)\n\tat [email protected]/org.elasticsearch.bootstrap.Natives.tryInstallSystemCallFilter(Natives.java:102)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initializeNatives(Elasticsearch.java:291)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase2(Elasticsearch.java:167)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:72)\n"}
Additional information
No response
Elasticsearch failure. Please refer to this. Plus, check MEM_LIMIT in docker/,env and RAM of your machine.
I had the exact same problem with docker deployment on windows, accessing port 1200 locally and port 9200 in the container, but this error occurred when running the service
This is an Elasticsearch issue.
This is an Elasticsearch issue.
how to deal it
我在 Windows 上部署 docker 时遇到了完全相同的问题,在本地访问端口 1200 和容器中的端口 9200,但是在运行服务时会出现此错误
老哥,你的问题解决了嘛
检查你的电脑配置是否符合ragflow的最低配置要求,我是这个原因
------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2025年2月12日(星期三) 下午2:04 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [infiniflow/ragflow] [Bug]: Connection error caused by: ConnectionError(Connection error caused by: NewConnectionError(<urllib3.connection.HTTPConnection object at 0x7ffff94f1900>: Failed to establish a new connection: [Errno 111] Connection refused)) (Issue #2424)
我在 Windows 上部署 docker 时遇到了完全相同的问题,在本地访问端口 1200 和容器中的端口 9200,但是在运行服务时会出现此错误
老哥,你的问题解决了嘛
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>