-
Notifications
You must be signed in to change notification settings - Fork 129
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
Issues upgrading from 2.0.3 to version 2.1.0 #44
Comments
@garrmark this ansible role is not written to support the upgrade of graylog. should you want to do that, I recommend that you follow the instructions from the graylog docs. |
More information. If I start with a clean OS, and use the same playbook, 2.1 installs and runs fine. I'm using ubuntu/trusty64. So it appears to me something that is set up by the 2.0 install and not removed in the 2.1 upgrade. |
@danvaida in order for the ansible role to be useful, I think it should support an upgrade. I suppose we could do a clean install and restore the index from a backup, but that would require a bit more work. Thoughts? |
Have you seen what's the upgrade path from 1.x to 2.x? A role that would do this, even for minor versions upgrade, on RH & Debian platform would turn into a monster. Imagine the tests coverage for the upgrade part... I'm not the role maintainer but I'm definitely advising against that. Sent from my iPhone
|
Oh, and I'm sorry to hear that you don't find the role useful. Feel free to submit a PR that covers what you want and I'm sure the maintainer will consider it. Sent from my iPhone
|
There's simply another instance of Graylog running (probably the old one). Kill the old instance and start the newly installed version of Graylog. Other than that, @danvaida basically already said the important parts. |
How do you guys do upgrades? I don't need new functionality if there's already a good way to do it. |
I'm trying to upgrade from version 2.0.3 to version 2.1.0:
My 2.0.3 install was done with the Graylog2.graylog-ansible-role and the following config:
I am then upgrading Graylog2.graylog-ansible-role to version 2.1.0 and removing graylog_rest_transport_uri and adding graylog_web_endpoint_uri like so:
I get the following errors after running the playbook which indicate an issue with starting grizzly and the port already in use:
The text was updated successfully, but these errors were encountered: