Graylog active and not listening port 9000

[rds25 (rémi)]

Graylog is active but not the webgui no port 9000 in listening.
Debian 11

In the logs I see this:

and then he writes:

2022-12-28T21:08:14.982+01:00 INFO [MongoDBPreflightCheck] MongoDB is not available. Retry #1
2022-12-28T21:08:16.983+01:00 INFO [cluster] Cluster description not yet available. Waiting for 30000 ms before timing out
2022-12-28T21:08:46.984+01:00 INFO [MongoDBPreflightCheck] MongoDB is not available. Retry #2
2022-12-28T21:08:48.986+01:00 INFO [cluster] Cluster description not yet available. Waiting for 30000 ms before timing out
2022-12-28T21:09:18.987+01:00 INFO [MongoDBPreflightCheck] MongoDB is not available. Retry #3
2022-12-28T21:09:20.989+01:00 INFO [cluster] Cluster description not yet available. Waiting for 30000 ms before timing out
how to fix please?

[StefanAustin]

To me, it looks like the connection is going towards port 27017

[tmacgbay]

It would help if we knew more about your environment. Port 27017 seems non-standard and the other errors show that MongoDB isn’t up. You can post your server.conf file (Properly obfuscated) and also consider reading through this page to help give us more information to help you solve your problem…

[chris.black-gl (Chris Black)]

GL uses 27017 to communicate with Mongo. If the mongo URI is not in the server.conf, GL can’t reach it and will never finish starting.

[tmacgbay]

@chris.black-gl

GL uses 27017 to communicate with Mongo

Silly me - it’s me that non-standard. If I look at my server.conf WITH comments I can see the default 27017.

@rds25 - Graylog uses Mongo to store environment and settings without it working, Graylog won’t run.

[rds25 (rémi)]

Indeed, MongoDB had a little problem so I went back to a backup. And I intercepted the anomaly. Ty