import and start does not work #422
Replies: 2 comments
-
That should be because you server info from old to a new host. When you initially setup cronicle build script adds current host (the old one) to the master list. When you restore on the new server this is not happening anymore, so new host is not becoming the master. To fix it you need to edit master group regex (like do smth like "storage-cli.js edit server_groups/0", maybe check docs how to do that), or just remove lines starting with "server" on the backup file before restoring. |
Beta Was this translation helpful? Give feedback.
-
Hello mikeTWC1984, Many greetings
|
Beta Was this translation helpful? Give feedback.
-
Hello,
I have a problem with cronicle.
When I start the server (container) for the first time and then ...
"/opt/cronicle/bin/control.sh setup".
"/opt/cronicle/bin/control.sh start"
everything works.
But now I have backups, which I import into the freshly started container, but then cronicle hangs at "Waiting for master server..." and nothing happens.
"/opt/cronicle/bin/control.sh import /cronicle_restore/cronicle_20210707_1551.txt"
"/opt/cronicle/bin/control.sh start"
Do any of you have any idea why this is not working?
cronicle version 0.8.62
node v12.18.3
Container (debian 9.13)
Thanks for your help.
Florian
Beta Was this translation helpful? Give feedback.
All reactions