Re: Pointing to Memcached on Remote Server

Thanks again everyone The solution was a quick adjustment in memcached.conf. Changing -l 127.0.0.1 to -l 0.0.0.0 Matt On Dec 5 2011, 1:27 pm, mattym wrote: > Thanks all - > > I stepped away from this issue for a few days.  I am confident this > thread will point me in

Re: Pointing to Memcached on Remote Server

Thanks all - I stepped away from this issue for a few days. I am confident this thread will point me in the right direction. I did notice with nmap I am getting: PORT STATE SERVICE 11211/tcp closed unknown I will be digging into this issue again soon and this thread helps! Thanks again

Re: Pointing to Memcached on Remote Server

Also check memcached configuration (/etc/memcached.conf) from this file,you can limit IP addresses that memcached listening to here is a configuration parameter that you might have # Specify which IP address to listen on. The default is to listen on all IP addresses # This parameter is one of the

Re: Pointing to Memcached on Remote Server

Hi Matt, Did you check that port 11211 is open for connections on the remote server? Regards, Medhat On Fri, Dec 2, 2011 at 2:49 PM, mattym wrote: > Hi all - > > I am stuck on this one. Caching with memcached works when I reference > the local box holding Django. But

Re: Pointing to Memcached on Remote Server

Matt, Do you have the port open on the public-facing side of the remote IP? In other words, from another computer outside of that remote computer's network, can you run "nmap -p 11211 xx.xxx.xxx.xx"? (obviously you'd need nmap for this, but you get what I'm trying to imply) -- Joey "JoeLinux"

Pointing to Memcached on Remote Server

Hi all - I am stuck on this one. Caching with memcached works when I reference the local box holding Django. But when I point my setting to a remote box it does not cache: This is with Django 1.3 using python-memcached on the localbox in a virtualenv 'default': { 'BACKEND':