finding the cause and setting an alert would certainly help anticipate.
This data is collected each minute automatically, at a cost of less than
.1% of one ifl per server, at process and system level.  There are more
metrics, this is a sample


Report: ESALNXP      LINUX      Velocity Software Corporate ZMAP 4.2.0 02/
Monitor initialized: 02/27/     First record analyzed: 02/27/15 19:00:00
----------------------------------------------------------------------------
node/     <-Process Ident-> <---------------Storage Metrics (MB)---------->
 Name     ID    PPID   GRP   Size RSS Peak Swap Data Stk EXEC Lib Lck PTbl
--------- ----- ----- ----- ---- ---- ---- ---- ---- ---- ---- --- --- ----

02/27/15
19:01:00
oracle        0     0     0 7375  980 7212    0  174  4.9 1839 478   0 8.98
 init         1     1     0    1    0  0.8    0 0.14  0.1 0.6   0   0 0.01
 perl      2140     1  2140    9    6  9.0    0 4.06  0.1 1.4 2.2   0 0.03
 snmpd    22809     1 22808   35    9 34.7    0 3.50  0.1 0.0  29   0 0.05


and at system level:
Report: ESALNXR      LINUX RAM/Storage Analysis Report
Velocity Sof
Monitor initialized: 02/27/15 at 19:00:00 on 2828 serial 314C7     First
record
-------------------------------------------------------------------------------

Node/    <--------Memory in megabytes-------------> <-Kernel(MB)->
<-Buffers(MB
<---Cache----><---Anonymous---> Stack<-Slab-->
Time     Total Free Size Actv Swap Total Actv Inact Size Size SRec Size
Dirty B
-------- ----- ---- ---- ---- ---- ----- ---- ----- ---- ---- ---- ----
----- -
02/27/15
19:01:00
oracle   994.8 13.7  550    0  0.8 115.6    0     0    0 38.4    0
251   0.2
-------------------------------------------------------------------------------

19:02:00
oracle   994.8 13.7  550    0  0.8 115.6    0     0    0 38.3    0
251   0.0



On 7/9/2015 9:31 AM, Michael MacIsaac wrote:
Barton,

It reports on the /proc/buddyinfo values and anticipates vmcp failing?

On Thu, Jul 9, 2015 at 12:26 PM, Barton Robinson <
[email protected]> wrote:

And a good performance monitor would already have this reported - down
to the process level.


On 7/9/2015 9:06 AM, Michael MacIsaac wrote:

Let me answer my own question.  Perhaps kludgy, but by adding 'tee' to
sudo, this technique works:

root@lab141:~ # visudo
root@lab141:~ # tail -1 /etc/sudoers
%zoom ALL=NOPASSWD:/usr/bin/tee
root@lab141:~ # su - mike
mike@lab141:~ # free -m
               total       used       free     shared    buffers     cached
Mem:           491        473         18          0        111        170
-/+ buffers/cache:        190        300
Swap:          512          0        511
mike@lab141:~ # echo 3 | sudo /usr/bin/tee /proc/sys/vm/drop_caches >
/dev/null
mike@lab141:~ # free -m
               total       used       free     shared    buffers     cached
Mem:           491        103        388          0          1         12
-/+ buffers/cache:         89        401
Swap:          512          0        511



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to