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

0.7.1 upgrade fails #961

Closed
3 tasks done
0-wiz-0 opened this issue Jul 28, 2020 · 5 comments
Closed
3 tasks done

0.7.1 upgrade fails #961

0-wiz-0 opened this issue Jul 28, 2020 · 5 comments

Comments

@0-wiz-0
Copy link

0-wiz-0 commented Jul 28, 2020

Baikal version: 0.6.1 to 0.7.1 upgrade

  • I have searched open and closed issues for duplicates (Error updating from 0.5.0 to 0.7 #942 looks similar but I'm using sqlite)
  • I have installed the release zip, not the source code zip
  • I have moved the whole, untouched Specific and config folders to the new installation (there was no config in 0.6.1)
    Problem:
    The upgrade starts fine and arrives at:
Upgrading Baïkal from version 0.6.1 to version 0.7.1

Please create a backup before upgrading.

Upgrading might take a few minutes depending on the number of events and contacts. Do not interrupt the upgrade!

but when I press the Start Upgrade button, I get:

Error: Call to a member function getPDO() on null in /usr/pkg/share/baikal/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php:98
Stack trace:
#0 /usr/pkg/share/baikal/Core/Frameworks/BaikalAdmin/Controller/Install/VersionUpgrade.php(68): BaikalAdmin\Controller\Install\VersionUpgrade->upgrade('0.6.1', '0.7.1')
#1 /usr/pkg/share/baikal/Core/Frameworks/Flake/Core/Render/Container.php(69): BaikalAdmin\Controller\Install\VersionUpgrade->render()
#2 /usr/pkg/share/baikal/Core/Frameworks/Flake/Controller/Page.php(90): Flake\Core\Render\Container->renderBlocks()
#3 /usr/pkg/share/baikal/html/admin/install/index.php(100): Flake\Controller\Page->render()
#4 {main}

Fix:
The problem was that I used a non-default database path (/home/baikal/something.db instead of /usr/pkg/share/baikal/db/...).
The path I used was correctly displayed in the web interface, but in the new yaml file on disk, the default path was written instead.
Was I supposed to edit the yaml file myself? I had understood that the web interface would do it automatically for me.
Once I fixed the db path in the yaml file, the upgrade finished successfully.

@fbett
Copy link

fbett commented Jul 30, 2020

Looks like the problem in #946

@0-wiz-0
Copy link
Author

0-wiz-0 commented Jul 30, 2020

True, but in my setup I use sqlite3 as backend, while #946 has a mysql backend.
I didn't try going via 0.7.0.

@typoman76
Copy link

Had the same issues. Updating from 0.6.1 to 0.7.1.
The installer showed everything correctly but didn't write it to the yaml file. I hat to enter it manually and set mysql to true. After that, the upgrade worked!

@allofmex
Copy link

I hat to enter it manually

Same for me, installer showed "use mysql true" (not showing sql detailed settings as far as I remember), but upgrade failed.
After editing yaml manually, it upgraded.

(0.6.1 -> 0.7.1, mysql db)

@ByteHamster
Copy link
Member

Should be fixed in #979

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

5 participants