run netstat -an in console every time to get connection status and check if it´s running bad or not
2012/6/29 Geoffrey Hoffman <[email protected]> > You're not insane and you're doing everything I would do if I saw the same > thing you're seeing. > > Having said that, I do not have a good explanation for you, either. > > Didn't you say you have Wireshark running? Maybe port scanning/sniffing is > doing something weird? > > Did you build against a particular version of libmemcached ? > > If you happen to have VirtualBox or access to AWS or another server, fire > up a VM and/or run memcached on a separate box, try connecting to [not > 127.0.0.1] and see if you get the same? > > > On Fri, Jun 29, 2012 at 4:30 PM, Aaron Jackson <[email protected]>wrote: > >> I am testing from CLI for now. On the first execution with memcached just >> being restarted, cmd_set is 1 after the set, but running the script after >> this results in cmd_set being incremented in twos. >> >> eg.. >> >> first run - cmd_set = 1 >> second - cmd_set = 3 >> third - cmd_set = 5 >> >> and it literally is just one set operation in a blank file. "php >> test.php" from the terminal. >> >> I did a few tests before and check this out... >> >> <?php >> $s = fsockopen('localhost', 11211); >> fwrite($s, "set key 0 0 5\r\nhello\r\n"); >> fclose($s); >> exit(); >> >> results in memcached saying: >> >> <31 new auto-negotiating client connection >> 31: Client using the ascii protocol >> <31 set key 0 0 5 >> >31 STORED >> <31 connection closed. >> <31 new auto-negotiating client connection >> 31: Client using the ascii protocol >> <31 set key 0 0 5 >> >31 STORED >> <31 connection closed. >> >> Am i going in insane? >> >> Thanks, >> Aaron >> >> > -- Roberto Spadim Spadim Technology / SPAEmpresarial
