Memory and disk usage show 0
andreimarcu opened this issue · 14 comments
On 03/31/2014 02:05 PM, Andrei Marcu wrote:
image
https://cloud.githubusercontent.com/assets/4650950/2572783/18a5d920-b918-11e3-894e-a5e69cea6d7c.pngNot entirely sure why or how. At least the units are right.
—
Reply to this email directly or view it on GitHub
#9.I see this on my work system but not my home system, so looks like
something in the environment perhaps?. Let me know if I can do anything
to help debug.
What linux dist and python version are you running when you get this result?
Ubuntu Server 12.04 (64-bit) and python2.7
32 or 64 bit?
64-bit
On 03/31/2014 10:43 PM, Joakim Hamrén wrote:
What linux dist and python version are you running when you get this
result?—
Reply to this email directly or view it on GitHub
#9 (comment).For me:
work system (where I see the issue) - the final Linux 3.14 rc, Python 2.7.3.
home system (where all is fine) - Linux 3.5.3, Python 2.7.3.
On 03/31/2014 10:43 PM, Joakim Hamrén wrote:
What linux dist and python version are you running when you get this
result?—
Reply to this email directly or view it on GitHub
#9 (comment).Add to last: in both cases 64 bit.
Do you get this only on the overview page or on the specific subpages as well (like /disks)?
I couldn't reproduce it on a ubuntu 12.04 64 bit vm (python 2.7.3).
Try doing this on your system:
>>> import psutil
>>> psutil.virtual_memory()
vmem(total=248832000L, available=132767744L, percent=46.6, used=245284864L, free=3547136L, active=95465472, inactive=96030720, buffers=24330240L, cached=104890368)
>>>
psutil works correctly on my end
vmem(total=25241628672L, available=15559065600L, percent=38.4, used=24215044096L, free=1026584576L, active=8299745280, inactive=8832221184, buffers=414846976L, cached=14117634048)
Fine here too. Work system (where I see the issue):
vmem(total=8285351936L, available=5278818304L, percent=36.3, used=6089396224L, free=2195955712L, active=2620768256, inactive=1339269120, buffers=1156362240L, cached=1926500352)
That's good. same issue on /disks?
I believe its a issue with Jinja's broken filesizeformat
pallets/jinja#59
Indeed, looks like it. Great catch, thanks!