Comments (9)
@muhammadsiddiqbe Hi, can you please describe in a little more detail how you ended up with this error?
I can only assume that you started the preflight interface, created a CA (probably also a Renewal policy) and then pressed resume or skip? Did you start a DataNode? Do you even want to use a DataNode or do you want to use a standalone OpenSearch?
from docker-compose.
Hi, I'm having the same problem. I used the docker compose file form open-core & when i ran the stack, i'm getting the same error.
i am new to this, so when i started the container and went to x.x.x.x:9000, it begins with the installation. I generate a certificate but it says no nodes configured "No data nodes have been found."
the open-core dockercompose file is missing the opensearch or elastisearch container
this is the error that i get in the graylog-datanode-1 container logs
2023-12-20T01:23:45.246Z ERROR [PreflightCheckService] Preflight check failed with error: /proc/sys/vm/max_map_count value should be at least 262144 but is 65530 (set via "vm.max_map_count" sysctl)
2023-12-20T01:23:45.247Z ERROR [CmdLineTool] Startup error:
org.graylog2.bootstrap.preflight.PreflightCheckException: /proc/sys/vm/max_map_count value should be at least 262144 but is 65530 (set via "vm.max_map_count" sysctl)
at org.graylog.datanode.bootstrap.preflight.OpenSearchPreconditionsCheck.runCheck(OpenSearchPreconditionsCheck.java:51) ~[graylog-datanode.jar:?]
at com.google.common.collect.ImmutableList.forEach(ImmutableList.java:422) ~[guava-32.1.2-jre.jar:?]
at org.graylog2.bootstrap.preflight.PreflightCheckService.runChecks(PreflightCheckService.java:51) ~[graylog2-server-5.2.2.jar:?]
at org.graylog.datanode.bootstrap.ServerBootstrap.runPreFlightChecks(ServerBootstrap.java:133) ~[graylog-datanode.jar:?]
at org.graylog.datanode.bootstrap.ServerBootstrap.beforeInjectorCreation(ServerBootstrap.java:118) ~[graylog-datanode.jar:?]
at org.graylog.datanode.bootstrap.CmdLineTool.doRun(CmdLineTool.java:286) ~[graylog-datanode.jar:?]
at org.graylog.datanode.bootstrap.CmdLineTool.run(CmdLineTool.java:244) [graylog-datanode.jar:?]
at org.graylog.datanode.bootstrap.Main.main(Main.java:57) [graylog-datanode.jar:?]
Exception in thread "main" org.graylog2.bootstrap.preflight.PreflightCheckException: /proc/sys/vm/max_map_count value should be at least 262144 but is 65530 (set via "vm.max_map_count" sysctl)
at org.graylog.datanode.bootstrap.preflight.OpenSearchPreconditionsCheck.runCheck(OpenSearchPreconditionsCheck.java:51)
at com.google.common.collect.ImmutableList.forEach(ImmutableList.java:422)
at org.graylog2.bootstrap.preflight.PreflightCheckService.runChecks(PreflightCheckService.java:51)
at org.graylog.datanode.bootstrap.ServerBootstrap.runPreFlightChecks(ServerBootstrap.java:133)
at org.graylog.datanode.bootstrap.ServerBootstrap.beforeInjectorCreation(ServerBootstrap.java:118)
at org.graylog.datanode.bootstrap.CmdLineTool.doRun(CmdLineTool.java:286)
at org.graylog.datanode.bootstrap.CmdLineTool.run(CmdLineTool.java:244)
at org.graylog.datanode.bootstrap.Main.main(Main.java:57)
from docker-compose.
@yodaphone Hi, you have a different error - which is also, what the message says. May I point you to the docs?
https://go2docs.graylog.org/5-2/setting_up_graylog/graylog_data_node_getting_started.htm?tocpath=Setting%20up%20Graylog%7CGraylog%20Data%20Node%7C_____1
and/or
https://github.com/Graylog2/docker-compose?tab=readme-ov-file#configure-your-os
OpenSearch is included in the DataNode. To fix it, easiest is to start over by doing docker compose down -v
to remove everything and start over after fixing the os-setting. Let me know if it works!
from docker-compose.
i started over and ran the docker compose file in open-core with the env file again. I did change the setting in the OS but still getting this error. unable to connect to web ui
I'm running
Ubuntu 22.04
Docker version 24.07
2023-12-20 14:04:37,840 INFO : org.graylog2.featureflag.ImmutableFeatureFlagsCollector - Following feature flags are used: {default properties file=[frontend_hotkeys=on, field_types_management=on, cloud_inputs=on, scripting_api_preview=>
2023-12-20 14:04:40,158 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: AWS plugins 5.2.2+8eab621 [org.graylog.aws.AWSPlugin]
2023-12-20 14:04:40,167 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Integrations 5.2.2+8eab621 [org.graylog.integrations.IntegrationsPlugin]
2023-12-20 14:04:40,170 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Threat Intelligence Plugin 5.2.2+8eab621 [org.graylog.plugins.threatintel.ThreatIntelPlugin]
2023-12-20 14:04:40,173 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: Elasticsearch 7 Support 5.2.2+8eab621 [org.graylog.storage.elasticsearch7.Elasticsearch7Plugin]
2023-12-20 14:04:40,176 INFO : org.graylog2.bootstrap.CmdLineTool - Loaded plugin: OpenSearch 2 Support 5.2.2+8eab621 [org.graylog.storage.opensearch2.OpenSearch2Plugin]
2023-12-20 14:04:40,309 INFO : org.graylog2.bootstrap.CmdLineTool - Running with JVM arguments: -Dlog4j2.formatMsgNoLookups=true -Djdk.tls.acknowledgeCloseNotify=true -XX:+UnlockExperimentalVMOptions -XX:-OmitStackTraceInFastThrow -XX:+>
2023-12-20 14:04:41,277 INFO : org.mongodb.driver.client - MongoClient with metadata {"driver": {"name": "mongo-java-driver|legacy", "version": "4.8.1"}, "os": {"type": "Linux", "name": "Linux", "architecture": "amd64", "version": "6.2.>
2023-12-20 14:04:41,299 INFO : org.mongodb.driver.client - MongoClient with metadata {"driver": {"name": "mongo-java-driver|legacy", "version": "4.8.1"}, "os": {"type": "Linux", "name": "Linux", "architecture": "amd64", "version": "6.2.>
2023-12-20 14:04:41,268 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketOpenException: Exception opening socket
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:73) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.ConnectException: Connection refused
at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
at sun.nio.ch.Net.pollConnectNow(Unknown Source) ~[?:?]
at sun.nio.ch.NioSocketImpl.timedFinishConnect(Unknown Source) ~[?:?]
at sun.nio.ch.NioSocketImpl.connect(Unknown Source) ~[?:?]
at java.net.SocksSocketImpl.connect(Unknown Source) ~[?:?]
at java.net.Socket.connect(Unknown Source) ~[?:?]
at com.mongodb.internal.connection.SocketStreamHelper.initialize(SocketStreamHelper.java:107) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:82) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
... 4 more
2023-12-20 14:04:41,385 INFO : org.mongodb.driver.cluster - Cluster description not yet available. Waiting for 30000 ms before timing out
2023-12-20 14:05:11,414 INFO : org.graylog2.bootstrap.preflight.MongoDBPreflightCheck - MongoDB is not available. Retry #1
2023-12-20 14:05:13,449 INFO : org.mongodb.driver.cluster - Cluster description not yet available. Waiting for 30000 ms before timing out
2023-12-20 14:05:13,986 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketException: mongodb: Temporary failure in name resolution
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:217) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:78) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.UnknownHostException: mongodb: Temporary failure in name resolution
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) ~[?:?]
at java.net.InetAddress.getAddressesFromNameService(Unknown Source) ~[?:?]
at java.net.InetAddress$NameServiceAddresses.get(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:209) ~[graylog.jar:?]
... 6 more
2023-12-20 14:05:14,496 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketException: mongodb
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:217) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:78) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.UnknownHostException: mongodb
at java.net.InetAddress$CachedAddresses.get(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:209) ~[graylog.jar:?]
... 6 more
2023-12-20 14:05:24,049 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketException: mongodb: Temporary failure in name resolution
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:217) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:78) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.UnknownHostException: mongodb: Temporary failure in name resolution
at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) ~[?:?]
at java.net.InetAddress$PlatformNameService.lookupAllHostAddr(Unknown Source) ~[?:?]
at java.net.InetAddress.getAddressesFromNameService(Unknown Source) ~[?:?]
at java.net.InetAddress$NameServiceAddresses.get(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:209) ~[graylog.jar:?]
... 6 more
2023-12-20 14:05:24,559 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketException: mongodb
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:217) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:78) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
Caused by: java.net.UnknownHostException: mongodb
at java.net.InetAddress$CachedAddresses.get(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName0(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at java.net.InetAddress.getAllByName(Unknown Source) ~[?:?]
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:209) ~[graylog.jar:?]
... 6 more
2023-12-20 14:05:34,107 INFO : org.mongodb.driver.cluster - Exception in monitor thread while connecting to server mongodb:27017
com.mongodb.MongoSocketException: mongodb: Temporary failure in name resolution
at com.mongodb.ServerAddress.getSocketAddresses(ServerAddress.java:217) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.initializeSocket(SocketStream.java:78) ~[graylog.jar:?]
at com.mongodb.internal.connection.SocketStream.open(SocketStream.java:68) ~[graylog.jar:?]
at com.mongodb.internal.connection.InternalStreamConnection.open(InternalStreamConnection.java:183) ~[graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.lookupServerDescription(DefaultServerMonitor.java:198) [graylog.jar:?]
at com.mongodb.internal.connection.DefaultServerMonitor$ServerMonitorRunnable.run(DefaultServerMonitor.java:158) [graylog.jar:?]
at java.lang.Thread.run(Unknown Source) [?:?]
from docker-compose.
@yodaphone interesting, I never got this one myself. That looks as if mongodb never came up. You never get to the UI then, right? please do a docker compose down -v
again, and then start mongodb first with docker compose up -d mongodb
make sure that it's running ok. If it's up, start the rest of the services. I'm re-checking that file myself again, too.
edit: I ran the open-core docker-compose.yml
again, worked fine for me. I did not check with the exact Ubuntu version you have - but it's docker so I guess that should not make a difference.
from docker-compose.
hi there
here's the log from the mongodb container
WARNING: MongoDB 5.0+ requires a CPU with AVX support, and your current system does not appear to have that! see https://jira.mongodb.org/browse/SERVER-54407 see also https://www.mongodb.com/community/forums/t/mongodb-5-0-cpu-intel-g4650-compatibility/116610/2 see also https://github.com/docker-library/mongo/issues/485#issuecomment-891991814
whats wierd is that i have another docker instance running in a different VM that is identical to the one thats running this instance as well and I dont have that error there.
from docker-compose.
Ok, I figured out the issue. the only difference between the VMs was that i was using KVM for the processor but when i changed it to "host" mongodb started working. not sure why this is having an impact. I use proxmox for Virtualization
from docker-compose.
@yodaphone I'm glad you found the problem! So everything works now?
@muhammadsiddiqbe you're fine now, too?
can I close this issue?
from docker-compose.
closed this as there was no further feedback so I guess it works now
from docker-compose.
Related Issues (20)
- The connection does not work after opensearch is replaced with datanode. HOT 19
- Error on Data-Node after provision certificate HOT 4
- Opensearch is not available after provision certificate HOT 10
- Email configuration doesn't apply HOT 1
- Introduction of datanode may be confusing for users, possibly need to add text in the docker compose file to communication how to perform first setup HOT 10
- confusing documentation HOT 2
- SSL Certificate Hostname Verification Issue with Graylog in Docker Environment HOT 3
- The graylog/graylog-datanode:5.2 docker image is not starting correctly returning an error max_map_count value should be at least 262144 but is 65530 HOT 3
- Cannot connect to data node HOT 1
- datanode won't restart after hitting flood-stage watermark HOT 13
- DataNode: Failed to load keystore from Mongo collection for node GRAYLOG CA HOT 2
- Node API Browser uses Docker internal IP HOT 1
- The signing key's size is 208 bits which is not secure enough HOT 4
- How to connect to Data Node to fix long messages not logged HOT 5
- Facing error org.graylog2.bootstrap.CmdLineTool - Startup error HOT 1
- certificates expired for datanode after long downtime HOT 5
- How to generate password and SHA2 in Windows? HOT 1
- docker compse max_map_count value should be at least 262144 but is 65530 HOT 2
- Add to readme which folder may be used for single node use
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-compose.