Summary | Hord could not connect to PostgreSQL via pgpool2 |
Queue | Horde Groupware Webmail Edition |
Queue Version | 1.2.2 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | pama0005 (at) hs-niederrhein (dot) de |
Created | 04/30/2009 (5910 days ago) |
Due | |
Updated | 04/30/2009 (5910 days ago) |
Assigned | |
Resolved | 04/30/2009 (5910 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
bug in pgpool2. It seems that pgpool2 could not handle transactions
(BEGIN, COMMIT) correctly.
(firefox) trys to log in into horde, but nothing happens, but if I
than restart pgpool2 than I can see the horde portal, but if I try to
do something nothing happens until I restart pgpool2 the next time.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ Hord could not connect to PostgreSQL via pgpool2
Type ⇒ Bug
State ⇒ Unconfirmed
background. For loadbalancing an redundancy I'm using pgpool2 to
connect to the database. The complete setup runs fine until I enable
parallel querry mode an querry cache in pgpool2. Since I've done that
I could not connect to horde, my browser try to access horde but
nothing happens.
At first I think it was a bug in pgpool2 or my php but I'm able to
connect to the database via pgpool2 with psql on commandline and with
an self written php script, so I think the problem is somewhere in
horde.
Systeminformation:
OS: Ubuntu 8.04 Server
PostgreSQL-Server: 8.3.1
PHP: 5.2.4-2ubuntu5.6 with Suhosin-Patch
PGpool2: Version 2.2