Upgrade 1.8 to 14 (16/17)

mstyslav 2019-03-04 13:15:47 UTC #1

Hello
we have ver. EGW 1.8, was installed 5 years ago
employs approximately 2,000 people, mail, contacts
it’s time to upgrade. Of course, I wanted to reinstall the system, install version 16 or 17, and transfer the data. but so probably not. let’s start with version 14 (community edition)
I read many different instructions and topics on this and other forums. but did not get an exact answer.
Please, if possible, give me instructions or a link to it.
I have CentOS 6, php 5.3.3
I know that a compatibility package is needed, but for version 1.8 or 14 I did not find it.
I will be grateful for your help!

Mstyslav

RalfBecker 2019-03-04 14:22:36 UTC #2

Hi Msyslav,

we no longer publish 14.3 packages, as they are outdated.

For an update, please use latest 17.1 packages, which require PHP 5.6 minimum. The next version will require PHP 7.1 minimum, so I would recommend to install the new machine with PHP 7.2 or 7.3 on a current Ubuntu 18.04, Debian 9 or CentOS 7.

For the update:

make a clean new installation according the instruction on https://wiki.egroupware.org/
for the 1.8 update install the egroupware-epl-compat package
if you use Wiki, SiteMgr, KnowledgeBase, you also need to install them, as they are no longer installed by default
make database backup inside EGroupware Admin or Setup
rsync your old data-directory (default /var/lib/egroupware/default/) to the new server (includes the backup)
fix the ownership, in case you changed the distribution eg. CentOS to Ubuntu
log into Setup (credentials are in /root/egroupware-epl-install.log) to run the restore and then the update

Ralf

RalfBecker 2019-03-04 14:23:52 UTC #3

We also offer to do the migration for your:

That included not only the upgrade, but also an introduction to the new version.

Ralf

mstyslav 2019-03-04 14:53:55 UTC #4

Thanks for the response!
I already have a clean installation of 17.1:

Ubuntu 18 + php 7.2 + installed egroupware-epl-compat (17.1.20190222)
installed egw 17 through “git clone -c 17.1” (README.md)
I do not quite understand which version of egroupware-epl-compat is set to 1.8?
if I understand you correctly, backup and restore need to be done exactly from http://my_groupware/setup/db_backup.php?

wbr
Mstyslav

RalfBecker 2019-03-04 15:14:50 UTC #5

All I said was: to update from 1.8, you need to have egroupware-epl-compat installed, as it contains the old update-scripts from 1.8 to 14.3.

Our db_backup.php takes care of a lot of little things, you otherwise have to know and take care of.
With enough knowledge and extra steps, everything can also be done eg. with mysqldump.

Ralf

mstyslav 2019-03-04 15:29:26 UTC #6

I do not understand whether it is necessary to install a epl-compat package on a server with 1.8, and if so, which version?
I tried to do a restore from backup through the installation, but in the end I got a non-working system
I apologize for asking possibly stupid questions, but I do not understand everything. and I want to understand
tnx

RalfBecker 2019-03-04 16:34:50 UTC #7

On the 1.8 you only do the backup, rsync it with the files to the new system, which must have the egroupware-epl-compat package installed, to be able to update from 1.8 (without it can only update from latest 14.3!).

Ralf

mstyslav 2019-03-05 07:55:21 UTC #8

thank!
I’ll check it out, do as you say.
Tell me, is the content synchronization /var/lib/egroupware/default/ is required for successful import from 1.8? or is it critical only for users and their files?

RalfBecker 2019-03-05 08:11:36 UTC #9

This depends on the content of your database. If you have photos in your addressbooks, they will be moved from the database to the filesystem. If you later overwrite them, eg. by completely replacing the files dir, they will be lost.

For a first test migration you can ignore the files, if you copy the db_backup-file manually.

Ralf

mstyslav 2019-03-05 09:14:06 UTC #10

after recovering from backup, got this (screen)

If I am right, then you need to do an “upgrade”?

RalfBecker 2019-03-05 09:34:30 UTC #11

Yes, restore does not automatic update

Ralf

mstyslav 2019-03-05 09:45:11 UTC #12

ok!
after the update i get:

====
Invalid SQL: SELECT config_name,config_value FROM config WHERE config_name LIKE ‘ads%’ OR config_name LIKE ‘ldap%’ OR config_name LIKE 'account%’ OR config_name LIKE ‘%encryption%’ OR config_name=‘auth_type’_
Unknown column ‘config_name’ in ‘field list’ (1054)
====

in the table the “config” really does not have such fields, more precisely there are fields "name and "volue"
if I rename from, then further (after the repetition of the update) I get even more SQL errors

