I’ve been testing the upgrade from RT 3.2.1 to RT 3.5.5. I’ve run into
a problem that I don’t run into in my upgrade from 3.2.1 to 3.4.4. I
also run into this problem with a vanilla install of 3.5.5 so
I know it’s not upgrade related. When I open a new ticket after the
upgrade and click Update Ticket, I get the following message:
“The connection to fqdn.example.com has terminated unexpectedly. Some
data may have been transferred.”
What version of mason are you using?
Any ideas? I’m running this on RHEL 4.0 with Perl 5.8.7, mod_perl
2.0.1, & Apache 2.0.54 (not Red Hat’s Apache2).
Is this not yet a supported configuration? Which version of Mason do you
RT 3.5 is very much still a testing branch. With an open source product
"supported" has a rather…nuanced meaning. We’re still supporting RT2
for customers. We’re supporting RT 3.0, 3.2, 3.4 and several
development/feature branches off of 3.4. While I’d love to get to the
bottom of whatever’s biting you with 3.5, we don’t have the resources to
dive into every issue reported by a user. (As the old line goes, “if it
breaks, you get to keep both pieces.”)
So yes, the configuration you describe is one that I would expect to
work. But if you need a stable production RT, I’d suggest that you
consider sticking with the stable production releases.
All that being said, I’d love to hear more about what you see as you dig
into this issue. Things to check:
Is it mod_perl2? (If you use standalone_httpd or fastcgi, does it
Is it SSL?
Is it some browser or set of browsers?