Unable to log dashboard - no tcp/9000

Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question.
Don’t forget to select tags to help index your topic!

1. Describe your incident:
Hi, first post so hoping in the right category but please let me know if not.
I am trying to get graylog working to consider using it at work.

Installed from the Graylog instructions and after the usual (in my experience) trials and tribulations of getting something working on Linux I got through the preflight page with the certificates (not my area of expertise at all!).

Once that completed port 9000 is no longer listening if I do:
ss -tulpn
But tcp/9200, tcp/9300 and tcp/8999 amonst the other standards are.

What am I missing as to why this port is no long available and I cannot get to any gui?

Installed on Ubuntu 24.04.2
Checked the following logs and can’t see anything obvious:
/var/log/graylog-server/server.log
/var/log/graylog-datanode/datanode.log
/var/log/mongodb/mongod.log

2. Describe your environment:

  • OS Information:
    Ubuntu 24.04.2 LTS
  • Package Version:

graylog-6.1-repository 1-1
graylog-datanode 6.1.8-1
graylog-server 6.1.8-1
mongodb-database-tools 100.11.0
mongodb-mongosh 2.4.2
mongodb-org 7.0.17

  • Service logs, configurations, and environment variables:

3. What steps have you already taken to try and solve the problem?

4. How can the community help?

I am trying to access the gui dashboard in MS Edge to complete configuration and view logs

Helpful Posting Tips: Tips for Posting Questions that Get Answers [Hold down CTRL and link on link to open tips documents in a separate tab]

The big thing that will happen after preflight is that graylog server wont be happy if datanode isnt available. So my first guess would be to look in logs for anything related to that, it will complain about the “indexer”.

Are these on the same machine or two machines?

Hi Joel,

Thanks for the reply.

Apologies I should have added currently all on 1 machine.

As I have had some issues getting it going I wanted to get it going on one and then move to two possibly with a new build.

After having another scan through the logs for “indexer” I did come across an issue where I had configured the message_journal_max_size too high so was getting an error about free space, corrected that and restarted.

Now ss -tulpn shows:

which to me suggests its listening on 9000 for IPv6, is that correct?

Although from the datanode logs I can see:

Suppressed: org.graylog.shaded.opensearch2.org.opensearch.client.ResponseException: method [POST], host [https://graylog:9200], URI [/gl-datanode-metrics/_search?typed_keys=true&max_concurrent_shard_requests=5&ignore_unavailable=false&expand_wildcards=open&allow_no_indices=true&ignore_throttled=true&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=true], status line [HTTP/1.1 404 Not Found]
{“error”:{“root_cause”:[{“type”:“index_not_found_exception”,“reason”:“no such index [gl-datanode-metrics]”,“index”:“gl-datanode-metrics”,“resource.id”:“gl-datanode-metrics”,“resource.type”:“index_or_alias”,“index_uuid”:“na”}],“type”:“index_not_found_exception”,“reason”:“no such index [gl-datanode-metrics]”,“index”:“gl-datanode-metrics”,“resource.id”:“gl-datanode-metrics”,“resource.type”:“index_or_alias”,“index_uuid”:“na”},“status”:404}

Just trying to narrow down this but would love to be pointed in the right direction.

Many thanks

Interestingly even with the error mentioned above I refreshed the web browser and a login appeared.

It wouldn’t let me login with the initial details from the server.log but the password I entered during setup.

But seem ok.

Do I need to be concerned by the index error?

If so as above some guidance on resolution would be greatly appreciated.

Thanks again.

As long as opensesrch status shows green in graylog on the datanode page im pretty sure that error just happens sometimes.

It certainly does show green.

Many thanks for your assistance.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.