RT warning message regarding Custom Field

Hi,

after upgrading to RT 4.4.1 I’m facing the following issue:

When updating a Ticket in a certain queue (before submitting, opening
the update page is sufficient), RT logs the following warning message:

[23016] [Thu Oct 27 12:11:24 2016] [warning]: Couldn’t load object RT::Transaction #0 (/opt/rt4/sbin/…/lib/RT/Interface/Web.pm:3107)

Using the source code, I was able to track this issue down to be related
to a Custom Field that is set up as follows:

Name: IP Address
Type: Enter one IP address
Applies to: Ticket Transactions
Entry Hint: Enter one IP Address

the other fields are empty.

If I disable this custom field for the queue it is enabled for, the
warning message disappears.

Does anybody have an idea what could be going on here?

Cheers,

Klaus

Hi,

after upgrading to RT 4.4.1 I’m facing the following issue:

When updating a Ticket in a certain queue (before submitting, opening
the update page is sufficient), RT logs the following warning message:

[23016] [Thu Oct 27 12:11:24 2016] [warning]: Couldn’t load object RT::Transaction #0 (/opt/rt4/sbin/…/lib/RT/Interface/Web.pm:3107)

Sorry, the file contained some debug code; the error is actually raised
in line 3104.

Also, I found the following patch for RT 4.0.12:

http://lists.bestpractical.com/pipermail/rt-commit/2013-May/024391.html

Is that a known issue? It didn’t occur for me in RT 4.0.7 (Debian
Package), which is the Version I was using before upgrading to 4.4.1.

Thanks again,

Klaus

Hello Klaus,

I have the same problem with CustomFields, which applie to Ticket Transactions, both in RT 4.2.13 and in RT 4.4.1.

Have you received a response from the BPS developers to your question?
Is that a known issue?

The adaptions from the patch works also for me. The warning no longer occurs. But is this procedure recommended from BPS?

Regards,
Patrick

System: Debian jessie 8.8
DB: MariaDB 10.1.21

This was fixed in 4.2.14 and 4.4.2 by this commit.

I don’t believe it caused any issues, just extra noise in the logs, correct?

Thank you very much for the answer, Jim!

Yes, it just seems to cause extra noise in the logs.