timloo / memcached

Automatically exported from code.google.com/p/memcached
0 stars 0 forks source link

mcm_server_stats():3022: unknown stat variable: libevent #305

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.build libmemcache-1.4.0.rc2,memcached-1.4.15,libevent-2.0.21-stable
2.in a cpp file,use function struct memcache_server_stats   *mcm_stats(struct 
memcache_ctxt *ctxt, struct memcache *mc); to get server's stat
3.the program output "[WARN@1357390301.515636] mcm_server_stats():3022: unknown 
stat variable: libevent". i print the result curr_items,total_items all of them 
were zore which are wrong result.

What is the expected output? What do you see instead?
telnet to the memcached and print stats. both of curr_items and total_items are 
not zore

What version of the product are you using? On what operating system?
Red Hat Enterprise Linux Server release 5.7 (Tikanga) 

Please provide any additional information below.

Original issue reported on code.google.com by gab...@126.com on 5 Jan 2013 at 1:07

GoogleCodeExporter commented 9 years ago
What is zore? Do you mean zero?

You should file a bug with the libmemcache launchpad (or ask for help on their 
mailing list). This issue doesn't affect the memcached daemon.

Original comment by dorma...@rydia.net on 5 Jan 2013 at 7:16

GoogleCodeExporter commented 9 years ago
i am sorry that i Misspelled the letter zero.
when I try to use  mc_server_stats to get the server’s stat. the process 
encounter segment error.
the same Situation occure when i try to get the server’s stat by 
apr_memcache-0.7.0's function apr_memcache_stats

Original comment by gab...@126.com on 6 Jan 2013 at 3:05

GoogleCodeExporter commented 9 years ago
I don't know what to tell you. You said via telnet the values were fine. This 
isn't the project for libmemcached or apr_memcache. try asking them?

Original comment by dorma...@rydia.net on 6 Jan 2013 at 3:43

GoogleCodeExporter commented 9 years ago
okay,thank you for your ansewer

Original comment by gab...@126.com on 6 Jan 2013 at 4:58