"Loading component failed: unknown format:" when loading Sidecar page

[damianharouff]

When loading the Sidecar page in 6.0 rc-2:

I'm not seeing any issues on the network tab:

There's nothing that appears in server.log when loading the Sidecar page too. I've tried the usual front-end tricks like reloading without cache, trying a different browser, etc.

Your Environment

Graylog Version: Graylog 6.0.0-rc.2+9b62575
Java Version: Embedded
OpenSearch Version: 2.13.0
MongoDB Version: 7.0.6
Operating System: Debian 12
Browser version: Chrome Version 123.0.6312.107 (Official Build) (arm64)

[kmerz]

@damianharouff could you please check, if the issue still exists?

Could someone else check if that is a problem, then this would be a blocker!

[mpfz0r]

removing the blocker label. no one else has seen this issue so far

[macorpage]

Same problem in version 6.0 rc-3. Any suggestion?

[mpfz0r]

@macorpage we are still having troubles reproducing this. which browser are you using? does ctrl-shift-reload help?

[macorpage]

Hi @mpfz0r I am using Firefox 124.0.2. I tried ctrl-shift-reload and it opens a new tab and I can see Sidecar Overview but when I change view (eg I click on Streams) and go back to Sidecar Overview I have the same problem. I tried also with Chrome and Edge, same problem and ctrl-shift-reload does not work at all.
The problem occurred after upgrading from graylog 5.2 to 6

Red Hat Enterprise Linux release 9.3
elasticsearch-oss.x86_64 7.10.2-1
graylog-server.x86_64 6.0.0-11.rc.3
mongodb-org.x86_64 6.0.15-1.el9

[mpfz0r]

@macorpage Sorry, I meant using the keyboard combination ctrl-shift-r which reloads the entire page in your browser without using cached frontend assets.

[macorpage]

Hi @mpfz0r, same problem.

[drewmiranda-gl]

For what its worth @mcdowellster also reported this but not sure if he still has the issue.

[dennisoelkers]

Hey @macorpage, is this reproducible right now for you?

[drewmiranda-gl]

I was able to reproduce based off of what ethan said about the sidecar being offline.

1. Install sidecar on an endpoint and start it
2. observe the sidecar appears in /system/sidecars and shows online
3. stop the sidecar service on the endpoint
4. wait for the timeout to occur, once offline the page shows the error

See http://videos.graylog.com/watch/dkPmuRVqur4r2g6ayAJd8o?
Jump ahead to about ~57s to see the it