I can provide a screen
I have already done all this before, but did not get any result ((

RalfBecker 2019-03-05 10:07:58 UTC #13

We don’t have a table called “config”, only “egw_config”.

That is true for 1.8 and current version.

Ralf

mstyslav 2019-03-05 10:42:04 UTC #14

Yes, I know that all your tables start with "egw_"
the question is why the updater climbs into the table “config”?
can not be ignored, the update does not go further

RalfBecker 2019-03-05 12:10:21 UTC #15

I can not answer, without further analysis, why your updates fails.

Next step would be, restore the database update once again.
And the next time instead of just clicking on update, check the box for further diagnostics output and provide that, incl. Apache error.log and maybe general query log of database.

Please provide here only the logs before and after the error, not the full logs!

Anyway I can only help so much, at some point you might need to consider buying an update package from us.

Ralf

mstyslav 2019-03-05 12:24:11 UTC #16

I removed the extra (“alien”) tables
now with the “update” I get a report on duplicates

_AlterColumnSQL(‘egw_ea_accounts’,‘acc_folder_archive’,Array ( [type] => varchar [precision] => 128 [comment] => archive folder ) ) sql=Array ( [0] => ALTER TABLE egw_ea_accounts ADD acc_folder_archive VARCHAR(128) ) _
Duplicate column name ‘acc_folder_archive’

_AlterColumnSQL(‘egw_ea_accounts’,‘acc_folder_ham’,Array ( [type] => varchar [precision] => 128 [comment] => ham folder ) ) sql=Array ( [0] => ALTER TABLE egw_ea_accounts ADD acc_folder_ham VARCHAR(128) ) _
Duplicate column name ‘acc_folder_ham’

_AlterColumnSQL(‘egw_ea_accounts’,‘acc_spam_api’,Array ( [type] => varchar [precision] => 128 [comment] => SpamTitan API URL ) ) sql=Array ( [0] => ALTER TABLE egw_ea_accounts ADD acc_spam_api VARCHAR(128) ) _
Duplicate column name ‘acc_spam_api’

_AlterColumnSQL(‘egw_addressbook’,‘contact_files’,Array ( [type] => int [precision] => 1 [default] => 0 [comment] => &1: photo, &2: pgp, &4: smime ) ) sql=Array ( [0] => ALTER TABLE egw_addressbook ADD contact_files TINYINT DEFAULT 0 ) _
Duplicate column name ‘contact_files’

_AlterColumnSQL(‘egw_history_log’,‘share_email’,Array ( [type] => varchar [precision] => 4096 [default] => [nullable] => 1 [comment] => email addresses of share who made the change, comma seperated ) ) sql=Array ( [0] => ALTER TABLE egw_history_log ADD share_email VARCHAR(4096) ) _
Duplicate column name ‘share_email’

Invalid SQL: UPDATE egw_preferences SET preference_value=’{“notifyAdded”:"\u00c3\u0192\u00c6\u2019\u00c3\u2020\u00e2\u20ac\u2122\u00c3\u0192\u00e2\u20ac\u0161\u00c3\u201a\u00c2\u0090\u00c3\u0192\u00c6\u2019\u00c3\u00a2\u00e2\u201a\u00ac\u00c5\u00a1\u00c3\u0192\u00e2\u20ac\u0161\u00c3\u201a\u00c2\u00a1\u00c3\u0192\u00c6\u2019\u00c3\u2020\uu201a\u00c2\u0090\u00c3\u0192\u00c6\u2019\u00c3\u00a2\u00e2\u201a\u00ac\u00c5\u00a1\u00c3\u0192\u00e2\u20ac\u0161\u00c3\u201a\u00c2\u00ba\\\\\\\\\""}’ WHERE preference_owner=-1 AND preference_app='calendar’
Data too long for column ‘preference_value’ at row 1 (1406)

there are no duplicates, I rechecked

mstyslav 2019-03-05 12:37:44 UTC #17

I think I managed to do it …
I’ll check and write the result

mstyslav 2019-03-06 14:10:30 UTC #18

I want to inform you that the problem was due to the tables created by postfixadmin
I deleted them and then everything went well
Today I created another clean installation and decided to check the transfer process again. did everything according to the manual
However, after recovering from backup, I received an error

Invalid SQL: SELECT contact_id,contact_jpegphoto,contact_pubkey
FROM egw_addressbook
WHERE contact_jpegphoto != ‘’ OR contact_pubkey IS NOT NULL AND contact_pubkey LIKE '%-----%'
Unknown column ‘contact_jpegphoto’ in ‘field list’ (1054)

the field that did not find the “update” (contact_jpegphoto) is present in the table
I deleted and created it again, with no result. if the delete field is the same error
I ask for help!

Mstyslav

mstyslav 2019-03-07 07:22:06 UTC #19

rolled back to a clean install, made backup and restore again. has passed
but!
After logging in, I see an empty screen, only the menu on top
where to look?
thank!

mstyslav 2019-03-07 07:25:35 UTC #20

I specifically describe all my problems, maybe it will be useful for someone and will help to solve problems that arise.