Multi-node KO after ES and Graylog update

[Service (Informatique)]

Hello,

Thanks for you response.

@gsmith

I realize that the settings before the Upgrade was working, and this was a major version upgrade I think because you have two conflicting statements as shown above. Some settings and configuration have changed between versions.

Yes, first I updated 3.1 directly to 4.2. Nodes are VM machines so I go back in time in Graylog 3.1 (when all worked fine) and after that do update step-by-step. So starting: 3.1 to 3.2 => OK. After that, I do update 3.2 to 3.3 and after that it was KO and so I answered you (second message in this post).

After graylog updated to 3.3 I change this parameter on 2 nodes:

@gsmith

mongodb_uri = mongodb://localhost/graylog,node2.xx.xx:27017/graylog?replicaSet=rs01  <--You Have this
mongodb_uri = mongodb://10.200.6.92:27017,10.200.6.93:27017,10.200.6.94:27017/graylog?replicaSet=replica01  <--Perhaps try this suggestion

• On node 1:
  mongodb_uri = mongodb://localhost:27017,node2.xx.xx:27017,node-quorum.xx.xx:27017/graylog?replicaSet=rs01
• On node 2:
  mongodb_uri = mongodb://localhost:27017,node1.xx.xx:27017,node-quorum.xx.xx:27017/graylog?replicaSet=rs01

I start Graylog and it’s now OK!

So it was - apparently - an error in this mongoDB connection string in graylog configuration… An incompatibility between Graylog 3.2 and 3.3? In any case it’s working now!

So after that, I upgraded 3.3 to 4.2 and it’s OK too: cluster ID not changed and cluster with 2 nodes is up and running.

So for Graylog upgrade it’s OK: done 3.1 to 4.2 upgrade

Now I’ll try to upgrade ES from 6.8.23 to 7.10.2. Hope it will go well…

Thanks again for your research and advices!
Regards,