OTRS 3.1 Beta

[kruegerM]

Running a test update of 3.1 (update from 3.0.6).
The scripts/DBUpdate-to-3.1.pl has been running for 3 hours now... It updated 21360 tickets succesfully - gave a message about 'Migrated 0 articles of 0 (with Free fields data)' - and since then nothing.
How long should I expect this script to run (approximately)?

Thanx.

Mark

[jojo]

I don't know any figures yet...

but it is beta, so the script still could have a bug

[kruegerM]

I let the program run - it took almost 7 hours before it finished, but it showed mysql connection errors (time out?). Below are the results given after the 7-hour processing:

------------------------------------------------
Step 7 of 22: Verify if ticket data was successfully migrated... done.

DBD::mysql::db do failed: MySQL server has gone away at /opt/otrs/Kernel/System/DB.pm line 438.
ERROR: OTRS-DBUpdate-to-3.1-10 Perl: 5.10.0 OS: linux Time: Wed Nov 30 20:22:42 2011

Message: MySQL server has gone away, SQL: 'SELECT freekey1, freetext1, freetime1 FROM ticket'

Traceback (1423):
Module: main::_IsFreefieldsMigrationAlreadyDone (v1.62) Line: 394
Module: scripts/DBUpdate-to-3.1.pl (v1.62) Line: 125

DBD::mysql::db do failed: MySQL server has gone away at /opt/otrs/Kernel/System/DB.pm line 438.
ERROR: OTRS-DBUpdate-to-3.1-10 Perl: 5.10.0 OS: linux Time: Wed Nov 30 20:22:42 2011

Message: MySQL server has gone away, SQL: 'SELECT a_freekey1, a_freetext1 FROM article'

Traceback (1423):
Module: main::_IsFreefieldsMigrationAlreadyDone (v1.62) Line: 399
Module: scripts/DBUpdate-to-3.1.pl (v1.62) Line: 125

Step 8 of 22: Verify if article data was successfully migrated... Free fields were deleted, migration is already done!
done.

DBD::mysql::st execute failed: MySQL server has gone away at /opt/otrs/Kernel/System/DB.pm line 570.
ERROR: OTRS-DBUpdate-to-3.1-10 Perl: 5.10.0 OS: linux Time: Wed Nov 30 20:22:42 2011

Message: MySQL server has gone away, SQL: 'SELECT id, name, field_order FROM dynamic_field ORDER BY field_order, id'

Traceback (1423):
Module: Kernel::System::DynamicField::DynamicFieldList (v1.48) Line: 689
Module: main::_MigrateFreeFieldsConfiguration (v1.62) Line: 1030
Module: scripts/DBUpdate-to-3.1.pl (v1.62) Line: 139

Can't use an undefined value as a HASH reference at scripts/DBUpdate-to-3.1.pl line 1035.
Step 9 of 22: Migrate free fields configuration...
------------------------------------------------

[jojo]

this should not happen. Have a look at your database settings if they are the same like on the old machine

[kruegerM]

I've been running a copy of our production database on this machine for about 3 months now. I do have a snapshot of the machiine - I can rebuild it to where it was, recheck the production copy, then try the migration again.

[kruegerM]

Still getting same results. I was using the "fixed" DBUpdate-to-3.1.pl, so I backed everything up, and ran the migration with the original script. With this step 6 runs, but I get the following before step 7 :

A field was not correctly migrated: 8 Ticket 300
Found DynamicField value '', expected ''!

After step 8 I get the following error:

Ticket or article data was not successfully migrated!
DO NOT CONTINUE THE UPGRADING PROCESS UNTIL THIS ISSUE IS FIXED, OTHERWISE YOU MAY LOSE DATA!
Died at scripts/DBUpdate-to-3.1.pl line 134.

So now I'm at a loss. Glad this is just beta.

[kruegerM]

Status update -
Now working with Beta 2 - and SUCCESSFULLY testng an upgrade of our production system in the development environment. Moving to Dynamic Fields is probably the long pole in the tent - but am able to advance now!!

[fnold]

Hi,
we get the same error trying to update from otrs 3.0.11 to 3.1Beta4

Step 7 of runs for approx 24hours and then DBUpdate-to-3.1.pl crashes when reaching step 8:

Code: Select all

   Verified ticket 85900 of 86019 (with Free fields data).
   Verified ticket 86000 of 86019 (with Free fields data).

 Verified 86019 tickets of 86019 (with Free fields data).
done.

DBD::mysql::db do failed: MySQL server has gone away at /opt/otrs-3.1.0.beta4/Kernel/System/DB.pm line 478.
ERROR: OTRS-DBUpdate-to-3.1-87 Perl: 5.8.8 OS: linux Time: Tue Jan 24 08:50:06 2012

 Message: MySQL server has gone away, SQL: 'SELECT freekey1, freetext1, freetime1 FROM ticket'

 Traceback (32240):
   Module: main::_IsFreefieldsMigrationAlreadyDone (v1.67) Line: 394
   Module: scripts/DBUpdate-to-3.1.pl (v1.67) Line: 125

DBD::mysql::db do failed: MySQL server has gone away at /opt/otrs-3.1.0.beta4/Kernel/System/DB.pm line 478.
ERROR: OTRS-DBUpdate-to-3.1-87 Perl: 5.8.8 OS: linux Time: Tue Jan 24 08:50:06 2012

 Message: MySQL server has gone away, SQL: 'SELECT a_freekey1, a_freetext1 FROM article'

 Traceback (32240):
   Module: main::_IsFreefieldsMigrationAlreadyDone (v1.67) Line: 399
   Module: scripts/DBUpdate-to-3.1.pl (v1.67) Line: 125

We test with a clone of the production environment which runs well for many months, so database setting should be ok (e.g max_allowed_packet = 16M).
I also checked that the DB is running after OTRS-DBUpdate-to-3.1 crashed.
Does it make sense to run the script again whithout step 7, so that step 8 follows on step 6?
Is there a chance to accelarate this part of the migration script? 24hours is quite a looong downtime
Regards
Florian