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

renderd does not listen on unix and TCP sockets. #137

Closed
StyXman opened this issue Sep 16, 2016 · 0 comments · Fixed by #263
Closed

renderd does not listen on unix and TCP sockets. #137

StyXman opened this issue Sep 16, 2016 · 0 comments · Fixed by #263

Comments

@StyXman
Copy link

StyXman commented Sep 16, 2016

I'm configuring renderd on a separate machine than the one wit Apache/mod_tile, so I'm obliged to put this in renderd.conf:

iphostname=0.0.0.0
ipport=7654

But if I also want to test that it's running properly with render_list, I need the Unix socket, because I can't tell it the IP/port to connect to, so:

socketname=/var/run/renderd/renderd.sock

renderd ignores the latter:

Sep 16 11:47:16 diablo renderd[4832]: Parsing section renderd
Sep 16 11:47:16 diablo renderd[4832]: config renderd: ip socket=0.0.0.0:7654
Sep 16 11:47:16 diablo renderd[4832]: config renderd: num_threads=2tile
Sep 16 11:47:16 diablo renderd[4832]: config renderd: num_slaves=0
Sep 16 11:47:16 diablo renderd[4832]: config renderd: tile_dir=/var/lib/mod_tile
Sep 16 11:47:16 diablo renderd[4832]: config renderd: stats_file=/var/run/renderd/renderd.stats

Maybe the easiest way to solve this is to teach render_* to use a TCP/IP address.

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

Successfully merging a pull request may close this issue.

1 participant