Submitted by rus83 on Tue, 08/20/2013 - 07:41
Performed updates today (as usual):
Webmin to 1.650 Usermin to 1.560 Virtualmin to 4.02.gpl
'Real memory' status and bar have gone/disappeared from the index page on my Debian 6 and 7 OpenVZ containers without vSWAP. The vSWAP containers are unaffected and 'Real Memory' is displayed together with 'Virtual Memory' just fine.
Edit: Running 'Re-Check Virtualmin Configuration' reports: Your system has only 0 bytes of memory, which is below the Virtualmin recommended minimum of 256 MB.
Status:
Closed (fixed)
Comments
Submitted by rus83 on Tue, 08/20/2013 - 07:56 Comment #1
Submitted by Karl on Tue, 08/20/2013 - 10:08 Pro Licensee Comment #2
Here too on Debian 7. I'm getting the same report: "Your system has only 0 bytes of memory ...".
Submitted by JamieCameron on Tue, 08/20/2013 - 12:57 Comment #3
Could you post the output of the
free
command and the contents of/proc/user_beancounters
and/proc/meminfo
on one of the VMs that is having this problem?Submitted by Karl on Tue, 08/20/2013 - 14:02 Pro Licensee Comment #4
free:
total used free shared buffers cached
Mem: 6291456 2416624 3874832 0 0 1457896
-/+ buffers/cache: 958728 5332728
Swap: 0 0 0
/proc/user_beancounters:
Version: 2.5
uid resource held maxheld barrier limit failcnt
32412: kmemsize 67870727 68837376 201326592 209715200 0
lockedpages 0 0 8192 8192 0
privvmpages 475431 476999 1572864 9223372036854775807 0
shmpages 2657 2657 50176 50176 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numproc 160 189 4116 4116 0
physpages 605543 608782 1572864 1572864 0
vmguarpages 0 0 786432 9223372036854775807 0
oomguarpages 224275 224275 851968 9223372036854775807 0
numtcpsock 66 67 4116 4116 0
numflock 149 149 1024 1056 0
numpty 1 1 512 512 0
numsiginfo 0 21 1024 1024 0
tcpsndbuf 2277240 2294680 33554432 50331648 0
tcprcvbuf 1212144 1228528 33554432 50331648 0
othersockbuf 552552 553328 16777216 33554432 0
dgramrcvbuf 0 0 33554432 50331648 0
numothersock 321 321 4116 4116 0
dcachesize 37707103 37715761 36700160 37748736 0
numfile 6049 6095 32768 32768 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
dummy 0 0 9223372036854775807 9223372036854775807 0
numiptent 14 14 1024 1024 0
/proc/meminfo:
MemTotal: 6291456 kB
MemFree: 3869284 kB
Cached: 1458788 kB
Active: 1840720 kB
Inactive: 515168 kB
Active(anon): 749116 kB
Inactive(anon): 147984 kB
Active(file): 1091604 kB
Inactive(file): 367184 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 8 kB
Writeback: 0 kB
AnonPages: 897100 kB
Shmem: 10628 kB
Slab: 66288 kB
SReclaimable: 36828 kB
SUnreclaim: 29460 kB
Submitted by rus83 on Tue, 08/20/2013 - 14:08 Comment #5
Debian 6 OpenVZ container:
root@376516:~# free
total used free shared buffers cached
Mem: 1048800 337752 711048 0 0 0
-/+ buffers/cache: 337752 711048
Swap: 0 0 0
Version: 2.5
uid resource held maxheld barrier limit failcnt
255558: kmemsize 6859238 12995237 204800000 204800000 0
lockedpages 0 438 2048 2048 0
privvmpages 84906 225057 262200 262200 0
shmpages 1072 16088 128000 128000 0
dummy 0 0 0 0 0
numproc 56 117 600 600 0
physpages 20683 139162 0 9223372036854775807 0
vmguarpages 0 0 262200 262200 0
oomguarpages 20683 139162 262200 262200 0
numtcpsock 27 95 4096 4096 0
numflock 10 65 2048 2048 0
numpty 1 2 32 32 0
numsiginfo 0 62 1024 1024 0
tcpsndbuf 479312 1691464 20480000 20480000 0
tcprcvbuf 442368 13073712 20480000 20480000 0
othersockbuf 264600 963000 20480000 20480000 0
dgramrcvbuf 0 33344 10240000 10240000 0
numothersock 150 499 2048 2048 0
dcachesize 582180 1031961 10240000 10240000 0
numfile 2055 4075 50000 50000 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
dummy 0 0 0 0 0
numiptent 24 39 2048 2048 0
MemTotal: 1048800 kB
MemFree: 709600 kB
Buffers: 0 kB
Cached: 0 kB
SwapCached: 0 kB
Active: 0 kB
Inactive: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 1048800 kB
LowFree: 709600 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 780 kB
Writeback: 0 kB
AnonPages: 0 kB
Mapped: 0 kB
Slab: 0 kB
PageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 0 kB
Committed_AS: 0 kB
VmallocTotal: 0 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
Hugepagesize: 2048 kB
Submitted by JamieCameron on Tue, 08/20/2013 - 14:59 Comment #6
Thanks. Could you also post screenshots of what you see on the System Information page?
Make sure you click "Refresh system information" in the top right first, to clear any caches of old data.
Submitted by Karl on Tue, 08/20/2013 - 16:30 Pro Licensee Comment #7
Here's the screenshot. I clicked "Refresh system information" many times.
Submitted by rus83 on Tue, 08/20/2013 - 18:20 Comment #8
I have the same screen on Debian 6 and 7 containers. The VPS has also been rebooted, but I am unable to reboot the host node (CentOS). I have not tested this on CentOS containers yet.
Submitted by JamieCameron on Tue, 08/20/2013 - 19:26 Comment #9
If you go to Webmin -> System -> Running Processes -> Memory , what RAM size and usage does it display above the process list?
Submitted by rus83 on Tue, 08/20/2013 - 19:54 Comment #10
Real memory: 0 bytes total / 759.27 MB free Swap space: 0 bytes total / 0 bytes free
Submitted by rus83 on Tue, 08/20/2013 - 20:06 Comment #11
Jamie, I just deployed a new Debian 7 VPS with vSwap on another server running OpenVZ Web Panel (instead of VePortal), updated Virtualmin and the memory 'disappeared' there as well. If there is a way to pass you the root login privately, I can recycle it after you debug it. You can keep it for testing purposes, I'm a fan of your software.
Submitted by JamieCameron on Tue, 08/20/2013 - 22:06 Comment #12
rus38 - that would be really useful. You can email me the login details at jcameron@virtualmin.com
Submitted by Karl on Wed, 08/21/2013 - 10:50 Pro Licensee Comment #13
Jamie, I have one identical VPS with Debian 7 here where I did not upgrade yet. So you could see "before" and "after". Is that helpful for you?
Submitted by JamieCameron on Wed, 08/21/2013 - 13:32 Comment #14
Ok, I found the cause of this, and have a fix for it - it turns out that it happens if a burstable memory limit is set for the VM, and that limit is the same as the hard memory cap. This will be fixed in the next Webmin release, or you can apply the code change from https://github.com/webmin/webmin/commit/25303ca2c5c6ac2a7b09a0aa07cb8aeb...
Submitted by Karl on Wed, 08/21/2013 - 16:39 Pro Licensee Comment #15
Yes, it works. But I'm wondering about this:
"Real memory" is always showing the burst memory value, not the "guaranteed" memory value. Is the term "hard memory cap" meaning the "guaranteed" memory value?
Thanks.
Submitted by JamieCameron on Wed, 08/21/2013 - 17:25 Comment #16
The next release of the Virtualmin theme package will show the burstable and hard memory limits separately.
Submitted by Karl on Wed, 08/21/2013 - 17:38 Pro Licensee Comment #17
Thanks and best regards. :)
Submitted by Issues on Wed, 09/04/2013 - 19:11 Comment #18
Automatically closed -- issue fixed for 2 weeks with no activity.