# All dashboards lost after upgrade from 3.1.x to 3.2.1

**URL:** https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897
**Category:** Graylog Central (peer support)
**Created:** [February 11, 2020, 11:41am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897 "2020-02-11T11:41:07Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![rsa](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rsa](https://community.graylog.org/u/rsa)
#### Post date: [February 11, 2020, 11:41am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/1 "2020-02-11T11:41:07Z")

</div>

Hi!  
After upgrade to 3.2 I’ve lost all (~50) dashboards with hundreds of widgets.  
Following meaningful error is thrown:

> 2020-02-11T10:36:40.194+02:00 ERROR [ConfigurationManagementPeriodical] Error while running migration \<V20191125144500\_MigrateDashboardsToViews{2019-11-25T14:45:00Z}\>  
> java.lang.RuntimeException: Unable to parse function: avg(time-taken)  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.viewwidgets.Series.toSeriesSpec(Series.java:60) ~[graylog.jar:?]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.AggregationWidget.lambda$toSearchTypes$2(AggregationWidget.java:82) ~[graylog.jar:?]  
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0\_212]  
> at java.util.Collections$2.tryAdvance(Collections.java:4717) ~[?:1.8.0\_212]  
> at java.util.Collections$2.forEachRemaining(Collections.java:4725) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[?:1.8.0\_212]  
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0\_212]  
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[?:1.8.0\_212]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.AggregationWidget.toSearchTypes(AggregationWidget.java:82) ~[graylog.jar:?]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.V20191125144500\_MigrateDashboardsToViews.createSearchType(V20191125144500\_MigrateDashboardsToViews.java:186) ~[graylog.jar:?]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.V20191125144500\_MigrateDashboardsToViews.lambda$migrateDashboard$5(V20191125144500\_MigrateDashboardsToViews.java:154) ~[graylog.jar:?]  
> at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267) ~[?:1.8.0\_212]  
> at java.util.Iterator.forEachRemaining(Iterator.java:116) ~[?:1.8.0\_212]  
> at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[?:1.8.0\_212]  
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0\_212]  
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[?:1.8.0\_212]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.V20191125144500\_MigrateDashboardsToViews.migrateDashboard(V20191125144500\_MigrateDashboardsToViews.java:155) ~[graylog.jar:?]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.V20191125144500\_MigrateDashboardsToViews.lambda$upgrade$0(V20191125144500\_MigrateDashboardsToViews.java:90) ~[graylog.jar:?]  
> at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0\_212]  
> at java.util.ArrayList.forEach(ArrayList.java:1257) ~[?:1.8.0\_212]  
> at java.util.stream.SortedOps$RefSortingSink.end(SortedOps.java:390) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:483) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[?:1.8.0\_212]  
> at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0\_212]  
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0\_212]  
> at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) ~[?:1.8.0\_212]  
> at org.graylog.plugins.views.migrations.V20191125144500\_MigrateDashboardsToViewsSupport.V20191125144500\_MigrateDashboardsToViews.upgrade(V20191125144500\_MigrateDashboardsToViews.java:91) ~[graylog.jar:?]  
> at org.graylog2.periodical.ConfigurationManagementPeriodical.doRun(ConfigurationManagementPeriodical.java:43) [graylog.jar:?]  
> at org.graylog2.plugin.periodical.Periodical.run(Periodical.java:77) [graylog.jar:?]  
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_212]

After master node restart the same error message is thrown. Is there something i can do to resolve this?  
Thanks!

---

<div class="post-metadata">

### Author: ![rsa](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rsa](https://community.graylog.org/u/rsa)
#### Post date: [February 12, 2020, 6:38am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/2 "2020-02-12T06:38:42Z")

</div>

Dashboards are obviously there (in a mongodb collection) but migration script could not migrate them. I’ve tried to export/import mongodb dashboard collection to 3.1 test environment I have for a later creation of content pack on that 3.1 version and uploading this content pack on 3.2 version afterwards as a workaround but this also failed (i could import mongodb data, create content pack on version 3.1, could upload it on 3.2 but it is failing to install).  
I had one custom content pack with dashboards which was uploaded but not installed previously and this pack installed successfully so basically version 3.1 content packs are at some level compatible with 3.2 but still I could not install successfully content pack from that temporary 3.1 test environment into 3.2 version even with only 1 dashboard and 3 simple widgets.  
Can someone assist me on how to migrate those as it will take many days to recreate them manually.

