Correspondance (probably) not recorded in WebUI

Hi,
I submitted the below to rt-users a few days ago, but reckon I might get better mileage here… Anybody even got pointers on debugging this?

I’m encountering this problem in rt-2.0.15

When sending a reply from the web interface, the transaction is not recorded, and an email is sent with no body, just the headers.

I’ve attached the log output from RT, but the highlights are:
[Mon Sep 1 13:04:32 2003] [crit]: RT::Attachment->Create couldn’t, as you didn’t specify a transaction

[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): To is feargal@chrysalink.net
[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): Cc is
[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): Bcc is
[Mon Sep 1 13:04:32 2003] [debug]: RT::Transaction=HASH(0x8e22d5c): Prepared NotifyRequestors

[Mon Sep 1 13:04:32 2003] [debug]: RT::Transaction=HASH(0x8e22d5c): Committed NotifyRequestors

[Mon Sep 1 13:04:33 2003] [warning]: Transaction Created
[Mon Sep 1 13:04:33 2003] [err]: RT::Ticket=HASH(0x8e76b24) couldn’t init a transaction (Transaction Created)

I’m running RT-2.0.15 with perl 5.8.0, PostgreSQL 7.3.3, FreeBSD 4.8-STABLE, Apache 1.3.28 with mod_fastcgi 2.4.0

Before anyone asks, yes, I’m not the requestor, yes the scrips are set up to send, and yes I know RT never emails the actor :slight_smile:

Researching the problem, I’ve found similar problems, but they claim to have been resolved a few releases ago, and exhibit different behaviour - http://rt3.fsck.com/Ticket/Display.html?id=950

The correspondance template uses {$Transaction->Content()}, but that should be irrelevant anyway as it looks as if it’s not getting the transaction in the first place.

Any ideas?

Feargal Reilly,
Systems Administrator,
The FBI.

Hi,
I’m encountering this problem in rt-2.0.15

When sending a reply from the web interface, the transaction is not recorded, and an email is sent with no body, just the headers.

I’ve attached the log output from RT, but the highlights are:
[Mon Sep 1 13:04:32 2003] [crit]: RT::Attachment->Create couldn’t, as you didn’t specify a transaction

[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): To is feargal@chrysalink.net
[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): Cc is
[Mon Sep 1 13:04:32 2003] [debug]: RT::Action::Notify=HASH(0x8f87c9c): Bcc is
[Mon Sep 1 13:04:32 2003] [debug]: RT::Transaction=HASH(0x8e22d5c): Prepared NotifyRequestors

[Mon Sep 1 13:04:32 2003] [debug]: RT::Transaction=HASH(0x8e22d5c): Committed NotifyRequestors

[Mon Sep 1 13:04:33 2003] [warning]: Transaction Created
[Mon Sep 1 13:04:33 2003] [err]: RT::Ticket=HASH(0x8e76b24) couldn’t init a transaction (Transaction Created)

I’m running RT-2.0.15 with perl 5.8.0, PostgreSQL 7.3.3, FreeBSD 4.8-STABLE, Apache 1.3.28 with mod_fastcgi 2.4.0

Before anyone asks, yes, I’m not the requestor, yes the scrips are set up to send, and yes I know RT never emails the actor :slight_smile:

Researching the problem, I’ve found similar problems, but they claim to have been resolved a few releases ago, and exhibit different behaviour - http://rt3.fsck.com/Ticket/Display.html?id=950

The correspondance template uses {$Transaction->Content()}, but that should be irrelevant anyway as it looks as if it’s not getting the transaction in the first place.

Any ideas?

Feargal Reilly,
Systems Administrator,
The FBI.