After upgrade from 4.0 to 4.1 graylog stop working

Hi,

Before the upgrade graylog was not “processing” any logs. With other posts I fixed it and did the upgrade.

After upgrade had a ton of issues and again with posts I found in the forum I managed to put it at a “Running” state but web page keeps saying Server currently unavailable.

ubuntu@graylog:~$ sudo systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-07-26 12:26:44 WEST; 28s ago
Docs: http://www.elastic.co
Main PID: 3055 (java)
Tasks: 61 (limit: 4915)
CGroup: /system.slice/elasticsearch.service
└─3055 /usr/bin/java -Xms4g -Xmx4g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Des.net

Jul 26 12:26:44 graylog systemd[1]: Started Elasticsearch.
Jul 26 12:26:44 graylog elasticsearch[3055]: warning: Falling back to java on path. This behavior is deprecated. Specify JAVA_HOME
ubuntu@graylog:~$ sudo systemctl status mongod.service
● mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-07-26 12:07:20 WEST; 20min ago
Docs: https://docs.mongodb.org/manual
Main PID: 475 (mongod)
CGroup: /system.slice/mongod.service
└─475 /usr/bin/mongod --config /etc/mongod.conf

Jul 26 12:07:20 graylog systemd[1]: Started MongoDB Database Server.
ubuntu@graylog:~$ sudo systemctl status gra
graphical.target graylog-server.service
ubuntu@graylog:~$ sudo systemctl status gra
graphical.target graylog-server.service
ubuntu@graylog:~$ sudo systemctl status gra
graphical.target graylog-server.service
ubuntu@graylog:~$ sudo systemctl status graylog-server.service
● graylog-server.service - Graylog server
Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/graylog-server.service.d
└─10-after_services.conf
Active: active (running) since Mon 2021-07-26 12:27:06 WEST; 37s ago
Docs: http://docs_graylog_org
Main PID: 3248 (graylog-server)
Tasks: 108 (limit: 4915)
CGroup: /system.slice/graylog-server.service
├─3248 /bin/sh /usr/share/graylog-server/bin/graylog-server
└─3281 /usr/bin/java -Xms3g -Xmx3g -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:-OmitStackTraceInFastThrow -Djdk.tls.acknowledgeCloseNotify=tr

Jul 26 12:27:06 graylog systemd[1]: graylog-server.service: Service hold-off time over, scheduling restart.
Jul 26 12:27:06 graylog systemd[1]: graylog-server.service: Scheduled restart job, restart counter is at 1.
Jul 26 12:27:06 graylog systemd[1]: Stopped Graylog server.
Jul 26 12:27:06 graylog systemd[1]: Started Graylog server.

epoch timestamp cluster status node.total node.data shards pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1627299973 11:46:13 graylog green 1 1 288 288 0 0 0 0 - 100.0%

TIA

Is there any error in graylog logs file?
sudo tail -f /var/log/graylog-server/server.log

well… I think I found the problem…if I use the alias/DNS for the server it doesn’t work, if I put the IP it works…
graylog.mydomain.com:9000 I get server currently not available
if I put the IP it works 192.168.1.241:9000

Where can I fix this?

Here is the result for the command shoothub.
ubuntu@graylog:~$ sudo tail -f /var/log/graylog-server/server.log
2021-07-26T16:54:27.574+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:54:28.616+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:54:56.080+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:54:56.961+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:54:56.968+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:54:57.645+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:55:56.660+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:55:57.300+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:56:01.703+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.
2021-07-26T16:56:03.011+01:00 ERROR [AuditLogger] Unable to write audit log entry because there is no valid license.

This could be the same issue I was seeing here.

Yes, had to force the true and it works now. TY :slight_smile:

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