Upgrade from 5.0.9 to 5.1.5 No Web UI

Graylog Central (peer support)
1

I have a working Graylog 5.0.9 cluster that I am unable to upgrade to 5.1.5. When I upgrade, the web UI does not load. The service starts without issue. The logs are clear of errors and yet the UI does not load. I have checked by attempting to connect to the first node in the cluster directly from my computer. I attempt to connect to the first node directly from itself. All I get is connection refused. I can see from nmap that the server does not have port 9000 open. I checked that I didn’t mistaken overwrite the server.conf and it is still my previous config.

I am at a loss as to what to check.

Here are my specs for each node in the cluster.
Ubuntu 22.04.3 LTS
MongoDB 6.0.8
Opensearch 2.8.0
UFW Disabled

2

Can you view the page source to see if it shows anything? How about the developer console (f12 for chromium browsers like Chrome, Edge) (I think this may also work for firefox).

What happens when you query via curl? e.g.
curl http://127.0.0.1:9000

3

Using nmap I can see that the servers no longer have port 9000 open. When the servers were on 5.0.9 they did.

4

Meaning graylog is not listening/bound to TCP 9000?

Do you see it listed when you run sudo netstat -ntlp ?

(note you may need to first install net-tools, sudo apt install net-tools)

Also if you run the curl command, curl http://127.0.0.1:9000 do you get any output?

6

I got my ports confused. Yes after upgrading the servers are no longer listening on port 9000, but the service starts with no errors.

Before update running netstat -ntlp

netstat -ntlp
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      -
tcp        0      0 10.50.2.201:27017       0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.1:27017         0.0.0.0:*               LISTEN      -
tcp6       0      0 10.50.2.201:9300        :::*                    LISTEN      -
tcp6       0      0 :::5555                 :::*                    LISTEN      -
tcp6       0      0 10.50.2.201:9200        :::*                    LISTEN      -
tcp6       0      0 :::5049                 :::*                    LISTEN      -
tcp6       0      0 :::5048                 :::*                    LISTEN      -
tcp6       0      0 :::5051                 :::*                    LISTEN      -
tcp6       0      0 :::5050                 :::*                    LISTEN      -
tcp6       0      0 :::5053                 :::*                    LISTEN      -
tcp6       0      0 :::5052                 :::*                    LISTEN      -
tcp6       0      0 :::5045                 :::*                    LISTEN      -
tcp6       0      0 :::5044                 :::*                    LISTEN      -
tcp6       0      0 :::5047                 :::*                    LISTEN      -
tcp6       0      0 :::5046                 :::*                    LISTEN      -
tcp6       0      0 10.50.2.201:9000        :::*                    LISTEN      -
tcp6       0      0 :::12201                :::*                    LISTEN      -
tcp6       0      0 :::1514                 :::*                    LISTEN      -
tcp6       0      0 :::22                   :::*                    LISTEN      -

After upgrade running netstat -ntlp

 netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      887/systemd-resolve
tcp        0      0 10.50.2.201:27017       0.0.0.0:*               LISTEN      920/mongod
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      971/sshd: /usr/sbin
tcp        0      0 127.0.0.1:27017         0.0.0.0:*               LISTEN      920/mongod
tcp6       0      0 10.50.2.201:9300        :::*                    LISTEN      922/java
tcp6       0      0 10.50.2.201:9200        :::*                    LISTEN      922/java
tcp6       0      0 :::22                   :::*                    LISTEN      971/sshd: /usr/sbin

Service Status

service graylog-server status
● graylog-server.service - Graylog server
     Loaded: loaded (/lib/systemd/system/graylog-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2023-10-04 19:38:41 UTC; 1min 10s ago
       Docs: http://docs.graylog.org/
   Main PID: 5947 (graylog-server)
      Tasks: 83 (limit: 14171)
     Memory: 416.2M
        CPU: 18.013s
     CGroup: /system.slice/graylog-server.service
             ├─5947 /bin/sh /usr/share/graylog-server/bin/graylog-server
             └─5948 /usr/share/graylog-server/jvm/bin/java -Xms2g -Xmx2g -server -XX:+UseG1GC -XX:-OmitStackTraceInFastThrow -Djdk.tls.acknowledgeCloseNotify=true -Dlog4j2.formatMsgNoLookups=true -jar -Dlog4j.confi>

Oct 04 19:38:41 gl1 systemd[1]: Started Graylog server.
7

Anyone have any ideas?

8

I am the only one with this issue? I just tried again on my node 3 and the same thing. Service starts, nothing on port 9000

9

what are the last lines in /var/log/graylog-server/server.log ?

I can remember an instance of 5.1 not booting up after an upgrade, after a single mongodb on one of the nodes was stuck. The others were fine. Could you check all your mongodbs and maybe restart them?

10

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