Syslog Errors

[wipeout_630]

I see the following errors in my System Log every time a ticket is created (pulled from /var/log/messages).
I have disabled the DynamicFields in ViewPhoneNew and ViewEmailNew but the messages continue to appear.

Code: Select all

Sep  4 15:02:27 limelight OTRS-CGI-01[29104]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:33 limelight OTRS-CGI-01[29109]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:38 limelight OTRS-CGI-01[29108]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:41 limelight OTRS-CGI-01[29109]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:44 limelight OTRS-CGI-01[29103]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:44 limelight OTRS-CGI-01[29103]: [Error][Kernel::System::ITSMCIPAllocate::PriorityAllocationGet][Line:232]: Need ImpactID!
Sep  4 15:02:46 limelight OTRS-CGI-01[29107]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:02:46 limelight OTRS-CGI-01[29107]: [Error][Kernel::System::ITSMCIPAllocate::PriorityAllocationGet][Line:232]: Need ImpactID!
Sep  4 15:03:01 limelight OTRS-CGI-01[29105]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:03:01 limelight OTRS-CGI-01[29105]: [Error][Kernel::System::ITSMCIPAllocate::PriorityAllocationGet][Line:232]: Need ImpactID!
Sep  4 15:03:06 limelight OTRS-CGI-01[30486]: [Error][Kernel::System::DynamicField::DynamicFieldUpdate][Line:356]: Need ID!
Sep  4 15:03:06 limelight OTRS-CGI-01[30486]: [Error][Kernel::System::ITSMCIPAllocate::PriorityAllocationGet][Line:232]: Need ImpactID!

I see these errors in the log whenever I modify anything in SysConfig:

Code: Select all

Sep  4 14:43:18 limelight OTRS-CGI-01[29107]: [Error][Kernel::System::SysConfig::ConfigSubGroupList][Line:1042]: Need Name!
Sep  4 14:58:15 limelight OTRS-CGI-01[29103]: [Error][Kernel::System::SysConfig::ConfigSubGroupList][Line:1042]: Need Name!

I also get error messages when "TriggerEscalationStopEvents" is called (is this normal?):

Code: Select all

Sep  4 15:03:27 limelight OTRS-CGI-01[29105]: [Error][Kernel::System::Ticket::Event::TriggerEscalationStopEvents::Run][Line:55]: TriggerEscalationStopEvents called for ArticleCreate
Sep  4 15:03:27 limelight OTRS-CGI-01[29105]: [Error][Kernel::System::Ticket::Event::TriggerEscalationStopEvents::Run][Line:55]: TriggerEscalationStopEvents called for TicketStateUpdate

I have renamed the PriorityIDs and ImpactIDs to match my desired naming convention and have changed them in every SysConfig option I could find. Tickets are processing normally and I see no errors on the FrontEnd.

[wipeout_630]

I have updated the state names and state types in SQL and verified they all match correct in SysConfig but I am still getting the same errors.

[crythias]

I don't know ITSM well enough, but this *sounds* like the AgentTicketPhone.dtl and/or AgentTicketEmail.dtl is attempting to store some Dynamic Fields via the corresponding Modules. See if you have an OTRS/Custom/Kernel/Modules/xxx or other theme that is trying to do this.

It also sounds like a field in the .dtl is required for ITSM and not passed.

If you looked at your Package Manger, does it indicate that your ITSM install is properly configured per stock?

[jojo]

you are not supposed to do this:

I have updated the state names and state types in SQL and verified they all match correct in SysConfig but I am still getting the same errors.

[wipeout_630]

There are several .rpmsave and .backup files under /OTRS/Kernel/Output and /OTRS/Kernel/Modules. I think the upgrade from 3.0 to 3.1 broke more than I realized. I'm going to try a fresh install on another testbed and configure from scratch to see if it's a Theme or SysConfig issue. And yes, Package Manager says everything is installed correctly. To be on the safe side I also reinstalled the ITSM suite but no luck.

@Jojo
http://doc.otrs.org/3.1/en/html/states-customizing.html

[jojo]

this is for adding state types, not for renaming them. You can not rename state types without changing source code. Adding new state type will also need some coding so OTRS knows what to do with it.