Are there any errors in the MongoDB service log before it starts closing connections and shutting down the service before restarting? Above where the top of the screenshot starts. The Graylog log you posted first indicates a problem opening a connection to MongoDB. That’s where all of the Graylog server configurations live.
Unless the kernel is killing the service for some reason (we should see that in kern.log), it will be in one of those. Any errors in the current log? Or, what’s at the end of the prior log? (mongodb.log.1)
Hello @manga411, so glad you fixed your MongoDB issue! For me an outdated version still showing after an upgrade is usually simply because the browser cache needs to be refreshed. The simplest fix is to force a refresh using whatever method your browser requires. For me it is to hold shift while clicking refresh or pressing F5.
Hello @ttsandrew I tried your suggestion pressing F5 and even tried another browser but I’m still getting this message? Can you confirm the steps I mentioned are correct to upgrade Graylog?
Yes those are the correct steps, I just used those exact steps (plus one more for enterprise plugins) to upgrade our test environment from 3.8 to 4.0.
does apt show graylog-server show version 2.5?
Were there any errors when you ran the install?
You confirmed you did cycle the service, correct? sudo systemctl restart graylog-server
If the repository is already downloaded and available in the current directory you don’t need to run the first command again. The rest of the commands are correct, yes.
flexible@test-pur-syslog-1:~ sudo apt-get upgrade graylog-server=2.5.1
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version ‘2.5.1’ for ‘graylog-server’ was not found
flexible@test-pur-syslog-1:~