Graylog start erorr

[ahmedakkaya (Ahmet Akkaya)]

root@graylog:~# systemctl status graylog-server
● graylog-server.service - Graylog server
Loaded: loaded (/lib/systemd/system/graylog-server.service; enabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2022-09-01 06:50:06 UTC; 9s ago
Docs: http://docs.graylog.org/
Process: 10275 ExecStart=/usr/share/graylog-server/bin/graylog-server (code=exited, status=1/FAILURE)
Main PID: 10275 (code=exited, status=1/FAILURE)
CPU: 5.916s

2022-09-01T06:50:43.626Z INFO  [ImmutableFeatureFlagsCollector] Following feature flags are used: {}
2022-09-01T06:50:44.242Z INFO  [CmdLineTool] Loaded plugin: AWS plugins 4.3.5 [org.graylog.aws.AWSPlugin]
2022-09-01T06:50:44.243Z INFO  [CmdLineTool] Loaded plugin: Collector 4.3.5 [org.graylog.plugins.collector.CollectorPlugin]
2022-09-01T06:50:44.243Z INFO  [CmdLineTool] Loaded plugin: Threat Intelligence Plugin 4.3.5 [org.graylog.plugins.threatintel.ThreatIntelPlugin]
2022-09-01T06:50:44.244Z INFO  [CmdLineTool] Loaded plugin: Elasticsearch 6 Support 4.3.5+32fa802 [org.graylog.storage.elasticsearch6.Elasticsearch6Plugin]
2022-09-01T06:50:44.244Z INFO  [CmdLineTool] Loaded plugin: Elasticsearch 7 Support 4.3.5+32fa802 [org.graylog.storage.elasticsearch7.Elasticsearch7Plugin]
2022-09-01T06:50:44.263Z INFO  [CmdLineTool] Running with JVM arguments: -Xms1g -Xmx1g -XX:NewRatio=1 -XX:+ResizeTLAB -XX:-OmitStackTraceInFastThrow -Djdk.tls.acknowledgeCloseNotify=true -Dlog4j2.formatMsgNoLookups=true -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -Dlog4j.configurationFile=file:///etc/graylog/server/log4j2.xml -Djava.library.path=/usr/share/graylog-server/lib/sigar -Dgraylog2.installation_source=deb
2022-09-01T06:50:44.599Z INFO  [cluster] Cluster created with settings {hosts=[localhost:27017], mode=SINGLE, requiredClusterType=UNKNOWN, serverSelectionTimeout='30000 ms', maxWaitQueueSize=5000}
2022-09-01T06:50:44.632Z INFO  [cluster] Cluster description not yet available. Waiting for 30000 ms before timing out
2022-09-01T06:50:44.650Z INFO  [connection] Opened connection [connectionId{localValue:1, serverValue:245}] to localhost:27017
2022-09-01T06:50:44.653Z INFO  [cluster] Monitor thread successfully connected to server with description ServerDescription{address=localhost:27017, type=STANDALONE, state=CONNECTED, ok=true, version=ServerVersion{versionList=[5, 0, 11]}, minWireVersion=0, maxWireVersion=13, maxDocumentSize=16777216, logicalSessionTimeoutMinutes=30, roundTripTimeNanos=2374739}
2022-09-01T06:50:44.663Z INFO  [connection] Opened connection [connectionId{localValue:2, serverValue:246}] to localhost:27017
2022-09-01T06:50:44.683Z INFO  [connection] Closed connection [connectionId{localValue:2, serverValue:246}] to localhost:27017 because the pool has been closed.
2022-09-01T06:50:44.685Z INFO  [MongoDBPreflightCheck] Connected to MongoDB version 5.0.11
2022-09-01T06:50:44.825Z INFO  [SearchDbPreflightCheck] Connected to (Elastic/Open)Search version <Elasticsearch:7.10.2>
2022-09-01T06:50:44.855Z ERROR [PreflightCheckService] Preflight check failed with error: Journal directory </var/lib/graylog-server/journal> has not enough free space (2035 MB) to contain 'message_journal_max_size = 5120 MB' 

[H2Cyber]

Journal directory </var/lib/graylog-server/journal> has not enough free space (2035 MB) to contain ‘message_journal_max_size = 5120 MB’

You should either increase the amount of disk space available for the Journal directory (/var/lib/graylog-server/journal), or change the message_journal_max_size to a lower value in the server.conf Graylog configuration file.

[ahmedakkaya (Ahmet Akkaya)]

message_journal_max_size = 12gb

My problem was solved with the change, thanks .