On 2014-01-16 11:19, Will Roberts wrote:
Hi,
I'm working with an SmpScale configuration with 2 workers defined.
Each worker has its own set of unique ports that it listens on. The
coordinator process doesn't have any http_port lines and generates
tons of these warnings:
ERROR: No forward-proxy ports configured
That doesn't seem great, am I missing something? I'm sure I can work
around this by giving it some dummy port to listen on, but I'd rather
not if it doesn't really need it.
Something strange going on here with your Coordinator. That error is
only produced when actively generating a response that needs to embed a
URI for some resource served by Squid.
What is your coordinator doing that needs it to be aware of the worker
service port(s) so often?
Amos
