Failed to migrate from Graylog Enterprise 5.2.4 to 6.0


Graylog doesnt start after having upgraded its version from 5.2.4 to 6.0.1, with the error hereafter visible in the logs.

We are using Graylog Enterprise, running it on Ubuntu 20.04 focal with ElasticSearch 7.10.2 and MongoDB 7.0.9 (MongoDB was upgraded from 6.0.6 during installation of Graylog 6).

Any help would be appreciated.

2024-05-21T14:12:18.476Z WARN  [RestClient] request [PUT] returned 1 warnings: [299 Elasticsearch-7.10.2-747e1cc71def077253878a59143c1f785afa92b9 "'y' year should be replaced with 'u'. Use 'y' for year-of-era. Use new java.time date format specifiers."]
2024-05-21T14:12:18.516Z ERROR [ServerBootstrap] Exception while running migrations Unable to update index mapping gl-events_3
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at org.graylog.plugins.securityapp.migrations.V20240130141000_UpdateEventsIndexMapping.lambda$upgrade$0( ~[?:?]
        at java.base/java.util.Optional.ifPresent(Unknown Source) ~[?:?]
        at org.graylog.plugins.securityapp.migrations.V20240130141000_UpdateEventsIndexMapping.lambda$upgrade$1( ~[?:?]
        at ~[graylog.jar:?]
        at org.graylog.plugins.securityapp.migrations.V20240130141000_UpdateEventsIndexMapping.upgrade( ~[?:?]
        at org.graylog2.bootstrap.ServerBootstrap.lambda$runMigrations$3( ~[graylog.jar:?]
        at java.base/$ForEachOp$OfRef.accept(Unknown Source) ~[?:?]
        at java.base/$2$1.accept(Unknown Source) ~[?:?]
        at$1WithCharacteristics.lambda$forEachRemaining$1( ~[graylog.jar:?]
        at java.base/$RangeIntSpliterator.forEachRemaining(Unknown Source) ~[?:?]
        at$1WithCharacteristics.forEachRemaining( ~[graylog.jar:?]
        at java.base/ Source) ~[?:?]
        at java.base/ Source) ~[?:?]
        at java.base/$ForEachOp.evaluateSequential(Unknown Source) ~[?:?]
        at java.base/$ForEachOp$OfRef.evaluateSequential(Unknown Source) ~[?:?]
        at java.base/ Source) ~[?:?]
        at java.base/ Source) ~[?:?]
        at org.graylog2.bootstrap.ServerBootstrap.runMigrations( ~[graylog.jar:?]
        at org.graylog2.bootstrap.ServerBootstrap.startCommand( [graylog.jar:?]
        at org.graylog2.bootstrap.CmdLineTool.doRun( [graylog.jar:?]
        at [graylog.jar:?]
        at org.graylog2.bootstrap.Main.main( [graylog.jar:?]
Caused by: Elasticsearch exception [type=illegal_argument_exception, reason=Error parsing [format] on field [timerange_end]: Invalid format: [uuuu-MM-dd HH:mm:ss.SSS]: Illegal pattern component: uuuu]
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at ~[?:?]
        at$updateIndexMapping$4( ~[?:?]
        at ~[?:?]
        ... 23 more

You have run into a compatibility issue with ES6/ES7. I’m guessing the offending index was created with ES6? This causes ES7 to still apply legacy date format.

Looks like GL 6.0 uses some format strings that are not backwards compatible with ES6. That seems like a bug. I filed an issue.

An easy workaround is to ignore the migration failure by setting this in your graylog.conf:
ignore_migration_failures = true
The failing migration is specific to the Security product, which isn’t even available with ES. So you can safely ignore it.

Issue is fixed - will be included in the next bugfix release.

Meanwhile, setting ignore_migration_failures = true is your best workaround.

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