-
Notifications
You must be signed in to change notification settings - Fork 56
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
Upgrading sidecar from 1.1 to 1.2 #432
Comments
I think the easiest workaround for now is to manually stop the Sidecar Windows service. An alternative would be to use our Chocolatey package, which does that automatically. |
Maybe a safe way is to fully uninstall the service first:
This might be needed to apply our fix for #421 |
@mpfz0r thanks. Would uninstalling and reinstalling create a new sidecar entry in Graylog ? Or would Graylog recognise the fact that the endpoint is the same ? |
Hello, I would like to ask You folks if someone has same experience and maybe a some solution. I have a WinServer2019, sidecar v1.1.0 with unknown status in GL. I was thinking the upgrade to v1.2.0 can solve problem with connection to GL. After upgrade and replacement of files sidecar.yml and node-id from backup the sidecar upgade was visible on GL server after aprox 2hrs and the problem with unknown status remains. What is different is node-id has been changed after all. Thank You so much in advance. Regards, Jan. |
@Jenda2022 the unknown status has likely a different cause. Have you checked the logs of the sidecar and graylog for any errors? |
Hello, I checked the sidecar in debug mode: time="2022-10-07T20:04:14+02:00" level=info msg="Starting signal distributor" |
I have a fleet of Windows Sidecar v1.1 and I want to upgrade them to 1.2.
What would be the simplest recommended way to do so ? Do I have to I uninstall v1.1 first ?
The text was updated successfully, but these errors were encountered: