OTRS 3.1.5 Log error entries on system log

Moderator: crythias

Locked
StefanoBoccanera
Znuny newbie
Posts: 76
Joined: 23 Feb 2011, 15:43
Znuny Version: 3.1.5
Real Name: Stefano Boccanera
Company: I.Conseils (self-employee)
Location: Rome (Italy)

OTRS 3.1.5 Log error entries on system log

Post by StefanoBoccanera »

Hi

I just completed the migration to OTRS 3.1.5. All sound fine but I have following error log entries into the system log:

Tue Jun 5 16:44:19 2012 error OTRS-CGI-99 Need HistoryTypeID!
Tue Jun 5 16:44:19 2012 error OTRS-CGI-99 No TypeID for TicketDynamicFieldUpdate found!

Basically the error pair entries are logged for every dynamic field I configured for my ticket. The ticket is stored correctly but seem as OTRS cannot add the history entry.

Following it's the log from http error log
ERROR: OTRS-CGI-99 Perl: 5.12.2 OS: linux Time: Tue Jun 5 16:44:19 2012

Message: No TypeID for TicketDynamicFieldUpdate found!

Traceback (28841):
Module: Kernel::System::Ticket::HistoryTypeLookup (v1.549.2.3) Line: 5148
Module: Kernel::System::Ticket::HistoryAdd (v1.549.2.3) Line: 5186
Module: Kernel::System::DynamicField::ObjectType::Ticket::PostValueSet (v1.9) Line: 148
Module: Kernel::System::DynamicField::Backend::ValueSet (v1.71) Line: 499
Module: Kernel::Modules::AgentTicketPhone::Run (v1.47) Line: 1151
Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 868
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

ERROR: OTRS-CGI-99 Perl: 5.12.2 OS: linux Time: Tue Jun 5 16:44:19 2012

Message: Need HistoryTypeID!

Traceback (28841):
Module: Kernel::System::Ticket::HistoryAdd (v1.549.2.3) Line: 5193
Module: Kernel::System::DynamicField::ObjectType::Ticket::PostValueSet (v1.9) Line: 148
Module: Kernel::System::DynamicField::Backend::ValueSet (v1.71) Line: 499
Module: Kernel::Modules::AgentTicketPhone::Run (v1.47) Line: 1151
Module: Kernel::System::Web::InterfaceAgent::Run (v1.64) Line: 868
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
I'll try to flow across the code but after review my configuration setting I didn't found any problem.

Any idea about it?
Stefano Boccanera

OTRS : 3.1.5
ITSM : 3.1
S.O : RH
RDBMS : Postgres
simonsys
Znuny newbie
Posts: 1
Joined: 26 Jul 2012, 09:52
Znuny Version: 3.1.7
Real Name: Simon

Re: OTRS 3.1.5 Log error entries on system log

Post by simonsys »

Any news about this?
I have the same problem, on a 3.1.7. It happens when we launch PostMasterMailbox.pl (or at least I've seen it only there up to now)
crythias
Moderator
Posts: 10170
Joined: 04 May 2010, 18:38
Znuny Version: 5.0.x
Location: SouthWest Florida, USA
Contact:

Re: OTRS 3.1.5 Log error entries on system log

Post by crythias »

relevant code

Code: Select all

    # db query
    return if !$Self->{DBObject}->Prepare(
        SQL  => 'SELECT id FROM ticket_history_type WHERE name = ?',
        Bind => [ \$Param{Type} ],
    );
    while ( my @Row = $Self->{DBObject}->FetchrowArray() ) {
        $Self->{$CacheKey} = $Row[0];
    }

    # check if data exists
    if ( !$Self->{$CacheKey} ) {
        $Self->{LogObject}->Log(
            Priority => 'error',
            Message  => "No TypeID for $Param{Type} found!",
        );
        return;
    }
Summary: TicketDynamicFieldUpdate is being passed as string as a HistoryType, but it doesn't have a reference value in the table ticket_history_type

You can do this:

Code: Select all

INSERT INTO ticket_history_type (name, valid_id, create_by, create_time, change_by, change_time)
    VALUES
    ('TicketDynamicFieldUpdate', 1, 1, current_timestamp, 1, current_timestamp);
Danger level: pretty low. It already doesn't exist, but if you run it twice, it *might* duplicate. Backup database before making changes.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
AdminDH
Znuny newbie
Posts: 1
Joined: 14 Aug 2012, 09:28
Znuny Version: 3.1.7
Company: De Heus PTY LTD

Re: OTRS 3.1.5 Log error entries on system log

Post by AdminDH »

This worked for me. Thank you!

I had other missing entries:
EscalationResponseTimeStart
EscalationResponseTimeNotifyBefore
Locked