I was running some DB admin stuff, and that backed up the database, so
all available connections were taken. When you do something in RT
during this time, you get a server error notice, and this in the logs:
[Mon Sep 10 17:10:18 2001] [error] Connect Failed Sorry, too many clients already
at /var/vkmlm/rt2/lib/RT.pm line 14
I think RT should at least trap this and print a suitable error
message, rather than let apache’s internal error page pop up.
This is with Postgres.
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
I’ll happily take a patch for that.On Mon, Sep 10, 2001 at 05:14:48PM -0400, Vivek Khera wrote:
I was running some DB admin stuff, and that backed up the database, so
all available connections were taken. When you do something in RT
during this time, you get a server error notice, and this in the logs:
[Mon Sep 10 17:10:18 2001] [error] Connect Failed Sorry, too many clients already
at /var/vkmlm/rt2/lib/RT.pm line 14
I think RT should at least trap this and print a suitable error
message, rather than let apache’s internal error page pop up.
This is with Postgres.
–
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
“JV” == Jesse Vincent jesse@bestpractical.com writes:
JV> I’ll happily take a patch for that.
It seems to be an Apache::DBI fatal error… I’ll see if I can find a
way to propagate it back up the chain.
JV> On Mon, Sep 10, 2001 at 05:14:48PM -0400, Vivek Khera wrote: