Yes the default port is 11211 but i override it in my php code to 11234 and i 
do habe the memcached server running at port 11234. So that is not the problem 
atall


On Jul 11, 2010, at 2:08 PM, James Phillips <[email protected]> 
wrote:

> Port is 11211 not 11234
> 
> 
> 
> On Jul 11, 2010, at 1:49 PM, Snehal Shinde <[email protected]> wrote:
> 
>> In my PHP code I am using the correct port number as shown below:
>> 
>> $mResult = $this->cache->connect($my_ip,"11234");
>>                      if($mResult===false) {
>>                              $this->error = "Could NOT connect to memcache 
>> server";
>>                              error_log($this->error);
>>                      }
>> 
>> 
>> On Sun, Jul 11, 2010 at 12:44 PM, a. <[email protected]> wrote:
>> If you telnet to port 12345 (as you mentioned in your first mail), then 
>> maybe you should change the 11211 (which is the default port for memcached) 
>> in your php.ini?
>> 
>> 
>> a.
>> 
>> 
>> On Jul 11, 2010, at 9:32 PM, Snehal Shinde wrote:
>> 
>>> These are my PHP Memcache settings
>>> 
>>> [r...@app1 ~]# php -i | grep memcache
>>> PHP Warning:  Unknown: It is not safe to rely on the system's timezone 
>>> settings. You are *required* to use the date.timezone setting or the 
>>> date_default_timezone_set() function. In case you used any of those methods 
>>> and you are still getting this warning, you most likely misspelled the 
>>> timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in 
>>> Unknown on line 0
>>> memcache
>>> memcache support => enabled
>>> memcache.allow_failover => 1 => 1
>>> memcache.chunk_size => 8192 => 8192
>>> memcache.default_port => 11211 => 11211
>>> memcache.default_timeout_ms => 1000 => 1000
>>> memcache.hash_function => crc32 => crc32
>>> memcache.hash_strategy => standard => standard
>>> memcache.max_failover_attempts => 20 => 20
>>> 
>>> Snehal
>>> 
>>> On Sun, Jul 11, 2010 at 12:31 PM, Snehal Shinde <[email protected]> wrote:
>>> When users access the site, to get data it tries to connect to memcache. I 
>>> check if I am getting an error value back while connecting. That is when I 
>>> get this error message. However, as soon as I get this error, I immediately 
>>> go and check if the process is up and everytime its up and working fine.
>>> 
>>> Is this a problem with memcache. default_timeout_ms ? its set to 1000 by 
>>> default. do I need to bump it up? if so, how to do that? I have iptables 
>>> turned off on the server that is running memcached server. Also its a 
>>> persistent memcache by default. I think what might be happening is that 
>>> though the memcached server is up and running at times the servers are not 
>>> able to connect, maybe cause it timesout before it gets data back?
>>> 
>>> Any help or pointers would be highly appreciated
>>> 
>>> Snehal
>>> 
>>> 
>>> On Sun, Jul 11, 2010 at 12:17 PM, Dustin <[email protected]> wrote:
>>> 
>>> On Jul 11, 9:40 am, snehal <[email protected]> wrote:
>>> 
>>> > Can someone please tell me why do i STILL keep getting the COULD NOT
>>> > CONNECT to the server ERROR? Would really really appreciate a quick
>>> > response.
>>> 
>>>  What is producing that error?
>>> 
>>> 
>> 
>> 

Reply via email to