Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot read property 'query' of undefined when replaying search #6355

Closed
viebig opened this issue Aug 26, 2019 · 3 comments · Fixed by #6432

Comments

@viebig
Copy link

commented Aug 26, 2019

Expected Behavior

Be able to run queries and see messages

Current Behavior

Impossible to show input messages, when clicking replay query from dashboard, monkey error page appear with the following message:

Cannot read property 'query' of undefined Stack Trace: TypeError: Cannot read property 'query' of undefined at t.Z3h2JH4w.t.getSeriesInformation (http://xxx/assets/builtins.60a2621478c6c8ca385c.js:104:99716) ....

Context

Issue happened after upgrading graylog from 3.1.x to 3.1.0-6

Your Environment

  • Graylog Version: 3.1.0-6
  • Elasticsearch Version: 6.8.2
  • MongoDB Version: 4.0.12
  • Operating System: Ubuntu
  • Browser version: Chrome 73.0.3683.86 (Official Build) (64-bit)
@florianvolle florianvolle added the search label Aug 28, 2019
@kmerz kmerz removed their assignment Sep 2, 2019
@dennisoelkers

This comment has been minimized.

Copy link
Member

commented Sep 2, 2019

Hello @viebig,

we need some additional help from you debugging this issue. Can you please open up the Graylog Web Interface, go to your browser's JavaScript console, type JSON.stringify(localStorage) and add the output to this issue?

@viebig

This comment has been minimized.

Copy link
Author

commented Sep 2, 2019

Works on firefox, issue just exists with chrome.

"{"pinned-field-charts":"{\"q2ac8vus82039ab2nvnqa6nseh44bhnzmde2\":{\"renderer\":\"bar\",\"interpolation\":\"linear\",\"interval\":\"minute\",\"query\":\"gl2_source_input:5b2a7641eac5e70b59f98850 AND callStatus:CONGESTION AND classifierType:AMD\",\"valuetype\":\"count\",\"rangetype\":\"relative\",\"chartid\":\"q2ac8vus82039ab2nvnqa6nseh44bhnzmde2\",\"field\":\"callStatus\",\"createdAt\":1532720159374,\"range\":{\"relative\":300}},\"4ckehkcwlcrm6hr47t6knb3l5kpi2hrvibef\":{\"renderer\":\"bar\",\"interpolation\":\"linear\",\"interval\":\"minute\",\"query\":\"gl2_source_input:5b2a7641eac5e70b59f98850 AND callStatus:SILENCE AND classifierType:AMD\",\"valuetype\":\"count\",\"rangetype\":\"relative\",\"chartid\":\"4ckehkcwlcrm6hr47t6knb3l5kpi2hrvibef\",\"field\":\"callStatus\",\"createdAt\":1532720197871,\"range\":{\"relative\":300}},\"iz90mmxb8cwmlb0966z1p2u3h8kwvr5kz8o9\":{\"renderer\":\"area\",\"interpolation\":\"basis\",\"interval\":\"minute\",\"query\":\"gl2_source_input:5b2a7641eac5e70b59f98850 AND callStatus:MACHINE AND classifierType:AMD\",\"valuetype\":\"count\",\"rangetype\":\"relative\",\"chartid\":\"iz90mmxb8cwmlb0966z1p2u3h8kwvr5kz8o9\",\"field\":\"callStatus\",\"createdAt\":1532720210584,\"range\":{\"relative\":0}},\"simuhf0m9kqo03h9f78z2od2nsu8ulwhwcvc\":{\"renderer\":\"bar\",\"interpolation\":\"linear\",\"interval\":\"minute\",\"query\":\"gl2_source_input:5b2a7641eac5e70b59f98850 AND callStatus:NOANSWER AND classifierType:AMD\",\"valuetype\":\"count\",\"rangetype\":\"relative\",\"chartid\":\"simuhf0m9kqo03h9f78z2od2nsu8ulwhwcvc\",\"field\":\"callStatus\",\"createdAt\":1532720187318,\"range\":{\"relative\":0}}}","sessionId":"\"ff229fbd-3011-4ecc-aa79-df057d932a18\"","stacked-graphs":"{\"iz90mmxb8cwmlb0966z1p2u3h8kwvr5kz8o9\":[\"3q22jpcjvflghly48bqth8yk0a6t3rpgf64k\",\"q2ac8vus82039ab2nvnqa6nseh44bhnzmde2\",\"hltj85691y3rm04vtni1oi9rby5w4ojhjiwp\",\"simuhf0m9kqo03h9f78z2od2nsu8ulwhwcvc\",\"4ckehkcwlcrm6hr47t6knb3l5kpi2hrvibef\"]}","username":"\"admin\""}"
@no-response no-response bot removed the needs-input label Sep 2, 2019
@dennisoelkers

This comment has been minimized.

Copy link
Member

commented Sep 11, 2019

@viebig: This is an issue in 3.1.0/3.1.1. It seems like a stacked graph on the search page has lost some of its subgraphs. Do you have any idea how this could have happened?

We are addressing this in one of the next versions (3.1.2, if we are fast enough with the fix). For now you can enter the following command in your browser's JS console while being on the Graylog web if, to restore your search page:

delete localStorage['stacked-graphs']

This will remove the erroneous stacked graph and restore the remaining individual graphs, which you can stack again.

@dennisoelkers dennisoelkers added this to the 3.1.2 milestone Sep 11, 2019
@dennisoelkers dennisoelkers added bug and removed to-verify labels Sep 11, 2019
dennisoelkers added a commit that referenced this issue Sep 11, 2019
Before this change, stacked charts on the current search page could
reference a nonexisting subchart (see #6355 for an example), leading to
a nonfunctioning search page where the user is not able to remove the
faulty chart to restore it.

This change is adding subcharts conditionally, skipping them if the
given reference cannot be resolved. Therefore, even stacked chart
definitions which reference nonexisting subcharts can be displayed
(partially) correct.

Fixes #6355.
@mpfz0r mpfz0r closed this in #6432 Sep 12, 2019
mpfz0r added a commit that referenced this issue Sep 12, 2019
Before this change, stacked charts on the current search page could
reference a nonexisting subchart (see #6355 for an example), leading to
a nonfunctioning search page where the user is not able to remove the
faulty chart to restore it.

This change is adding subcharts conditionally, skipping them if the
given reference cannot be resolved. Therefore, even stacked chart
definitions which reference nonexisting subcharts can be displayed
(partially) correct.

Fixes #6355.
mpfz0r added a commit that referenced this issue Sep 12, 2019
Before this change, stacked charts on the current search page could
reference a nonexisting subchart (see #6355 for an example), leading to
a nonfunctioning search page where the user is not able to remove the
faulty chart to restore it.

This change is adding subcharts conditionally, skipping them if the
given reference cannot be resolved. Therefore, even stacked chart
definitions which reference nonexisting subcharts can be displayed
(partially) correct.

Fixes #6355.

(cherry picked from commit dbd1e44)
dennisoelkers added a commit that referenced this issue Sep 12, 2019
)

Before this change, stacked charts on the current search page could
reference a nonexisting subchart (see #6355 for an example), leading to
a nonfunctioning search page where the user is not able to remove the
faulty chart to restore it.

This change is adding subcharts conditionally, skipping them if the
given reference cannot be resolved. Therefore, even stacked chart
definitions which reference nonexisting subcharts can be displayed
(partially) correct.

Fixes #6355.

(cherry picked from commit dbd1e44)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.