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

Cannot load alert callbacks created on 1.0 #1428

edmundoa opened this Issue Sep 17, 2015 · 1 comment


None yet
2 participants

edmundoa commented Sep 17, 2015

Graylog 1.2.0 can't load alert callbacks created with Graylog 1.0 or earlier. The problem is that the MongoDB documents for those old alerts contain two ID fields: _id, and id. The first one is an ObjectId whereas the second one is a string, and that is confusing MongoJack when loading the objects.

A temporary solution while we try to fix it in a better way, is to run this MongoDB command:
db.alarmcallbackconfigurations.update({"id": {$exists: true}}, {$unset: {"id": ""}}, { multi: true })

Note: Don't forget to backup your MongoDB if you run the previous command. Please stop Graylog server before doing it, and only restart it after the backup and the update command are completed.

@edmundoa edmundoa added the bug label Sep 17, 2015

@edmundoa edmundoa self-assigned this Sep 17, 2015

@edmundoa edmundoa added this to the 1.2.1 milestone Sep 17, 2015

edmundoa added a commit that referenced this issue Sep 18, 2015

Remove duplicated ID field from alarm callbacks
Alarm callbacks created before 1.1 have a duplicated ID field, which
confuses MongoJack when loading the objects from MongoDB. Here we add a
periodical to migrate those alarm callbacks, removing the duplicated
`id` field to ensure we can load the objects.

Fixes #1428

edmundoa added a commit that referenced this issue Sep 21, 2015

@joschi joschi closed this Sep 21, 2015


This comment has been minimized.


edmundoa commented Sep 21, 2015

Thank you for the review!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment