[rt-users] Some users cannot create tickets others can

[Baxter Shepperson]

For some reason using Firefox and clicking Create Ticket repeatedly and
very quickly will work about 75% of the time.  Seems like a performance
issue.  IE doesn't work at all really.  Any ideas?  Anyone else run into
this?

-----Original Message-----
From: Sam Snow [mailto:sam.snow at christianheritageschool.org] 
Sent: Wednesday, April 20, 2005 9:22 PM
To: Baxter Shepperson
Cc: rt-users at lists.bestpractical.com
Subject: RE: [rt-users] Some users cannot create tickets others can


>
> -----Original Message-----
> From:	rt-users-bounces at lists.bestpractical.com on behalf of Baxter
> Shepperson
> Sent:	Wed 4/20/2005 3:10 PM
> To:	rt-users at lists.bestpractical.com
> Cc:
> Subject:	[rt-users] Some users cannot create tickets others can
>   Using rt-3.0.10-3 Fedora Core 2.  RT is working brilliantly for some
and
> others cannot create tickets.  Both IE and Firefox just time out or
give
> an error message "queue cannot be created"  All user's permissions are
> the same.  One even has ALL permissions granted.  Cannot find any
errors
> in mysql logs but I see this error "[Wed Apr 20 14:06:23 2005]
[notice]
> child pid 3264 exit signal Segmentation fault (11)" in my httpd error
> log.
>
>  I would sincerely appreciate ANY pointers as I feel I am very close
and
> RT is working for me for the most part.
>
>
> -----Original Message-----
> From:	rt-users-bounces at lists.bestpractical.com on behalf of Baxter
> Shepperson
> Sent:	Wed 4/20/2005 3:17 PM
> To:	rt-users at lists.bestpractical.com
> Cc:
> Subject:	RE: [rt-users] Some users cannot create tickets others
can
>
>   Research shows me so far that this was a problem with perl that was
> resolved with perl version 5.8.3 which is what I'm running.  Could it
> still be a problem with apache 2.0?  Why would it affect only a few
> users?  What would be causing browser timeouts for some and not
others?
>
>
> Baxter Shepperson said:
>   now I think it maybe Apache 2.0 that is causing the problem.  Has
> anybody else run into this before?  Shall I downgrade to Apache 1.33?
>

As a point of reference, 3.4.1 is working fine for me with apache2, but
I
am running it under fastcgi on a debian sarge box.

Sam