Issue when upgrading 0.2.7 to 0.4.4

[gizmo15]

Hi,

I have an issue when i upgrade from 0.2.7 to 0.4.4.

First, i have this:

Successful operations
synctoken was added to calendars
ctag was removed from calendars
calendarchanges was created
synctoken was added to addressbooks
ctag was removed from addressbooks
addressbookchanges was created
calendarsubscriptions was created
etag and size were added to cards
uid was added to calendarobjects
schedulingobjects was created
propertystorage was created
etag and size was recalculated for cards
warning: skipped record 1. Error: Invalid Mimedir file. Line starting at 3 did not follow iCalendar/vCard conventions
uid was recalculated for calendarobjects
vcardurl was migrated to the propertystorage system

and then, when i click on Acces the Baïkal Admin, i have that:

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

I follow the steps here: http://sabre.io/baikal/upgrade/.

I miss something?

Thanks

[shoopdawoop]

Similar Problem here. All I kept from v0.2.7 was the "Specific" folder.

[shoopdawoop]

So upgrading from v0.2.7 to v0.3.5 first worked fine. Updating to v0.4.4 from there just needed a few permission fixes, now it seems to work fine.

[gizmo15]

okay i will try

[evert]

Odd... I wonder if the upgrade process simply fails because it's not allowed to update the version number. From what I can tell though (from your log), the database upgrade was 100% successful. So one other workaround is to just do a clean 0.4.4 install and just move your (upgraded) database over the empty one....

[evert]

But let me know if you have any more info or if there's anything we can do here...

[pgaufillet]

Hi!

Same error here: the webserver was indeed missing the right to write to config.system.php file due to DAC settings (i.e. AppArmor or SELinux). Adding a preliminary sanity check about it would probably help.

[evert]

Do you know if such a situation is_writable() will return true? I believe that's the check we use.

[pgaufillet]

After a simple test, I confirm is_writable() does return true!

<?php
if(is_writable("/var/www/html/touch"))
    echo "Writable<br/>\n";
else
    echo "Unwritable<br/>\n";
$handle = fopen("/var/www/html/touch", "w");
if(!fwrite($handle,"test_string"))
    echo "Write failed<br/>\n";
else
    echo "Write succeeded<br/>\n";
fclose($handle);

with:

-rwxrwxrwx 1 www-data www-data 0 May 16 19:07 /var/www/html/touch

returns:

Writable
Write failed

[evert]

Interesting... turning this into a bug.

[pincy]

Can confirm this bug.
Even after changing permissions, it didnt retry to set the version in config.system.php.
Changing the version there to the showed 0.5.0 by hand solved the issue for me.

[evert]

If you are running 0.5.0 it means you're running off the git version, which is not a good idea unless you are developer and testing.

[sanderbaas]

Odd... I wonder if the upgrade process simply fails because it's not allowed to update the version number. From what I can tell though (from your log), the database upgrade was 100% successful. So one other workaround is to just do a clean 0.4.4 install and just move your (upgraded) database over the empty one....

This worked for me when updating from 0.2.7 to 0.4.6

[kidexx]

When I upgraded I had the same error with "exception 'PDOException' with message 'SQLSTATE[42S21]: Column already exists: 1060 Duplicate column name 'synctoken'" - I read in another forum the tipp to upgrade first to 0.3.2 in between. This I did and it worked fine.

[tamielbr]

Had similar issues upgrading from 0.2.7->0.4.6, but changing permissions and max_execution_time up in PHP made the upgrade work.

[evert]

Try upgrading to the latest version (0.5.2) some issues related to upgrade have been fixed. I'm closing this issue because it's aging, but if the issue persists please open a new ticket.