Graylog not starting after upgrade to 3.1 #6322
After upgrading from 3.0 to 3.1 graylog did not start anymore. Graylog server started it's startup process but failed when connecting to the mongodb.
Graylog server should start
Graylog service stops shortly after starting with the following log message:
I have obfuscated the real clustername and mongodb host, though the actual cluster would have 20 characters. It seems to hit a hard limit in mongodb versions before 4.2: https://docs.mongodb.com/manual/reference/limits/#Index-Name-Length
Upgrade to mongodb 4.2 or higher (untested) or downgrade to graylog 3.0 (tested). Also maybe a shorter cluster name might work, though that is not really a solution in our case.
Steps to Reproduce (for bugs)
I tried to test the upgrade to graylog 3.1 on a test cluster. No production impact.
The text was updated successfully, but these errors were encountered:
@JTabel Thank you for the report!
With cluster name you mean the database name? The complete index name in the error message seems to be less than 127 characters.
We will change the index name in the next bug fix release so it's not an issue anymore in the future.
Using the auto generated one can become a problem with the 127 character limit in MongoDB if the database name is long. Fixes #6322