Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
0013508: Update from 2017.02.05 to 2017.08.06 #6682
Reported by bernhard on 1 Oct 2017 20:03
Version: 2017.08.6 Community Edition
CentOS 7; php 5.6, postgresql; Update of tinebase:
SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "tine20_config_customfields" does not exist, query was: ALTER TABLE "tine20_config_customfields" RENAME TO "tine20_customfield_config"
Additional information: Fehler tritt nur unter PostgreSQL auf; nicht unter MariaDB oder MySQL
Comment posted by pmehrer on 2 Oct 2017 09:19
it seems your tine20_application table got corrupted. The "version" column of your installed applications should be around 10.xx
Please restore the correct application versions from a backup and the update will work. It is a got idea not to alter that data.
Comment posted by bernhard on 2 Oct 2017 12:03
I am sorry, but the version numbers in the table tine20_applications seem to be correct:
tine20=# select * from tine20_applications;
Comment posted by bernhard on 3 Oct 2017 15:12
is there any solution for this installation bug? The suggested solution does not work, because the version numbers in the database are correct as you can see above. Every time a user logon, he gets the hint to update tine20. But the update does not work!
Comment posted by lukasz on 4 Oct 2017 07:52
I am not sure if it is related but while trying to update tinebase and other apps from 2017.02.05 to 2017.08.6 I receive:
2da43 setupuser - 2017-10-04T07:40:55+00:00 ERR (3): Setup_Controller::updateApplication::582 SQLSTATE[HY000]: General error: 1025 Error on rename of './noboCrmdb/#sql-1d2b_11d' to './noboCrmdb/noboCrm_container' (errno: 150), query was: ALTER TABLE
After login in as a regular user in About Tine20 version 2017.08.6 is reported.
Comment posted by lukasz on 4 Oct 2017 08:19
After trying to upgrade there is another issue. Application version of tinebase has been changed to 2 (!)
mysql> select * from noboCrm_applications;
Comment posted by pmehrer on 10 Oct 2017 13:35
thank you for reporting this issue. I was able to reproduce the set back of Tinebase to Version 2 (it happens only if there occurs another error and you repeat the update process and it fails again a 2nd time) This is fixed and merged. But it will not help you, as your issue is the failing update.
As mentioned in other tickets we are not able to reproduce this. Most likely you have a concurrent process altering your data while the update runs and that is why it fails (or you have a corrupted database from the start, like a missing foreign key constraint)