IdP clustering with memcached

[Vedran Bartonicek]

>>>You have to run a memcached server on whatever host you're attempting to
connect to, and your note reads like you have not done that. Fortunately
it's trivial to run memcached, and my recommendation is that you run a
memcached daemon on every IdP host per the docs.

That was it, many thanks!
After installing and starting the daemon manually, it worked  - with IdP
configured to connect to memcached running on the same node.
I was expecting that IdP app would start it since there is some memcached
lib (obviously just a client) as part of the rpm.











On 20 September 2016 at 13:53, Marvin Addison <marvin.addison at gmail.com>
wrote:

> On Tue, Sep 20, 2016 at 6:14 AM Vedran Bartonicek <vbartoni at gmail.com>
> wrote:
>
>> 2016-09-20 12:59:20.350 INFO net.spy.memcached.MemcachedConnection:
>>  Reconnecting {QA sa=/10.0.221.53:11211, #Rops=0, #Wops=0, #iq=0,
>> topRop=null, topWop=null, toWrite=0, interested=0}
>>
>
> That's the _client_ attempting to connect to 10.0.221.53:11211, which
> presumably is your IdP host.
>
> It appears that nobody is listening to port 11211 (e.g. by using netstat
>> -tulpn).
>>
>
> You have to run a memcached server on whatever host you're attempting to
> connect to, and your note reads like you have not done that. Fortunately
> it's trivial to run memcached, and my recommendation is that you run a
> memcached daemon on every IdP host per the docs.
>
> M
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160920/14b6be54/attachment-0001.html>