Update 5.0.19 to 6 > RuntimeDB could not be loaded

Moderator: crythias

Post Reply
kwpr
OTRS newbie
Posts: 4
Joined: 21 Mar 2018, 15:30
OTRS Version?: 5.0.19

Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by kwpr » 27 Mar 2018, 11:37

Hi,

I already spend quite some time trying to update from 5.0.19 to version 6.
Now, I got to the point where I get a "Migration completed!" but the otrs page does not load because of "Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB could not be loaded"

Full error:

Code: Select all

Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB could not be loaded:
Can't locate Kernel/System/Ticket/ArticleSearchIndex/RuntimeDB.pm in @INC (you may need to install the Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB module) (@INC contains: /usr/Custom /usr/Kernel/cpan-lib /usr /usr/sbin/../../Custom /usr/sbin/../../Kernel/cpan-lib /usr/sbin/../.. /opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /etc/apache2)
at /opt/otrs/Kernel/System/ObjectManager.pm line 254.\n
at /opt/otrs/Kernel/System/ObjectManager.pm line 636.\n\t
Kernel::System::ObjectManager::_DieWithError(Kernel::System::ObjectManager=HASH(0x5558f62f0cb8), "Error", "Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB could n"...) called at /opt/otrs/Kernel/System/ObjectManager.pm line 261\n\t
Kernel::System::ObjectManager::_ObjectBuild(Kernel::System::ObjectManager=HASH(0x5558f62f0cb8), "Package", "Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB") called at /opt/otrs/Kernel/System/ObjectManager.pm line 200\n\t
Kernel::System::ObjectManager::Get(Kernel::System::ObjectManager=HASH(0x5558f62f0cb8), "Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB") called at /opt/otrs/Kernel/System/Ticket/Article.pm line 982\n\t
Kernel::System::Ticket::Article::ArticleSearchIndexSQLJoinNeeded(Kernel::System::Ticket::Article=HASH(0x5558f910b520), "SearchParams", HASH(0x5558f8cde8b8)) called at /opt/otrs/Kernel/System/Ticket/TicketSearch.pm line 491\n\t
Kernel::System::Ticket::TicketSearch::TicketSearch(Kernel::System::Ticket=HASH(0x5558f86d1a78), "Result", "ARRAY", "Permission", "rw", "UserID", 1, "OrderBy", ...) called at /opt/otrs/Kernel/Output/HTML/Dashboard/TicketGeneric.pm line 735\n\t
Kernel::Output::HTML::Dashboard::TicketGeneric::Run(Kernel::Output::HTML::Dashboard::TicketGeneric=HASH(0x5558f866c280), "AJAX", undef, "CustomerID", "", "CustomerUserID", "") called at /opt/otrs/Kernel/Modules/AgentDashboardCommon.pm line 983\n\t
Kernel::Modules::AgentDashboardCommon::_Element(Kernel::Modules::AgentDashboard=HASH(0x5558f749fb68), "Name", "0100-TicketPendingReminder", "Configs", HASH(0x5558f70ed8f8), "Backends", HASH(0x5558f74361a8)) called at /opt/otrs/Kernel/Modules/AgentDashboardCommon.pm line 610\n\t
Kernel::Modules::AgentDashboardCommon::Run(Kernel::Modules::AgentDashboard=HASH(0x5558f749fb68)) called at /opt/otrs/Kernel/System/Web/InterfaceAgent.pm line 1102\n\t
Kernel::System::Web::InterfaceAgent::Run(Kernel::System::Web::InterfaceAgent=HASH(0x5558f6d1cd18)) called at /opt/otrs/bin/cgi-bin/index.pl line 40\n\t
ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler(Apache2::RequestRec=SCALAR(0x5558f3ca6e58)) called at /usr/lib/x86_64-linux-gnu/perl5/5.24/ModPerl/RegistryCooker.pm line 207\n\t
eval {...} called at /usr/lib/x86_64-linux-gnu/perl5/5.24/ModPerl/RegistryCooker.pm line 207\n\t
ModPerl::RegistryCooker::run(ModPerl::Registry=HASH(0x5558f59fda00)) called at /usr/lib/x86_64-linux-gnu/perl5/5.24/ModPerl/RegistryCooker.pm line 173\n\t
ModPerl::RegistryCooker::default_handler(ModPerl::Registry=HASH(0x5558f59fda00)) called at /usr/lib/x86_64-linux-gnu/perl5/5.24/ModPerl/Registry.pm line 32\n\t
ModPerl::Registry::handler("ModPerl::Registry", Apache2::RequestRec=SCALAR(0x5558f3ca6e58)) called at -e line 0\n\t
eval {...} called at -e line 0\n
Migration showed some "Inconsistent SysConfig settings detected, please update them manually" so I updated Ticket::SearchIndexModule

