Skip to content
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

Ignores my postgres port setting #60

Closed
tjwebb opened this issue Dec 7, 2012 · 3 comments
Closed

Ignores my postgres port setting #60

tjwebb opened this issue Dec 7, 2012 · 3 comments

Comments

@tjwebb
Copy link

tjwebb commented Dec 7, 2012

For some crazy reason, it is trying to use port 6432 to connect to postgis, even though it is clearly set to 5432 in my development.js

Postgis Plugin: could not connect to server: Connection refused Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 6432? host=127.0.0.1 port=6432 dbname=cartodb_dev_user_2_db user=development_cartodb_user_2 connect_timeout=4 encountered during parsing of layer 'nbt_offices' in Layer at line 22"

I wish it told me line 22 of which file !!

@strk
Copy link
Contributor

strk commented Dec 7, 2012

Dejavu !
For some reason I think this was fixed in cartodb-1.0 (but could be wrong).

About the error message: it comes from mapnik, which is NOT reading that info
from a file (so can't give you a filename) but from a memory buffer.
In turn that memory is read from a redis store. There's a tools/show_style
in Windshaft-cartodb which you may find useful in that it should extract
the XML file that passed to mapnik generated that error message.
It takes the "username" (3rd level domain, used to get to your database)
and a table name ("nbt_offices" in your case).

Those XML files are cached so changing development.js after the first
run won't re-write them (and so could still have the old port number).
Another script under tools/ should help with regenerating those caches.

Please let me know what you find out

@tjwebb
Copy link
Author

tjwebb commented Dec 7, 2012

Yep, sure enough, tools/show_styles spits this out:

<Parameter name="port"><![CDATA[6432]]></Parameter>

I have no idea how it got there, but I'll figure out how to wipe it. This is a great start, thanks for the pointer.

@tjwebb
Copy link
Author

tjwebb commented Dec 7, 2012

Ok this is resolved. But of course, this just reveals another issue: #61 ;-)

@strk strk closed this as completed Dec 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants