[rt-users] Weird panic error

[Bart]

Hi everyone,

Thanks for all the replies!

I'll have a look at the perl stuff and see if something can receive an
update, but removing the HTML::Quoted packet doesn't seem right when
functionality is lost. Also, debuggin in production is rather hard since
the problem is pretty hard to predict (as I mentioned, I can't reproduce
it).

The problem only shows up every now and then, usually we empty the RT
caches and restart Apache after which the problem stays away for a few days
again. So it isn't a huge issue, just an annoying one when it occurs.

One thing that doesn't seem right are the errors relating to the database,
I think I'll take a closer look into that since that shouldn't happen at
all. The database is hosted on another server, but this is all on ethernet
distance (low latency). But, there might be an issue with the database
configuration or it might need more tweaking. Compared to the testing
environment this is the factor that's different, in the testing environment
the database is hosted on the same machine as RT.

Thanks for all the input so far, I believe that I can get allot further now
in solving this problem :)

-- Bart


Op 16 februari 2012 18:21 schreef Kevin Falcone
<falcone at bestpractical.com>het volgende:

> On Thu, Feb 16, 2012 at 06:05:00PM +0100, Gerard FENELON wrote:
> > Sorry Slightly off-topic
> >
> > On 2012-02-16 17:10, Kevin Falcone wrote:
> > >[...]
> > >>      Apache2::RequestIO::rflush: (103) Software caused connection
> abort at
> > >>      /usr/local/share/perl/5.10.1/Plack/Handler/Apache2.pm line 153,
> referer: [2]https://rt......
> > >Traditionally this is "someone hit the stop button".
> >
> > Honestly I have doubts on that traditional wisdom.
> > For example, I have 102 occurences of that error between
> > Mon Feb 13 07:37:12 2012 and Thu Feb 16 17:01:44 2012
> > 102 people hitting the stop button in 3,5 days ?!?
>
> Gerard - see Thomas' response about mobile connections.  My main point
> is that this error is not likely to be the problem he is seeking.
> Unfortunately, it's a mod_perl level error with no useful way to
> debug, and it's been that way since the mod_perl1 days.
>
> -kevin
>
> --------
> RT Training Sessions (http://bestpractical.com/services/training.html)
> * Boston — March 5 & 6, 2012
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120220/4b9f5d4e/attachment.htm>