Code: Select all

sudo -u otrs bin/otrs.Console.pl Admin::Config::Read --setting-name Ticket::SearchIndexModule
> Kernel::System::Ticket::ArticleSearchIndex::RuntimeDB
sudo -u otrs bin/otrs.Console.pl Admin::Config::Update --setting-name Ticket::SearchIndexModule --value "Kernel::System::Ticket::ArticleSearchIndex::DB"
I tired some cleanup but the error is still the same:

Code: Select all

sudo -u otrs bin/otrs.Console.pl Maint::Ticket::FulltextIndex --rebuild
sudo -u otrs bin/otrs.Console.pl Maint::Ticket::QueueIndexRebuild
sudo -u otrs bin/otrs.Console.pl Maint::Ticket::EscalationIndexRebuild
sudo -u otrs bin/otrs.Console.pl Maint::Cache::Delete
I read somewhere I have to uninstall all plugins but I only have original FAQ and Survey installed and don't want to loose any data.

Any idea what I could do next?

reneeb
OTRS guru
Posts: 4706
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by reneeb » 27 Mar 2018, 16:12

Open the sysconfig and search for "Ticket::SearchIndexModule". Edit the option and set a valid value...
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

kwpr
OTRS newbie
Posts: 4
Joined: 21 Mar 2018, 15:30
OTRS Version?: 5.0.19

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by kwpr » 27 Mar 2018, 17:34

Thanks for the answer.

In the 5.x version Ticket::SearchIndexModule is set to "RuntimeDB". Looks all right to me.

In version 6 I can't access the sysconfig page to search and change. That's why I updated the value from command line:

Code: Select all

sudo -u otrs bin/otrs.Console.pl Admin::Config::Update --setting-name Ticket::SearchIndexModule --value "Kernel::System::Ticket::ArticleSearchIndex::DB"
That did work but does change nothing. Same error.

I thought that might be a cache issue but I could not fix it.

reneeb
OTRS guru
Posts: 4706
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by reneeb » 27 Mar 2018, 19:35

Did you run "perl bin/otrs.Console.pl Maint::Config::Rebuild" after changing the setting?
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

kwpr
OTRS newbie
Posts: 4
Joined: 21 Mar 2018, 15:30
OTRS Version?: 5.0.19

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by kwpr » 28 Mar 2018, 09:34

In my bash history I see:

Code: Select all

sudo -u otrs bin/otrs.Console.pl Maint::Ticket::FulltextIndex --rebuild
sudo -u otrs bin/otrs.Console.pl Maint::Ticket::QueueIndexRebuild
sudo -u otrs bin/otrs.Console.pl Maint::Ticket::EscalationIndexRebuild
sudo -u otrs bin/otrs.Console.pl Maint::Cache::Delete
sudo -u otrs bin/otrs.Console.pl Maint::Config::Rebuild
But I check that again to make sure. I fixed some issues along the way maybe it does work now.

What I did to get here:

* set db and tables to utf8
* switch storage to File System: sudo -u otrs bin/otrs.Console.pl Admin::Article::StorageSwitch --target ArticleStorageFS
* set timezone in Kernel/Config.pm: $Self->{OTRSTimeZone} = 'Europe/Berlin';
* Update FAQ und Survey packages bevor(!) and after the migration

Code: Select all

sudo -u otrs scripts/DBUpdate-to-6.pl
tells my at the moment only this at the end:

Inconsistent SysConfig settings detected, please update them manually:

Ticket::Type::Default
Ticket::SearchIndexModule
Ticket::StorageModule

Ticket::Type::Default is set to "Others" and I have this ticket typ so I hope that is fine.
Ticket::SearchIndexModule I do change from "Kernel::System::Ticket::ArticleStorageDB" to "Kernel::System::Ticket::ArticleSearchIndex::DB"

A bit wired I get an error at the first time I change it:

Code: Select all

ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-10 Perl: 5.24.1 OS: linux Time: Tue Mar 27 17:50:44 2018

 Message: Setting Ticket::StorageModule Effective value is not correct: Kernel::System::Ticket::ArticleStorageDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleStorage*.pm)!

 Traceback (30344):
   Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3450
   Module: Kernel::System::Console::Command::Admin::Config::Update::Run Line: 170
   Module: (eval) Line: 460
   Module: Kernel::System::Console::BaseCommand::Execute Line: 454
   Module: Kernel::System::Console::InterfaceConsole::Run Line: 80
   Module: bin/otrs.Console.pl Line: 38

