No available statistics for this bin
catch - January 14, 2009 - 10:57
| Project: | Memcache API and Integration |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
I've had memcache up and running for a while, with a separate bin for most cache tables. Recently I noticed that all but 'default' and 'filter' have the message 'no available statistics for this bin'. Couldn't see a similar report anywhere so opening one up. It's not yet clear if this is a problem with my memcache instances or just the reporting, but any pointers as to where to look would be appreciated.
#1
Forgot about the footer reporting stats - as far as I can see the bins are being used properly, so it may just be the reporting.
#2
Just confirming I'm getting the same thing, so it could be a bug. I just installed memcache for the first time, and though everything seems to check out (see the second half), and memcache seems to be otherwise functional, I'm getting the same on the reporting page, "No available statistics for this bin". In my case the lack of even a slight change in performance leads me to believe it's not just the reporting, but that (in my case) it's just not working. I'm going to try out cache router tonight as well just to see if it produces different results, which might then help confirm if memcache module is working or not. I'll be happy to run any tests to help troubleshoot this issue, or otherwise help in any way needed.
#3
See also http://livebookmark.net/journal/2008/05/21/memcachephp-stats-like-apcphp/ for nice graphical stats of your memcache.
#4
Worked this out.
In my init script for memcache, I had a line
-m 312-d(note the missing space) which meant all daemons after that line weren't being started.While this was a stupid typo, it might be better to say "this daemon is not running" or something similar. Also I'm not clear in that case whether it falls back on the default bin, or simply bypasses the cache completely - I think it's the latter having compared with and without memcache-db.inc - and if that's the case would be good to flag a warning up somewhere more prominently.
While the error was mine, I think the message could be a bit more descriptive, so leaving active.
#5
I'm also getting the same problem, though MemCache itself is running fine and all my instances are happily running and filling up memory. I'm experiencing this on the 5.x version.
#6
On my local OS X 10.5.6 system, I am able to get default, slabs, items, and sizes but not able to get reset, malloc and maps.
The stats are requested in the dmemcache_stats() function in dmemcache.inc by a call to Memcache::getExtendedStats($type).
#7
Is there anything to do to access the stats, does it mean we should not use the "default" bin to see stats??
thanks!
#8
subscribing
#9
This appears to be working for me now. Turns out that we were on a 3.x version of the PECL Memcache so the solution was to downgrade to 2.2.5 and flush the cache. We're getting more hits than misses now. The only one that is off is the filter which has almost no hits...still working on that one.
#11
Coming from #383978: No available statistics for this bin, same issue, subscribing.