Skip to content
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

If gdev is reloaded gdev sync will go to inconsistent state #11

Open
onnimonni opened this issue Aug 19, 2016 · 0 comments
Open

If gdev is reloaded gdev sync will go to inconsistent state #11

onnimonni opened this issue Aug 19, 2016 · 0 comments
Assignees

Comments

@onnimonni
Copy link

Steps to reproduce:

$ gdev up
$ gdev reload
$ gdev sync

Then I can see that the sync fails:

$ gdev sync
INFO: Syncing files to data container with unison, using port 32779...
Contacting server...
Connected [//data-container//var/www/project -> //dev-machine//Users/henrikuittinen/Sources/asunnot.keva.fi]
Looking for changes
Fatal error: Warning: inconsistent state.
The archive file is missing on some hosts.
For safety, the remaining copies should be deleted.
  Archive ar33a3dac36ed37c0d952a172a45ded906 on host dev-machine should be DELETED
  Archive ar87132acb83c8baf3468e5ac97f28636b on host data-container is MISSING
Please delete archive files as appropriate and try again
or invoke Unison with -ignorearchives flag.
INFO: Sync is ready!

I think this can be fixed by adding -ignorearchives to the gdev sync command.

I think it happens because the data container is reloaded and it triggers data container hostname to change as well and because of that unison thinks it is inconsistent even though everthing is okay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants