Upgrading from 0.2.7 to 0.4.5 fails

[Wecoboss]

First of all, great work for Baikal !

I want to upgrade by baikal instance from 0.2.7 to 0.4.5 but I can't make it work on my server.

Here is my process :

• creation a brand new server with apache and mysql
• download and extraction of the baikal zip 0.4.5 in the web server folder
• set up of the virtualhost with the rewrite rules
• import of my previous Specific folder + mysql import
• navigation to the baikal url that redirects to the admin section

But NOTHING HAPPENS until the server crash for execution too long. The webserver log shows that I was on the good page /admin/install/.

I have tried to set the max_execution_time to 300 and to push the php memory to 512 MB but it doesn't change anything. I still get the same issue. I have around 3000 events and 700 contacts.

I don't see any errors anywhere (apache or mysql).

Thanks in advance for your help.

[evert]

The likely problem here is that you simply need to wait even longer. This is frustrating, but I guarantee that the upgrade is happening in the background.

Try set max_execution time to something ridiculous like 1800 (for 30 minutes). It might be enough to get to completion.

There is also a manual command-line upgrade possible. It's more obvious stuff is going on there and you're not tied to the browser. If you want, I can give you the instructions.

[Wecoboss]

Thanks for your very quick reply.

Indeed, the upgrade was really happening in the background because after the timeout there were changes in the database. However, changing the execution time to 1800 didn't solve the issue.

I found a way to finally do the update: I had to disable the dav services on all the connected devices. They were syncing during the update and were creating endless loop of redirection to /admin/install/admin/install/... I don't know if it is my specific network configuration that is the cause of this loop (I am using a nginx reverse proxy before the apache server) but it solved the issue.

I had another issue related to the update: after successfully update the database, I clicked on the button to access the admin section but it triggered another update that ended up with the known "duplicate synctoken" issue. So I had to restore my backup, do the first update, restart apache and connect to the normal baikal url after deleting all cookies, cache, to get a login prompt ... and it finally worked...

I think it could be a good thing to release the command-line upgrade commands if possible because it would have been easier for me to stop the public network interface on my server and update from cli instead of disconnecting every devices.

Thanks again for all your work.

[evert]

This is a good idea, and worth considering for a future version. We're doing a lot of re-writing so this could maybe be done then as well.