Attempted an upgrade on an Amazon AMI Graylog 2.0.2 cluster (3 web servers, 4 elastic nodes), encountered problems after installing 2.3.2 on the web servers, decided to revert. We upgraded by doing the following: wget https://packages.graylog2.org/releases/graylog-omnibus/ubuntu/graylog_2.3.2-3_am…

At this point, the strangest thing is that the master server is running mongodb just fine. It went through the same upgrade and revert steps, but it’s running (fortunately). I don’t know enough about mongodb to know what I need to do to it, but I wonder if it’s due to the changes to MongoDB from th…

Yet, that doesn’t make sense - why did the master web server come right up after the same revert?

I found some info on this error here : https://docs.mongodb.com/manual/reference/operator/query/type/#op._S_type Still trying to understand what to do.

and it appears that the only BSON I can find (/var/opt/graylog/data/mongodb) that might produce the error is always basic. { "storage" : { "engine" : "wiredTiger", "options" : { "directoryPerDB" : false, "directoryForIndexes" : false } } } 1 objects found

We have covered in the Documentation that you should not jump over multiple version numbers - just do one version after another. http://docs.graylog.org/en/2.4/pages/upgrade.html

Given that addition was added as of 2.3, I’m not surprised I completely missed that. I’ve been running varying versions of Graylog since 2.0, so I failed to see that. So if I do the upgrade from 2.0.2 to 2.1 to 2.2 to 2.3, that should go more smoothly. Thanks for that!

Now, in regards to the mongodb problem - given the error, would changing the version of mongo available in mongo’s bin folder potentially help it? I saw at least one troubleshooting thread recommend changing from 3.2.4 to 3.0 in an attempt to resolve their issues. Since I upgraded via graylog-ctl …

Problems after reverting an upgrade : MongoDB flapping

Graylog Central (peer support)

razumzhiro January 2, 2018, 7:05pm 4

Also, realized I completely forgot about the comment made here : Upgrading within Amazon

Downgrade is not supported, so make sure to make a backup or snapshot before upgrading.

Well, I see my first mistake.

Topic		Replies	Views
Warning: MongoDB 4.2.8 may break graylog-server 3+ Graylog Central (peer support)	4	871	August 26, 2020
Can't connect to web interface after upgrade to 6.0 Graylog Central (peer support) architecture	11	134	December 17, 2025
Upgrade Assistance from 2.4.6 to 2.4.7 Graylog Central (peer support)	25	1034	December 6, 2020
Graylog doesn't work when 1 of my 2 mongodb instances is down: Graylog Central (peer support) mongodb	5	151	May 20, 2025
Only 1 of 3 nodes shows gl configuration after upgrade Graylog Central (peer support)	3	655	October 6, 2020

Problems after reverting an upgrade : MongoDB flapping

Related topics