---

<div class="post-metadata">

### Author: ![ericMont](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/ericmont/32/5796_2.png) [@ericMont](https://community.graylog.org/u/ericMont)
#### Post date: [February 12, 2020, 8:11am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/3 "2020-02-12T08:11:32Z")

</div>

same error here after migration

ERROR [ConfigurationManagementPeriodical] Error while running migration \<V20191125144500\_MigrateDashboardsToViews{2019-11-25T14:45:00Z}\>

from graylog-3.1-repository\_latest.deb to graylog-3.2-repository\_latest.deb

please advise

---

<div class="post-metadata">

### Author: ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)
#### Post date: [February 12, 2020, 11:16am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/4 "2020-02-12T11:16:32Z")

</div>

he @ericMont

you did not share enough from your error. But you might run into the issue mentioned here:

> <https://github.com/Graylog2/graylog2-server/issues/7439>
>
> Expected Behavior
> The views migration should run with a series containing a dash (-) in the field name.
> Current Behavior
> The migration breaks up...

---

<div class="post-metadata">

### Author: ![rsa](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rsa](https://community.graylog.org/u/rsa)
#### Post date: [February 12, 2020, 11:24am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/5 "2020-02-12T11:24:45Z")

</div>

Just found this bug. Checked and i don’t have dashes though i have underscores in field names of series. Is this bug relevant to my problem or it is a whole different story?

---

<div class="post-metadata">

### Author: ![ec10](https://avatars.discourse-cdn.com/v4/letter/e/4da419/32.png) [@ec10](https://community.graylog.org/u/ec10)
#### Post date: [February 12, 2020, 11:29am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/6 "2020-02-12T11:29:06Z")

</div>

Hello, we have updated Graylog with 3.1.x to 3.2.1 and all our dashboards have disappeared

we get an error in the log:  
2020-02-12T11: 53: 18.952+01: 00 error [MongoDB Processing Status Recorder Service] failed to save the processing state  
2020-02-12T12: 08: 55.870+01: 00 error [periodic configuration management] error when performing migration \<V20191125144500\_MigrateDashboardstoviews{2019-11-25T14: 45: 00Z}\>

Graylog-server 3.2.1  
MongoDB 3.6.17  
Elasticsearch in 5.6.16

---

<div class="post-metadata">

### Author: ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)
#### Post date: [February 12, 2020, 11:31am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/7 "2020-02-12T11:31:14Z")

</div>

he @rsa  
please add this information to the issue - because that might be related and the devs can check for that too

---

<div class="post-metadata">

### Author: ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)
#### Post date: [February 12, 2020, 11:32am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/8 "2020-02-12T11:32:27Z")

</div>

he @ec10

sorry that you run into problems - but with the provided information it is not possible to identify the issue. It might be related to your MongoDB version. But that is just guessing. Because it might be something else.

---

<div class="post-metadata">

### Author: ![rsa](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rsa](https://community.graylog.org/u/rsa)
#### Post date: [February 14, 2020, 9:34am UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/9 "2020-02-14T09:34:24Z")

</div>

Cause of my problem indeed is as described in bug ([https://github.com/Graylog2/graylog2-server/issues/7439](https://github.com/Graylog2/graylog2-server/issues/7439)). As this affected only few percents of all widgets (I’ve hundreds of widgets and only some 20 included dash in a field name) I exported dashboard collection from mongodb, deleted those widgets there, cleared/truncated dashboard collection and imported back collection with affected widgets removed. Migration script succeeded. Will add those ~20 manually later.

---

<div class="post-metadata">

### Author: ![alexk](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@alexk](https://community.graylog.org/u/alexk)
#### Post date: [February 17, 2020, 2:46pm UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/10 "2020-02-17T14:46:16Z")

</div>

This will be fixed in 3.2.2. Underscores should always have worked, but dashes and @ haven’t. See [https://github.com/Graylog2/graylog2-server/pull/7448](https://github.com/Graylog2/graylog2-server/pull/7448)

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)
#### Post date: [March 2, 2020, 2:51pm UTC](https://community.graylog.org/t/all-dashboards-lost-after-upgrade-from-3-1-x-to-3-2-1/13897/11 "2020-03-02T14:51:59Z")

</div>

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