-
Notifications
You must be signed in to change notification settings - Fork 378
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
Server is not eligible for master after upgrade #474
Comments
What a bizarre problem. I've never heard of this one before. I can assure you that Cronicle never deletes any data. There is no code written anywhere that would go in and surgically remove your master group. That is just utterly bizarre. I'm curious if you grep over your log archives and try to find anything matching Anyway, we need to get the master group re-added, so you'll have to edit two JSON records manually. The first one is the record you included above, but use First, make sure Cronicle is not running for this procedure:
Next, edit this record:
Add your master group like this. Please pay special attention to the {
"type": "list_page",
"items": [
{
"id": "allgrp",
"title": "All Servers",
"regexp": ".+",
"master": 0
},
{
"id": "mastergrp",
"title": "Master Servers",
"regexp": "cronicle",
"master": 1
}
]
} Once you save and exit your editor ( Next, please edit this record (same path, but without the
This is the list header. Make sure the {
"page_size": 50,
"first_page": 0,
"last_page": 0,
"length": 2,
"type": "list"
} Again, save and exit your editor ( Now try starting Cronicle, waiting for one full minute, and see if your server becomes master.
If this process doesn't work, you can try doing a data export, then editing the export file (it's just plain text), make the necessary changes to the list records, then doing an import. Instructions here: https://github.com/jhuckaby/Cronicle#data-import-and-export |
Yay! That did the trick! The thing is that I only installed cronicle, tested a few things and then the project was on hold for some time, so I didn't use it for a long time. I also couldn't find a delete event in the log archives. Thanks for your quick help :) |
Summary
After not having used Cronicle for quite some time I fired it up again today and decided to update everything.
I installed software updates, OS patches and the current LTS version of Node.js. After checking Cronicle I found an available update from 0.8.-something (maybe 4?).
After not finding update instructions I ran the installer again which detected the installation without issues and showed me it does an update.
Having the update completed I wanted to login but got stuck with waiting for master. I waited for a long time and then checked the logs. Cronicle says
Server is not eligible for master -- it will be a slave only
. I dug around a bit and found the troubleshooting guide in the wiki and worked through that.Running
storage-cli.js get global/server_groups/0
revealed that there is actually no master group defined.The server also never changed hostname or IP address, also confirmed using the Node code mentioned in the guide.
Did I simply miss a version step that introduced groups and so I ended up without one? How would I go about adding a group manually?
Any help is appreciated!
Operating system and version?
Debian 10.11 (Buster)
Node.js version?
v16.13.2
Cronicle software version?
v0.9.2
Are you using a multi-server setup, or just a single server?
Single server
Are you using the filesystem as back-end storage, or S3/Couchbase?
Filesystem
Log Excerpts
The text was updated successfully, but these errors were encountered: