Upgrading from 5.0.22 to 6.0.1 Trouble

Moderator: crythias

Post Reply
thenodemaster
OTRS newbie
Posts: 1
Joined: 13 Dec 2017, 00:18
OTRS Version?: 5.0.22
Real Name: Scott Jones
Company: Synergy Information Solutions

Upgrading from 5.0.22 to 6.0.1 Trouble

Post by thenodemaster » 13 Dec 2017, 00:36

Running OTRS 5.0.22 FREE on Ubuntu server 16.04 and have had great success with it, however, when trying to update to 6.0.1 or 6.0.2, I am running into issues. I have been following the Updating OTRS pager found here: http://doc.otrs.com/doc/manual/admin/st ... ating.html

Where I am running into trouble is when running the DBUpdate-to-6.pl script as instructed in the how to, I get the following error:

[Tue Dec 12 14:22:53 2017] DBUpdate-to-6.pl: Use of uninitialized value $DefaultSetting{"Name"} in concatenation (.) or string at /opt/otrs/Kernel/System/SysConfig/DB.pm line 1370.
ERROR: OTRS-otrs.Console.pl-Maint::Database::Check-10 Perl: 5.22.1 OS: linux Time: Tue Dec 12 14:22:53 2017

Message: Setting OTRSTimeZone does not exists!

Traceback (5091):
Module: Kernel::System::SysConfig::SettingUpdate Line: 460
Module: scripts::DBUpdateTo6::MigrateTimeZoneConfiguration::Run Line: 164
Module: scripts::DBUpdateTo6::_ExecuteComponent Line: 157
Module: scripts::DBUpdateTo6::Run Line: 69
Module: scripts/DBUpdate-to-6.pl Line: 89

Not possible to complete migration, check previous messages for more information.

I did have to install libdatetime-perl before beginning the update and I did successfully perform a full backup of the OTRS system and database before beginning the process. and made sure that the permissions script was run and the config files were brought over as well as the XML files relocated and migrated.

I tried looking for the error on Google but did not find much. This error occurs shortly after the system asks for the timezone for the OTRSTimeZone, UserDefaultTimeZone as well as the same for the 9 calendars (I assuming these are really the individual users). All are set to America/Los_Angeles and accepted by the system.

The specific step it hangs on is 15 of 37: Migrating time zone configuration.

Kind of at a stand still. I am working with a relocated copy of the production VM so I can experiment without taking anything down in VMWare Workstation. Original location was VSphere. The only thing I changed on the experimental VM was the IP address and the hostname so as not to conflict with the live VM. The test VM is on a separate subnet from the production VM.

Any assistance would be appreciated. Please let me know if I can provide more information for this.

Thanks!

Naga
OTRS newbie
Posts: 1
Joined: 18 Jan 2018, 16:54
OTRS Version?: 5.0.20

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by Naga » 19 Jan 2018, 11:24

Hey,

Got that problem yesterday (along with a billion more..)
A workaround/fix :
config.pm
$Self->{OTRSTimeZone } = 'Europe/Berlin';

LXsysadmin
OTRS newbie
Posts: 18
Joined: 28 Jun 2018, 12:23
OTRS Version?: 5.0.22
Real Name: Martins

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by LXsysadmin » 06 Jul 2018, 15:49

The same there..... Is there some correct upgrade manual available? (OTRS5 to OTRS6 upgrade)

LXsysadmin
OTRS newbie
Posts: 18
Joined: 28 Jun 2018, 12:23
OTRS Version?: 5.0.22
Real Name: Martins

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by LXsysadmin » 06 Jul 2018, 16:05

Naga wrote:
19 Jan 2018, 11:24
Hey,

Got that problem yesterday (along with a billion more..)
A workaround/fix :
config.pm
$Self->{OTRSTimeZone } = 'Europe/Berlin';
Does this must be done before the first time run of scripts/DBUpdate-to-6.pl script?
I have entered $Self->{OTRSTimeZone } = 'Europe/Berlin'; but get the same error.

jojo
Moderator
Posts: 14363
Joined: 26 Jan 2007, 14:50
OTRS Version?: Git Master
Contact:

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by jojo » 06 Jul 2018, 16:40

the setting will be set by migration script
"Production": OTRS™ 6, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) git Master

Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com :: Share your ideas

LXsysadmin
OTRS newbie
Posts: 18
Joined: 28 Jun 2018, 12:23
OTRS Version?: 5.0.22
Real Name: Martins

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by LXsysadmin » 10 Jul 2018, 09:02

jojo wrote:
06 Jul 2018, 16:40
the setting will be set by migration script
Looks like not, because i get the same error as mentioned using this migration script. What would be the workaround?

eicki
OTRS newbie
Posts: 13
Joined: 01 Dec 2010, 12:55
OTRS Version?: 5.0.29

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by eicki » 13 Sep 2018, 13:07

Hi,

any workaround or solution?

Thanks,
Jens
Prod:
OTRS: 5.0.29
OS: CentOS 7 (Virtuozzo Container), Apache 2.4.6, Perl 5.16.3
DB: MySQL 5.6.39

Dev:
OTRS: 6.0.10
OS: CentOS 7 (Virtuozzo Container), Apache 2.4.6, Perl 5.16.3
DB: MySQL 5.7.21

LXsysadmin
OTRS newbie
Posts: 18
Joined: 28 Jun 2018, 12:23
OTRS Version?: 5.0.22
Real Name: Martins

Re: Upgrading from 5.0.22 to 6.0.1 Trouble

Post by LXsysadmin » 14 Sep 2018, 11:58

I am doing right now new one test, but looks that if i don't do XML migration (su -c "/opt/otrs/bin/otrs.Console.pl Dev::Tools::Migrate::ConfigXMLStructure --source-directory Kernel/Config/Files" -s /bin/bash otrs) then i don't get this error about "Setting OTRSTimeZone does not exists!".
As i don't have any specific XML configuration files or changes in OTRS 5 (just default), looks like this XML migration can be skipped.

The question is, is it safe to do migration without XML migration from OTRS 5 version?

Post Reply