-
Notifications
You must be signed in to change notification settings - Fork 293
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
Duplicate column name 'synctoken' during upgrade #589
Comments
Also I have saved before and after snapshots as this was testing in a vm. I also have this running in a production environment so please let me know what else I can provide. Thank you. |
Hey! sorry for not messaging here earlier. Generally the cause for this particular error is as follows:
This error is the error that would appear when trying upgrading again after a failed earlier upgrade. So in order for me to help figure out what went wrong and to fix this bug, I really need the original error. The only way you (@DigiAngel @joschal) can get this information if you go back to your original 0.2.7 backup, attempt the upgrade again and describe the symptoms =) |
Piece of cake...I'll try this after restoring my original Ubuntu 14.04/Baikal 0.2.7 setup. I'll get that to you tomorrow...thanks Evert! |
Ok this time the upgrade went fine...so I'm going to guess that the damaged php might have had an impact my last try. Anyway here's my process:
I will most likely do a mysqldump when I do the upgrade in production. At this point I'mma close this ticket out..thanks Evert! |
Good to hear! |
I followed the instructions of @DigiAngel but unfortunately still got this error.
More suggestions? |
I also turned off all devices that might sync with the server. |
Hi @joschal , Is it possible that you messed up with your previous backup? If you didn't make a backup before the upgrade process you're basically stuck here. |
I did several backups. Currently I'm back at 0.2.7 and it works fine. |
Do you think there is a chance of fixing the issue? Might there be a version in between where the upgrade works? Thanks for your fast support |
Nothing really has changed. The part of the upgrade code that this is hitting is from 0.3.0, which runs because you're upgrading from an older version. So as of right now I don't have an answer. I maintain that the error is actually happining earlier, and the real error you are seeing is a side-effect of running the upgrade again, after a previous failed one. However, I have a manual upgrade process that you can try. Requires some console skills though. sabre/dav ships with a command-line upgraders that provides more feedback. It's shipped with baikal. You'll need to run the following commands:
You must run them in order, and please report if one of them failed and with what error. When you first run the commands, it gives you some information on what arguments it needs. Specifically, you will need to pass it information on how to connect to your database. After all that you can change a configuration file in the Let me know if that works! |
Topic says it...looks like I've got a mysql-ish snafu or something...I get the below after:
not sure where to turn next. Thank you.
The text was updated successfully, but these errors were encountered: