3.1 - Invalid Challenge Token at logout - RESOLVED

[kruegerM]

When I click the logout link in the Agent interface of OTRS, 3.1.beta 5 - I get Error Message: Invalid Challenge Token! with the following Details:

Backend ERROR: OTRS-CGI-10 Perl: 5.10.0 OS: linux Time: Fri Feb 3 11:02:57 2012 Message: Invalid Challenge Token! Traceback (8077): Module: Kernel::Output::HTML::Layout::ChallengeTokenCheck (v1.380) Line: 1062 Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 417 Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 46 Module: (eval) (v1.90) Line: 204 Module: ModPerl::RegistryCooker::run (v1.90) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31

The Apache error_log file shows the following:

[Fri Feb 3 11:01:20 2012] -e: Use of uninitialized value in concatenation (.) or string at /opt/otrs//Kernel/System/Log.pm line 161, <DATA
> line 522.
ERROR: OTRS-CGI-10 Perl: 5.10.0 OS: linux Time: Fri Feb 3 11:01:20 2012

Message: Invalid Challenge Token!

Traceback (7901):
Module: Kernel::Output::HTML::Layout::ChallengeTokenCheck (v1.380) Line: 1062
Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 417
Module: ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 46
Module: (eval) (v1.90) Line: 204
Module: ModPerl::RegistryCooker::run (v1.90) Line: 204
Module: ModPerl::RegistryCooker::default_handler (v1.90) Line: 170
Module: ModPerl::Registry::handler (v1.99) Line: 31

Any ideas/suggestions appreciated.

[jojo]

I do not get the error on logout.

It is a beta version, do not use it for production systems!

[kruegerM]

ok - still working on development machine - but now with officially released 3.1.
Tried a straight 3.1 install - everything worked great.
New image, this time a copy of the production system and verified operation
Updated it to 3.1
Everything is fine EXCEPT still getting this error at logout.

[earwax]

Was everything fine when you ran OTRS before 3.1.1? I wonder if some of your Perl modules need to be updated?

[kruegerM]

After setting up the initial 3.0.6 copy of production I took the system through it's paces. Everything functioned correctly as 3.0.6, it's only after the 3.1 update that I have the logout issue. However, I will double-check the perl and other supporting installations; maybe something is absent that 3.0 didn't care about but 3.1 does.

[scareface]

It is because there are old Files in RPM
e.g.
# $Id: Header.dtl,v 1.105 2010/12/29 14:44:59 martin Exp $ should be -> # $Id: Header.dtl,v 1.111 2011/12/23 10:56:02 mg Exp $
This dtl is responsible for logout. The Challenge Token is implemented in v 1.108 so it Fails in v1.105 because it isn't implemented.

Please can anyone fix this so the RPM is shipped with the newes Files.
I download this one http://ftp.otrs.org/pub/otrs/RPMS/fedor ... noarch.rpm today about 13:00

[jojo]

Hi,

I downloaded the rpm and checked the content:

# --
# Header.dtl - provides global HTML header
# Copyright (C) 2001-2011 xxx, http://otrs.org/
# --
# $Id: Header.dtl,v 1.111 2011/12/23 10:56:02 mg Exp $

So somethin went wrong with your upgrade, in the file everything is OK

[scareface]

So somethin went wrong with your upgrade, in the file everything is OK

I delete the old folder of RC1.

Code: Select all

rm -r -f /opt/otrs/

Than install 3.0.11

Code: Select all

rpm -ivh --force otrs-3.0.11-03.noarch.rpm

import DB of productiv system
and installing 3.1.1

Code: Select all

rpm -Uvh otrs-3.1.1-02.noarch.rpm

And doing an upgrade as described in UPGRADE

Which step is wrong?

[edit]
I found a way to install and upgrade for my system.
using yum all is perfect and the newes files are there

Code: Select all

yum -v install otrs-3.0.11-03.noarch.rpm
yum -v update otrs-3.1.1-02.noarch.rpm

Thank you jojo to bring me on the right way.
[/edit]

[kruegerM]

I tried again - put copy of production on development server, then upgraded with 3.1.1-02 - logout is now working correctly. Not sure what happened, but it's ok now.