Error: Deployment failed!
It complains about the old value and does change the setting. If I run it again there is no more error.

Ticket::StorageModule is set to Kernel::System::Ticket::ArticleStorageFS. But I can't find Kernel/System/Ticket/ArticleStorageFS.pm in otrs 6. Not sure what the correct value should be.

kwpr
OTRS newbie
Posts: 4
Joined: 21 Mar 2018, 15:30
OTRS Version?: 5.0.19

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by kwpr » 10 Apr 2018, 11:55

Bump. Any idea what I could do next?

What are the correct values for Ticket::SearchIndexModule and Ticket::StorageModule (for FileSystem) in OTRS 6?

einhirn
OTRS newbie
Posts: 4
Joined: 28 Oct 2013, 11:03
OTRS Version?: 3.2.10

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by einhirn » 12 Jul 2018, 10:27

Hi,

Code: Select all

bin/otrs.Console.pl Admin::Config::Update --setting-name Ticket::SearchIndexModule --value "Kernel::System::Ticket::ArticleSearchIndex::DB"
is the only thing that is accepted: The XML File contains an Item

Code: Select all

ValueFilter="Kernel/System/Ticket/ArticleSearchIndex/*.pm"
which, when used with

Code: Select all

ls otrs/Kernel/System/Ticket/ArticleSearchIndex/*.pm
only shows "DB.pm"... Same for

Code: Select all

bin/otrs.Console.pl Admin::Config::Update --setting-name  Ticket::Article::Backend::MIMEBase::ArticleStorage --value "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageFS"
because of

Code: Select all

ValueFilter="Kernel/System/Ticket/Article/Backend/MIMEBase/ArticleStorage*.pm"

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 21 Jul 2018, 16:35

Running

Code: Select all

bin/otrs.Console.pl Admin::Config::Update --setting-name  Ticket::Article::Backend::MIMEBase::ArticleStorage --value "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB"
as OTRS-User, it shows the following error

Code: Select all

Updating setting value...

ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-21 Perl: 5.22.1 OS: linux Time: Sat Jul 21 16:33:28 2018

 Message: Setting Ticket::StorageModule Effective value is not correct: Kernel::System::Ticket::ArticleStorageDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleStorage*.pm)!

 Traceback (17622):
   Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3475
   Module: Kernel::System::Console::Command::Admin::Config::Update::Run Line: 170
   Module: (eval) Line: 460
   Module: Kernel::System::Console::BaseCommand::Execute Line: 454
   Module: Kernel::System::Console::InterfaceConsole::Run Line: 80
   Module: bin/otrs.Console.pl Line: 38

Error: Deployment failed!
Any ideas, why it's not possible? (looks like the ValueFilter isn't up-to-date, but why?)
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

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

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by jojo » 21 Jul 2018, 17:11

The Value is wrong
"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

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 22 Jul 2018, 20:08

jojo wrote:
21 Jul 2018, 17:11
The Value is wrong
What would be the correct value for OTRS6 and Article Storage in Database?
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

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

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by jojo » 22 Jul 2018, 20:33

Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB

Don't forget to deploy after setting
"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

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 22 Jul 2018, 22:39

jojo wrote:
22 Jul 2018, 20:33
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB

Don't forget to deploy after setting
This is exactly the value I tried to set.

The command was

Code: Select all

otrs@otrs:~$  bin/otrs.Console.pl Admin::Config::Update --setting-name  Ticket::Article::Backend::MIMEBase::ArticleStorage --value "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB"
and the error is

Code: Select all

ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-21 Perl: 5.22.1 OS: linux Time: Sun Jul 22 22:37:42 2018

 Message: Setting Ticket::StorageModule Effective value is not correct: Kernel::System::Ticket::ArticleStorageDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleStorage*.pm)!
Seems like the ValueFilter wants to get the old value? How can that be?
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

Tamerlain
OTRS newbie
Posts: 18
Joined: 13 Jul 2018, 15:15
OTRS Version?: 6.x.x.x

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Tamerlain » 24 Jul 2018, 15:33

Hi all,

i have exactly the same issue.
Used the old config of otrs5 (as adviced in upgrade manual) for making then the updates on it and gosh ...

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild" -s /bin/bash otrs
Rebuilding the system configuration...
ERROR: OTRS-otrs.Console.pl-Maint::Config::Rebuild-10 Perl: 5.20.1 OS: linux Time: Tue Jul 24 15:30:44 2018

Message: Setting Ticket::StorageModule Effective value is not correct: Kernel::System::Ticket::ArticleStorageDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleStorage*.pm)!

Traceback (8599):
Module: Kernel::System::SysConfig::ConfigurationDeploy Line: 3465
Module: Kernel::System::Console::Command::Maint::Config::Rebuild::Run Line: 69
Module: (eval) Line: 460
Module: Kernel::System::Console::BaseCommand::Execute Line: 454
Module: Kernel::System::Console::InterfaceConsole::Run Line: 80
Module: /opt/otrs/bin/otrs.Console.pl Line: 38

We did previously a complete fresh Installation of OTRS 6 and then dumped the old DB in it, copied the old configs, XMLs and so on and then runned all the adviced update steps.

Is there a way to coorect this directly in the database table? If yes in which one? Which table?
Viele Grüße,
T

reneeb
OTRS guru
Posts: 4706
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by reneeb » 30 Jul 2018, 11:28

Ticket::StorageModule must be set to a valid value like "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB"
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 30 Jul 2018, 11:32

Sascha79 wrote:
22 Jul 2018, 22:39
jojo wrote:
22 Jul 2018, 20:33
Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB

Don't forget to deploy after setting
This is exactly the value I tried to set.

The command was

Code: Select all

otrs@otrs:~$  bin/otrs.Console.pl Admin::Config::Update --setting-name  Ticket::Article::Backend::MIMEBase::ArticleStorage --value "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB"
and the error is

Code: Select all

ERROR: OTRS-otrs.Console.pl-Admin::Config::Update-21 Perl: 5.22.1 OS: linux Time: Sun Jul 22 22:37:42 2018

 Message: Setting Ticket::StorageModule Effective value is not correct: Kernel::System::Ticket::ArticleStorageDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleStorage*.pm)!
Seems like the ValueFilter wants to get the old value? How can that be?
Like already said, I tried to set "Kernel::System::Ticket::Article::Backend::MIMEBase::ArticleStorageDB" as value and it does not work.
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

reneeb
OTRS guru
Posts: 4706
Joined: 13 Mar 2011, 09:54
OTRS Version?: 3.3.x
Company: Perl-Services.de
Contact:

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by reneeb » 30 Jul 2018, 11:43

Did you check the Kernel/Config.pm?
Perl / OTRS development: http://perl-services.de
Free OTRS add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 31 Jul 2018, 12:30

reneeb wrote:
30 Jul 2018, 11:43
Did you check the Kernel/Config.pm?
Nothing about ArticleStorageDB in the Config.pm
I wonder, from where Admin::Config::Update takes it's validation-data.
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

Sascha79
OTRS newbie
Posts: 38
Joined: 23 Jul 2009, 09:21
OTRS Version?: 5.0.22 (GIT)
Real Name: Sascha

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by Sascha79 » 31 Jul 2018, 13:00

After looking a bit into the Console-Module Source, I found an "cleanup"-parameter for Maint::Config::Rebuild.

It really removed the problem and setting the Storage-Value now works!

Command is:

Code: Select all

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild --cleanup" -s /bin/bash otrs
I did not check (yet) what settings exactly have been removed - looking at the diff of ZZZAAuto.pm between before and after cleanup is a way?
"Production": OTRS5 (Ubuntu 16.04.4 Server (LTS) / Apache2 / MySQL 5+

zin
OTRS newbie
Posts: 15
Joined: 16 Sep 2016, 06:50
OTRS Version?: 5.0.x

Re: Update 5.0.19 to 6 > RuntimeDB could not be loaded

Post by zin » 31 Aug 2018, 06:23

Hi,

i also faced that error after upgrading 6.x.x :
"Setting Ticket::SearchIndexModule Effective value is not correct: Kernel::System::Ticket::ArticleSearchIndex::StaticDB doesn't satisfy ValueFilter(Kernel/System/Ticket/ArticleSearchIndex/*.pm)!"

Now i solved it with the following:
(i)you need default setting for SearchIndexModule, use the following command:
su -c "bin/otrs.Console.pl Admin::Config::Update --setting-name Ticket::SearchIndexModule --value Kernel::System::Ticket::ArticleSearchIndex::DB" -s /bin/bash otrs

(ii)don't forget to deploy
su -c "bin/otrs.Console.pl Maint::Ticket::FulltextIndex --rebuild" -s /bin/bash otrs

(iii)should delete cache
su -c "bin/otrs.Console.pl Maint::Cache::Delete" -s /bin/bash otrs
yours truly

Post Reply