You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to share a dashboard, the following error happens:
java.lang.RuntimeException: IOException encountered while reading from a byte array input stream
Unhandled exception in REST resource
java.lang.RuntimeException: IOException encountered while reading from a byte array input stream
at org.mongojack.internal.stream.JacksonDBDecoder.decode(JacksonDBDecoder.java:67) ~[graylog.jar:?]
at org.mongojack.JacksonDBCollection.findOneById(JacksonDBCollection.java:1291) ~[graylog.jar:?]
at org.graylog.plugins.views.search.db.SearchDbService.get(SearchDbService.java:72) ~[graylog.jar:?]
at org.graylog.plugins.views.search.views.RequiresParameterSupport.test(RequiresParameterSupport.java:43) ~[graylog.jar:?]
org.graylog.plugins.views.search.searchtypes.pivot.buckets.AutoValue_Time$Builder["interval"])
Caused by: java.lang.IllegalArgumentException: Time unit must be {quantity}{unit}, where quantity is a positive number and unit [smhdwM].
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:142) ~[graylog.jar:?]
This appears to be happen when invalid pivots were entered through the UI (was previously possible due to a bug).
See related issue/PR
Related to this issue/PR, where invalid pivots entered through the UI. #7195 #7196
Solution
To fix the issue, the invalid time unit will need to be identified and manually fixed with a Mongo command. The unit should be a number and a valid unit, for example 365d. Although this might not be the correct mongo command for every instance of this issue, I am documenting it here for reference.
Overview
When attempting to share a dashboard, the following error happens:
This appears to be happen when invalid pivots were entered through the UI (was previously possible due to a bug).
See related issue/PR
Related to this issue/PR, where invalid pivots entered through the UI.
#7195
#7196
Solution
To fix the issue, the invalid time unit will need to be identified and manually fixed with a Mongo command. The unit should be a number and a valid unit, for example
365d
. Although this might not be the correct mongo command for every instance of this issue, I am documenting it here for reference.HS800430336
The text was updated successfully, but these errors were encountered: