Marco Pfatschbacher

@H2Cyber I think the easiest workaround for now is to manually stop the Sidecar Windows service. Once it's stopped, you can run the 1.2 Sidecar installer and perform a regular...

Maybe a safe way is to fully uninstall the service first: ``` "C:\Program Files\Graylog\graylog-sidecar.exe" -service stop "C:\Program Files\Graylog\graylog-sidecar.exe" -service uninstall ``` This might be needed to apply our fix for...

@H2Cyber Yeah, it would :-( see #365 But you could copy the `node-id` file and restore it afterwards. That should do the trick.

@will-graylog if you are looking under the collector overview, and click on the collector name, you can see the details here:  Refs https://github.com/Graylog2/graylog2-server/pull/5208

@will-graylog @mikedklein did you see my comment above? Can we close this?

> edit: from testing, the assumed NODEID flag worked! That can't be right. The only supported flags are: https://github.com/Graylog2/collector-sidecar/blob/master/dist/recipe.nsi#L181-L186

What would be useful is a `/H` help switch in the installer that shows all options

Could that be because the node-id was already persisted in the node-id file from a previous install?

@MahdiGhiasi could you run your graylog in docker-compose with a debugging entry point for us and give us the output? ` entrypoint: "/bin/bash -c 'find /usr/share/graylog -type d -ls'"`

This seems to be where this happens: But I don't see why there is a regression between 4.3.3 and 4.3.4 https://github.com/Graylog2/graylog-docker/blob/4.3/docker-entrypoint.sh#L91-L94 ```setup() { # Create data directories for d in...