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

Issue when upgrating Baikal #683

Closed
ladetto opened this issue Apr 19, 2017 · 5 comments
Closed

Issue when upgrating Baikal #683

ladetto opened this issue Apr 19, 2017 · 5 comments

Comments

@ladetto
Copy link

ladetto commented Apr 19, 2017

Hello!

sorry to disturb you, but I just wanted to upgrade Baikal from version 0.2.7 to 0.4.6 and I got the message at the end of this email:
I have the instrance running under : https://baikal.ladetto.ch
I got this message when accessing: https://baikal.ladetto.ch/html/admin

I thank you in advance for any support!

Best regards,

Quentin

Errors
Uncaught exception during upgrade: exception 'PDOException' with message 'SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'synctoken'' in /home/ladetto/baikal.ladetto.ch/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php:102 Stack trace: #0 /home/ladetto/baikal.ladetto.ch/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php(102): PDO->exec('ALTER TABLE cal...') #1 /home/ladetto/baikal.ladetto.ch/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php(61): BaikalAdmin\Controller\Install\VersionUpgrade->upgrade('0.2.7', '0.4.6') #2 /home/ladetto/baikal.ladetto.ch/Core/Frameworks/Flake/Core/Render/Container.php(71): BaikalAdmin\Controller\Install\VersionUpgrade->render() #3 /home/ladetto/baikal.ladetto.ch/Core/Frameworks/Flake/Controller/Page.php(85): Flake\Core\Render\Container->renderBlocks() #4 /home/ladetto/baikal.ladetto.ch/html/admin/install/index.php(83): Flake\Controller\Page->render() #5 {main}

@derStephan
Copy link

derStephan commented Apr 21, 2017

I had the very same problem which was due to the fact that PHP stopped execution too early to complete the upgrade.

You need to raise the maximum execution time. Otherwise, the script will be stopped after 30s in the middle of the upgrade process and your data will be corrupted.

This gets worse with each entry you have in the database.

So, restore your backup, raise maximum execution time a lot and run the upgrade script again.

To raise maximum execution time, try adding

ini_set('max_execution_time', 3000); //3000 seconds = 50 minutes

to line 1 in the baikal-file /html/admin/install/index.php

right after <?php

Then run your upgrade and be patient.

P.S: You are not the first one to encounter this problem: #665 or #573

@ladetto
Copy link
Author

ladetto commented Apr 21, 2017

Dear Stefan,
Thanks a lot! it worked like a charm!
Best regards,
Quentin

@derStephan
Copy link

@ladetto May I ask how many contacts and events your installation holds? How long did the upgrade process take?

@ladetto
Copy link
Author

ladetto commented Apr 21, 2017

hello! I have 1600 contacts and the entries in the calendar must be around 500... I don't know the exact time, but after 5 minutes it was done. Sorry, not to be more precise, but I was working on another tab...

@evert
Copy link
Member

evert commented Apr 27, 2019

We've been pretty quiet because the project hasn't had an active maintainer for a while. There's recently been a new release that might solve some of these problems.

It's been a while since your message so I assume you either moved on or solved it. If not, give the latest version a shot and comment here if you're running into problems.

@evert evert closed this as completed Apr 27, 2019
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

3 participants