400: Error: connect ECONNREFUSED #171

Closed
strk opened this Issue Feb 27, 2014 · 5 comments

Projects

None yet

1 participant

@strk
Contributor
strk commented Feb 27, 2014

The logged error is not very useful without more context...

@strk strk added this to the 1.8.4 milestone Feb 27, 2014
@strk strk added the enhancement label Feb 27, 2014
@strk
Contributor
strk commented Feb 27, 2014

\cc @rafacas

@strk
Contributor
strk commented Feb 27, 2014

Also spotted for [POST LAYERGROUP ERROR].
Tried locally by killing redis or sql-api but in both cases the error that comes out is still nicely prefixes.

@strk
Contributor
strk commented Feb 27, 2014

I suspect the error comes deep from the tryGetTileOrGrid, and specifically from torque renderer, not prefixing the error raised by the sql adapter here: https://github.com/CartoDB/Windshaft/blob/0.19.1/lib/windshaft/renderers/torque.js#L376

@strk
Contributor
strk commented Feb 27, 2014

On our side (windshaft-cartodb) we could prefix the error where we catch it (during layers test, I suppose)

@strk
Contributor
strk commented Feb 27, 2014

ERR, that's still done in windshaft, so nothing for us here, all delegated to CartoDB/Windshaft#164

@strk strk pushed a commit that closed this issue Feb 28, 2014
Sandro Santilli Upgrade windshaft to 0.19.2
Fixes obscure "ECONNREFUSED" error message (closes #171)
Change some http status responses to be more appropriate to the case
73276b1
@strk strk closed this in 73276b1 Feb 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment