-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: Postgis Plugin: bad connection #16
Comments
Only the queries for the working tiles show up in the postgresql log. No trace in the postgresql log about any connection error. |
The error message comes from mapnik itself. Debugging it now. |
I use windshaft with pg_bouncer (I think this is in the readme), but I On Wed, Apr 18, 2012 at 11:21 AM, strk
|
On Wed, Apr 18, 2012 at 03:37:23AM -0700, tokumine wrote:
No trace of pg_bouncer in the Windshaft-cartodb README file
Don't you think it's a bug ? --strk; |
My database has max_connection 100. Should that value be configured in the environment config instead ? |
Alright I succeeded in fixing this. It was the max_size parameter in the XML file. Setting it to 0 keeps growing it until it ends out of connections. So I think there are a couple of issues here:
|
Set map connections to 10 in the environment settings? On 18 Apr 2012, at 15:09, strkreply@reply.github.com wrote:
|
Note, after setting connections to 0, flush the XML cache.... Simon On 18 Apr 2012, at 15:09, strkreply@reply.github.com wrote:
|
So I tried to reset redis cache and see the effects. I got no leakage, but a stable 4 connections, no matter max_size=0. I could reproduce the problem by killing windshaft node instance and restarting it.
The debugging information in parens I added the code for in my version of mapnik. There must be something making windshaft choke on kill... |
I'm still here, and can't fix it anymore now. redis keys are all cleared except "rails:cartodb_dev_user_2_db:clu_a_wi043" |
Sorry strk, at the airport now. Will check in when I land On 18 Apr 2012, at 16:02, strkreply@reply.github.com wrote:
|
Setting max_size:32 in windshaft's config/environment/development.js and flushing the XML in redis makes it work again. This time the pool has 4 records again. Sounds like max_size:0 isn't working as expected. |
max_size=0 commented out, matching production (and fixing this issue for me), in 0a305a9 |
tks On Mon, May 7, 2012 at 5:52 PM, strk <
|
I was seeing complete tiles missing from the display of a map and when looking at the windshaft log file I found a bunch of:
For other tiles it works fine so dunno what to look at.
Maybe a limit on number of client connections ?
The text was updated successfully, but these errors were encountered: