Sidecar configurations randomly unassigned

Graylog Central (peer support)
1

similar to Graylog 7.0.4 - All Sidecar loses Configuration after server reboot

Graylog sidecar configurations are been randomly unassigned.. There is nothing of value in the graylog server logs.. The screenshot is from this morning, simply shows the logs stopped after the configuration was removed

sidecar logs simply show
time=“2026-04-25T06:28:59Z” level=info msg=“Removing process runner: 6602bb68d26df91e6319377e-686e4709b93dcbb5772bf6bf”
time=“2026-04-25T06:28:59Z” level=info msg=“No configurations assigned to this instance. Skipping configuration request.”
time=“2026-04-25T06:28:59Z” level=info msg=“[filebeat-686e4709b93dcbb5772bf6bf] Stopping”

image
image1834×213 11 KB

We pull in the configuration into git everyday and this morning we saw, random sidecar IDs unassigned (for no reason)

image
image722×200 16.6 KB

image
image853×613 59.5 KB

Graylog version 7.0.6 and sidecar 1.5.2 (both latest)

2

Hey @rodney_vdw,

Do the config drops align with service restarts or is this occurring seemingly at random?

3

It seems to be random, the ones mention were on a Saturday morning, no one was even logged into Graylog and services were not restarted since the last patching to 7.0.6

Loaded: loaded (/usr/lib/systemd/system/graylog-server.service; enabled; preset: enabled) Active: active (running) since Tue 2026-04-21 09:17:27 UTC; 6 days ago

Till now, after adding back the missing sidecars there have been no issues again, will report if there are.

4

@rodney_vdw if it does’t happen again, I would suggest creating an issue here for the quickest resolution.

5

happened again last night - all sidecars had their configurations unassigned.. will create a bug ticket as suggested.