Upgrading from 5.0.22 to 6.0.1 Trouble
Moderator: crythias
-
- Znuny newbie
- Posts: 1
- Joined: 13 Dec 2017, 00:18
- Znuny Version: 5.0.22
- Real Name: Scott Jones
- Company: Synergy Information Solutions
Upgrading from 5.0.22 to 6.0.1 Trouble
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!
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!
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
Hey,
Got that problem yesterday (along with a billion more..)
A workaround/fix :
config.pm
$Self->{OTRSTimeZone } = 'Europe/Berlin';
Got that problem yesterday (along with a billion more..)
A workaround/fix :
config.pm
$Self->{OTRSTimeZone } = 'Europe/Berlin';
-
- Znuny newbie
- Posts: 21
- Joined: 28 Jun 2018, 12:23
- Znuny Version: 5.0.22
- Real Name: Martins
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
The same there..... Is there some correct upgrade manual available? (OTRS5 to OTRS6 upgrade)
-
- Znuny newbie
- Posts: 21
- Joined: 28 Jun 2018, 12:23
- Znuny Version: 5.0.22
- Real Name: Martins
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
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.
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
the setting will be set by migration script
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 21
- Joined: 28 Jun 2018, 12:23
- Znuny Version: 5.0.22
- Real Name: Martins
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
Hi,
any workaround or solution?
Thanks,
Jens
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
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
-
- Znuny newbie
- Posts: 21
- Joined: 28 Jun 2018, 12:23
- Znuny Version: 5.0.22
- Real Name: Martins
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
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?
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?
-
- Znuny newbie
- Posts: 10
- Joined: 07 Apr 2020, 17:37
- Znuny Version: 6.0.28
- Real Name: Jason Roske
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
Hi. I'm having this same issue going from 5.041 to 6.0.27
I've tried both the solutions of adding the
$Self->{OTRSTimeZone } = 'America/Regina'; to config.pm
and running migration with an empty XML directory... still fails with virtually the same error.
And yes I do have perl-DateTime installed.
DBUpdate-to-6.pl: Use of uninitialized value $DefaultSetting{"Name"} in concatenation (.) or string at /opt/otrs/Kernel/System/SysConfig/DB.pm line 1700.
ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-51 Perl: 5.16.3 OS: linux Time: Wed Apr 8 18:10:28 2020
Message: Setting OTRSTimeZone does not exists!
Traceback (76467):
Module: Kernel::System::SysConfig::SettingUpdate Line: 454
Module: scripts::DBUpdateTo6::Base::SettingUpdate Line: 664
Module: scripts::DBUpdateTo6::MigrateTimeZoneConfiguration::Run Line: 160
Module: scripts::DBUpdateTo6::_ExecuteComponent Line: 157
Module: scripts::DBUpdateTo6::Run Line: 69
Module: scripts/DBUpdate-to-6.pl Line: 87
Not possible to complete migration, check previous messages for more information.
Ideas?
I've tried both the solutions of adding the
$Self->{OTRSTimeZone } = 'America/Regina'; to config.pm
and running migration with an empty XML directory... still fails with virtually the same error.
And yes I do have perl-DateTime installed.
DBUpdate-to-6.pl: Use of uninitialized value $DefaultSetting{"Name"} in concatenation (.) or string at /opt/otrs/Kernel/System/SysConfig/DB.pm line 1700.
ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-51 Perl: 5.16.3 OS: linux Time: Wed Apr 8 18:10:28 2020
Message: Setting OTRSTimeZone does not exists!
Traceback (76467):
Module: Kernel::System::SysConfig::SettingUpdate Line: 454
Module: scripts::DBUpdateTo6::Base::SettingUpdate Line: 664
Module: scripts::DBUpdateTo6::MigrateTimeZoneConfiguration::Run Line: 160
Module: scripts::DBUpdateTo6::_ExecuteComponent Line: 157
Module: scripts::DBUpdateTo6::Run Line: 69
Module: scripts/DBUpdate-to-6.pl Line: 87
Not possible to complete migration, check previous messages for more information.
Ideas?
-
- Znuny newbie
- Posts: 10
- Joined: 07 Apr 2020, 17:37
- Znuny Version: 6.0.28
- Real Name: Jason Roske
Re: Upgrading from 5.0.22 to 6.0.1 Trouble
An update.... I downgraded the RMP to version 6.0.25 and I've gotten past that point.
Some history.... I updated our DEV system do 6.0.25 previously but before we applied to the live 6.0.27 came out so we were starting over with 27 and ran into that issue. Going back to 25 there is no upgrade issue at that point so we will upgrade to 25 then apply the patch to 27.
Thanks anyway to all who help on this site.
Some history.... I updated our DEV system do 6.0.25 previously but before we applied to the live 6.0.27 came out so we were starting over with 27 and ran into that issue. Going back to 25 there is no upgrade issue at that point so we will upgrade to 25 then apply the patch to 27.
Thanks anyway to all who help on this site.