I accidentally upgraded on my Dev server

Constant errors relating to the default index, unable to rotate indexes, and unable to create a new index.
This error constantly (current default index)
2019-05-07T17:35:37.252+10:00 ERROR [IndexFieldTypePoller] Invalid mapping response: {"graylog_14":{"mappings":{"dynamic_templates":[{"internal_fields":{"match":"gl2_*","mapping":{"type":"keyword"}}},{"store_generic":{"match_mapping_type":"string","mapping":{"type":"keyword"}}}],"properties":{"@metadata_beat":{"type":"keyword"},"@metadata_type":{"type":"keyword"},"@metadata_version":{"type":"keyword"},"@timestamp":{"type":"date"},"beat_hostname":{"type":"keyword"},"beat_name":{"type":"keyword"},"beat_version":{"type":"keyword"},"beats_type":{"type":"keyword"},"collector_node_id":{"type":"keyword"},"full_message":{"type":"text","analyzer":"standard"},"gl2_remote_ip":{"type":"keyword"},"gl2_remote_port":{"type":"keyword"},"gl2_source_collector":{"type":"keyword"},"gl2_source_input":{"type":"keyword"},"gl2_source_node":{"type":"keyword"},"host_name":{"type":"keyword"},"input_type":{"type":"keyword"},"log_file_path":{"type":"keyword"},"message":{"type":"text","analyzer":"standard"},"offset":{"type":"long"},"prospector_type":{"type":"keyword"},"source":{"type":"text","analyzer":"analyzer_keyword","fielddata":true},"streams":{"type":"keyword"},"tags":{"type":"keyword"},"timestamp":{"type":"date","format":"yyyy-MM-dd HH:mm:ss.SSS"}}}}}
This one when I tried to create a new index
2019-05-07T17:35:40.782+10:00 WARN [IndexFieldTypePollerPeriodical] Active write index for index set "V7Default" (5cd1354cc132055efc2747fe) doesn't exist yet
2019-05-07T17:35:40.791+10:00 INFO [connection] Opened connection [connectionId{localValue:9, serverValue:16}] to localhost:27017
2019-05-07T17:35:41.751+10:00 INFO [MongoIndexSet] Did not find a deflector alias. Setting one up now.
2019-05-07T17:35:41.752+10:00 INFO [MongoIndexSet] There is no index target to point to. Creating one now.
2019-05-07T17:35:41.753+10:00 INFO [MongoIndexSet] Cycling from <none> to <v7default_0>.
2019-05-07T17:35:41.753+10:00 INFO [MongoIndexSet] Creating target index <v7default_0>.
2019-05-07T17:35:41.754+10:00 ERROR [IndexRotationThread] Couldn't point deflector to a new index
org.graylog2.indexer.ElasticsearchException: Unsupported Elasticsearch version: 7.0.1
at org.graylog2.indexer.IndexMappingFactory.createIndexMapping(IndexMappingFactory.java:41) ~[graylog.jar:?]
at org.graylog2.indexer.indices.Indices.ensureIndexTemplate(Indices.java:363) ~[graylog.jar:?]
at org.graylog2.indexer.indices.Indices.create(Indices.java:411) ~[graylog.jar:?]
at org.graylog2.indexer.indices.Indices.create(Indices.java:397) ~[graylog.jar:?]
at org.graylog2.indexer.MongoIndexSet.cycle(MongoIndexSet.java:293) ~[graylog.jar:?]
at org.graylog2.indexer.MongoIndexSet.setUp(MongoIndexSet.java:261) ~[graylog.jar:?]
at org.graylog2.periodical.IndexRotationThread.checkAndRepair(IndexRotationThread.java:138) ~[graylog.jar:?]
at org.graylog2.periodical.IndexRotationThread.lambda$doRun$0(IndexRotationThread.java:76) ~[graylog.jar:?]
at java.lang.Iterable.forEach(Iterable.java:75) [?:1.8.0_212]
at org.graylog2.periodical.IndexRotationThread.doRun(IndexRotationThread.java:73) [graylog.jar:?]
at org.graylog2.plugin.periodical.Periodical.run(Periodical.java:77) [graylog.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_212]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_212]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_212]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_212]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_212]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_212]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]
FYI, I believe there is no way to downgrade a database once it’s updated, so it’s start from scratch time.
Remember to check your yum auto update settings!