log error after upgrading from otrs 4 to 5.0.6

Moderator: crythias

Post Reply
mrv
OTRS newbie
Posts: 9
Joined: 01 Feb 2016, 13:21
OTRS Version?: 5.0.6

log error after upgrading from otrs 4 to 5.0.6

Post by mrv » 01 Feb 2016, 13:30

Hi everyone
i just completed the otrs 4 to 5.0.6 upgrade
no errors releaved during the process

Taking a look at system log, i saw:

Code: Select all

Mon Feb 1 12:28:01 2016	error	OTRS-CGI-00	Module Kernel/Output/HTML/NotificationSchedulerCheck.pm not in @INC (/opt/otrs/Custom /opt/otrs/Kernel/cpan-lib /opt/otrs/ /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . /etc/httpd)
how to solve that?

thanks to everyone

root
Moderator
Posts: 1193
Joined: 18 Dec 2007, 12:23
OTRS Version?: 4/5/6
Real Name: Roy Kaldung
Company: Znuny Inc.
Contact:

Re: log error after upgrading from otrs 4 to 5.0.6

Post by root » 01 Feb 2016, 15:02

Check if the missing file is really absent. How did your updated your system? Via package or tar.gz archive?
OTRS 4/5/6 CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

You need professional services? Check out https://www.znuny.com/

mrv
OTRS newbie
Posts: 9
Joined: 01 Feb 2016, 13:21
OTRS Version?: 5.0.6

Re: log error after upgrading from otrs 4 to 5.0.6

Post by mrv » 01 Feb 2016, 15:42

root wrote:Check if the missing file is really absent. How did your updated your system? Via package or tar.gz archive?
Sorry which is the missing file?

I made update using the .rpm

eandrex
OTRS superhero
Posts: 213
Joined: 04 Nov 2012, 23:58
OTRS Version?: OTRS 4.x
Real Name: Esteban
Company: NORTON DE COLOMBIA

Re: log error after upgrading from otrs 4 to 5.0.6

Post by eandrex » 01 Feb 2016, 21:33

Well, the files does not seem to be part of OTRS 5 (https://github.com/OTRS/otrs/tree/rel-5 ... utput/HTML) but it does belong to OTRS 4 -your previous version- (https://github.com/OTRS/otrs/tree/rel-4 ... utput/HTML), so I guess it is a leftover from a configuration file https://github.com/OTRS/otrs/blob/rel-4 ... er.xml#L61

mrv
OTRS newbie
Posts: 9
Joined: 01 Feb 2016, 13:21
OTRS Version?: 5.0.6

Re: log error after upgrading from otrs 4 to 5.0.6

Post by mrv » 02 Feb 2016, 16:36

eandrex wrote:Well, the files does not seem to be part of OTRS 5 (https://github.com/OTRS/otrs/tree/rel-5 ... utput/HTML) but it does belong to OTRS 4 -your previous version- (https://github.com/OTRS/otrs/tree/rel-4 ... utput/HTML), so I guess it is a leftover from a configuration file https://github.com/OTRS/otrs/blob/rel-4 ... er.xml#L61
OK, so what i have to do?

eandrex
OTRS superhero
Posts: 213
Joined: 04 Nov 2012, 23:58
OTRS Version?: OTRS 4.x
Real Name: Esteban
Company: NORTON DE COLOMBIA

Re: log error after upgrading from otrs 4 to 5.0.6

Post by eandrex » 02 Feb 2016, 17:49

Well, if that is the case, in /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm should be a reference to

Code: Select all

$Self->{"Frontend::NotifyModule"}->{"800-Scheduler-Check"} = ...
and since it is not recommended to touch that file manually, you should add the following to /opt/otrs/Kernel/Config.pm

Code: Select all

delete $Self->{"Frontend::NotifyModule"}->{"800-Scheduler-Check"};
run the equivalent of otrs.RebuildConfig.pl in OTRS 5 (otrs.Console.pl Maint::Config::Rebuild ?). if you start seeing error 500 pages, it is due to permissions, so fix them with otrs.SetPermissions.pl and that should do the trick
Last edited by eandrex on 02 Feb 2016, 17:58, edited 1 time in total.

User avatar
jjurkus
OTRS newbie
Posts: 47
Joined: 29 Jan 2016, 15:36
OTRS Version?: 5.0.7

Re: log error after upgrading from otrs 4 to 5.0.6

Post by jjurkus » 02 Feb 2016, 17:57

Code: Select all

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild" -s /bin/bash otrs
su -c "/opt/otrs/scripts/DBUpdate-to-5.pl" -s /bin/bash otrs
Did you run these commands when the otrs daemons were not running?
OTRS 5.0.x on CentOS 7 with a PostgreSQL database.

mrv
OTRS newbie
Posts: 9
Joined: 01 Feb 2016, 13:21
OTRS Version?: 5.0.6

Re: log error after upgrading from otrs 4 to 5.0.6

Post by mrv » 02 Feb 2016, 18:42

jjurkus wrote:

Code: Select all

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild" -s /bin/bash otrs
su -c "/opt/otrs/scripts/DBUpdate-to-5.pl" -s /bin/bash otrs
Did you run these commands when the otrs daemons were not running?
yes
i followed this guide

https://otrs.github.io/doc/manual/admin ... ading.html

no error was reported on console

mrv
OTRS newbie
Posts: 9
Joined: 01 Feb 2016, 13:21
OTRS Version?: 5.0.6

Re: log error after upgrading from otrs 4 to 5.0.6

Post by mrv » 03 Feb 2016, 11:39

Solved the problem re executing

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild" -s /bin/bash otrs
su -c "/opt/otrs/scripts/DBUpdate-to-5.pl" -s /bin/bash otrs

User avatar
jjurkus
OTRS newbie
Posts: 47
Joined: 29 Jan 2016, 15:36
OTRS Version?: 5.0.7

Re: log error after upgrading from otrs 4 to 5.0.6

Post by jjurkus » 03 Feb 2016, 18:45

Seriously? I was going to suggest that, but decided that might be stupid :( :)
OTRS 5.0.x on CentOS 7 with a PostgreSQL database.

tek
OTRS newbie
Posts: 9
Joined: 21 Oct 2015, 14:46
OTRS Version?: 4.0.13

Re: log error after upgrading from otrs 4 to 5.0.6

Post by tek » 17 May 2018, 10:03

I have exactly the same problem since the migration from 4 to 5.0.6. Notifications no longer work.

i followed this guide

https://doc.otrs.com/doc/manual/admin/5 ... ading.html

no error was reported on console but in OTRS :

Code: Select all

Module Kernel/Output/HTML/Notification/SchedulerCheck.pm not in @INC (/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/ /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . /etc/httpd)
when i run these commands :

Code: Select all

su -c "/opt/otrs/bin/otrs.Console.pl Maint::Config::Rebuild" -s /bin/bash otrs
su -c "/opt/otrs/scripts/DBUpdate-to-5.pl" -s /bin/bash otrs

Code: Select all

error	OTRS-DBUpdate-to-5.pl-10	Table 'otrs.notifications' doesn't exist, SQL: 'SELECT notification_type FROM notifications'
error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'subject' in 'field list', SQL: 'SELECT subject, text, content_type FROM notification_event'
error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'charset' in 'field list', SQL: 'SELECT charset FROM notification_event'
error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'charset' in 'field list', SQL: 'SELECT charset FROM auto_response'

how to solve that?

thanks
Otrs 5 - Mysql 5 - Centos 7

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

Re: log error after upgrading from otrs 4 to 5.0.6

Post by reneeb » 17 May 2018, 13:32

Did you upgrade via rpm or with source code?
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

tek
OTRS newbie
Posts: 9
Joined: 21 Oct 2015, 14:46
OTRS Version?: 4.0.13

Re: log error after upgrading from otrs 4 to 5.0.6

Post by tek » 17 May 2018, 13:47

thx reneeb :)

i upgrade with source code
Otrs 5 - Mysql 5 - Centos 7

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

Re: log error after upgrading from otrs 4 to 5.0.6

Post by reneeb » 17 May 2018, 14:24

Were the steps 6.1 and 6.2 of the Upgrading manual successful?
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

tek
OTRS newbie
Posts: 9
Joined: 21 Oct 2015, 14:46
OTRS Version?: 4.0.13

Re: log error after upgrading from otrs 4 to 5.0.6

Post by tek » 17 May 2018, 15:16

no error was reported on console


Step 6.1

Code: Select all

su -c "bin/otrs.Console.pl Maint::Database::Check" -s /bin/bash otrs
Trying to connect to database 'DBI:mysql:database=otrs;host=localhost;' with user 'otrs'...
Connection successful.
Step 6.2

Code: Select all

su -c "scripts/DBUpdate-to-5.pl" -s /bin/bash otrs

Migration started...

Step 1 of 18: Refresh configuration cache...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
done.

Step 2 of 18: Check framework version...done.

Step 3 of 18: Migrate Database Column Types...done.

Step 4 of 18: Migrate charset to UTF-8 on auto_response table...done.

Step 5 of 18: Migrate charset to UTF-8 on notification_event table...done.

Step 6 of 18: Migrate event based notifications to support multiple languages...done.

Step 7 of 18: Migrate notifications to event based notifications...done.

Step 8 of 18: Migrate send notification user preferences...done.

Step 9 of 18: Add Email notification method to all event based notifications...done.

Step 10 of 18: Migrate Output configurations to the new module locations...
--- Toolbar modules......done.
--- Ticket menu modules......done.
--- Ticket overview menu modules......done.
--- Ticket overview modules......done.
--- Preferences group modules......done.
--- SLA/Service/Queue preference modules......done.
--- Article view modules......done.
--- Article attachment modules......done.
--- Article compose modules......done.
--- NavBar menu modules......done.
--- NavBar ModuleAdmin modules......done.
--- Dashboard modules......done.
--- Customer user generic modules......done.
--- FilterText modules......done.
--- Notify modules......done.
done.

Step 11 of 18: Add TicketZoom menu cluster configurations......done.
done.

Step 12 of 18: Fix wrong entries in module registrations......done.
done.

Step 13 of 18: Fixup statistics time field configuration where the time interval is too small...
done.

Step 14 of 18: Fixup wrong notification tags...done.

Step 15 of 18: Fixup dashboard statistics output format configuration...
done.

Step 16 of 18: Uninstall Merged Feature Add-Ons...done.

Step 17 of 18: Clean up the cache...done.

Step 18 of 18: Refresh configuration cache another time...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
done.

Migration completed!
Error log GUI :

Code: Select all

Thu May 17 15:14:24 2018	error	OTRS-DBUpdate-to-5.pl-10	Table 'otrs.notifications' doesn't exist, SQL: 'SELECT notification_type FROM notifications'
Thu May 17 15:14:24 2018	error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'subject' in 'field list', SQL: 'SELECT subject, text, content_type FROM notification_event'
Thu May 17 15:14:24 2018	error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'charset' in 'field list', SQL: 'SELECT charset FROM notification_event'
Thu May 17 15:14:24 2018	error	OTRS-DBUpdate-to-5.pl-10	Unknown column 'charset' in 'field list', SQL: 'SELECT charset FROM auto_response'
Otrs 5 - Mysql 5 - Centos 7

tek
OTRS newbie
Posts: 9
Joined: 21 Oct 2015, 14:46
OTRS Version?: 4.0.13

Re: log error after upgrading from otrs 4 to 5.0.6

Post by tek » 23 May 2018, 09:31

Anyone else ? :(
Otrs 5 - Mysql 5 - Centos 7

fcasal
OTRS wizard
Posts: 142
Joined: 21 Apr 2014, 16:14
OTRS Version?: 6.0.7

Re: log error after upgrading from otrs 4 to 5.0.6

Post by fcasal » 23 May 2018, 18:31

Why not upgrade to last 5 version, 5.0.26? It fixes many bugs and problems.

root
Moderator
Posts: 1193
Joined: 18 Dec 2007, 12:23
OTRS Version?: 4/5/6
Real Name: Roy Kaldung
Company: Znuny Inc.
Contact:

Re: log error after upgrading from otrs 4 to 5.0.6

Post by root » 23 May 2018, 18:57

Hi,

Looks like 6.1 was not completely run, I'm missing this:

Code: Select all

cat scripts/DBUpdate-to-5.mysql.sql | mysql -p -f -u root otrs
- Roy
OTRS 4/5/6 CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

You need professional services? Check out https://www.znuny.com/

tek
OTRS newbie
Posts: 9
Joined: 21 Oct 2015, 14:46
OTRS Version?: 4.0.13

Re: log error after upgrading from otrs 4 to 5.0.6

Post by tek » 24 May 2018, 11:03

I am on the last version available 5.0.27
Otrs 5 - Mysql 5 - Centos 7

root
Moderator
Posts: 1193
Joined: 18 Dec 2007, 12:23
OTRS Version?: 4/5/6
Real Name: Roy Kaldung
Company: Znuny Inc.
Contact:

Re: log error after upgrading from otrs 4 to 5.0.6

Post by root » 24 May 2018, 11:24

Hi,

And you applied the database changes as I asked?

- Roy
OTRS 4/5/6 CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

You need professional services? Check out https://www.znuny.com/

Post Reply