2012-02-06 14:06:14.106 INFO net.spy.memcached.MemcachedConnection:
Connection state changed for sun.nio.ch.SelectionKeyImpl@1d439fe
2012-02-06 14:06:14.107 INFO net.spy.memcached.MemcachedConnection:
Reconnecting due to failure to connect to {QA sa=0.0.0.0/0.0.0.0:11211,
#Rops=0, #Wops=0, #iq=0, topRop=null, topWop=null, toWrite=0, interested=0}
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:592)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:313)
at
net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:199)
at net.spy.memcached.MemcachedClient.run(MemcachedClient.java:1622)
On Tue, Feb 7, 2012 at 9:43 AM, Siddharth Jagtiani <
[email protected]> wrote:
> Thanks for your prompt response.
>
> I have modified my memcached load to "/usr/bin/memcached -m 64 -U 11211 -p
> 11211 -u root -l 127.0.0.1"
> Client now uses "super(new InetSocketAddress("127.0.0.1", 11211));"
> On the server I ran ps -ef
> prompt>:~$ sudo ps -ef | grep memcached
> [sudo] password for username:
> username 26614 14126 0 09:34 pts/2 00:00:00 /usr/bin/memcached -m 64
> -U 11211 -p 11211 -u root -l 127.0.0.1
> Also
> prompt$ sudo netstat -anp | grep 11211
> tcp 0 0 127.0.0.1:11211 0.0.0.0:*
> LISTEN 26614/memcached
> tcp 0 0 127.0.0.1:11211 127.0.0.1:56746
> ESTABLISHED 26614/memcached
> tcp6 0 0 127.0.0.1:56746 127.0.0.1:11211
> ESTABLISHED 26625/java
> udp 0 0 127.0.0.1:11211 0.0.0.0:*
> 26614/memcached
>
> I obvious still get the warn message. I know I am missing something really
> basic here.
>
> A flip question : Does this have any side effect ? Performance, CPU util
> or anything else ? If not, is there a log4j setting ?
>
> Thanks again
> Siddharth
>
>
> On Tue, Feb 7, 2012 at 4:36 AM, Dustin <[email protected]> wrote:
>
>> You're trying hard to run it as root. You should not do that.
>>
>> The annoying message is "connection refused." You don't have the server
>> bound to the interface you're trying to connect to. If you are forcing a
>> bind on 127.0.0.1, you should connect to 127.0.0.1.
>>
>
>
