Monitoring /tmp usage
list Rob Munsch
Okay, so DISK is not impressed with me and just monitoring the physical disk. I am running a client on a remote VPS, and would like to keep an eye on its /tmp, but not sure how or where to define that. Or if? Any tips appreciated. [df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev) Rob Munsch IT Administrator PhillyCarShare XXX-XXX-XXXX x131 www.phillycarshare.org Our Vision: A Philadelphia in which non-profit car sharing exceeds the convenience, flexibility, and affordability of car ownership.
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV).
▸
On 01/19/2011 03:38 PM, Rob Munsch wrote:Okay, so DISK is not impressed with me and just monitoring the physical disk. I am running a client on a remote VPS, and would like to keep an eye on its /tmp, but not sure how or where to define that. Or if? Any tips appreciated. [df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev) **Rob Munsch** IT Administrator Philly**Car**Share XXX-XXX-XXXX x131
www.phillycarshare.org <http://www.phillycarshare.org>;
▸
Our Vision: A Philadelphia in which non-profit car sharing exceeds the
convenience, flexibility, and affordability of car ownership.
- -- - ---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk03UeQACgkQmb+gadEcsb4aggCeLhcc9/QHS2EVOWQiThZibJXz KGEAnj8H+MJif0lHrYaakR8zI0JaUGlN =R3PO -----END PGP SIGNATURE-----
list Rob Munsch
Yeah - In client data, df doesn't even show it. At the command line, tho, a plain "df" *does* show it - as Filesystem "none." I am assuming Xymon is quietly, and normally quite correctly, ignoring any output that doesn't show an actual physical file system. Has anyone tried monitoring any kind of RAMdisk before..?
▸
-----Original Message----- From: Ryan Novosielski [mailto:user-ae4522577e16@xymon.invalid] Sent: Wednesday, January 19, 2011 4:05 PM To: xymon at xymon.com Subject: Re: [xymon] Monitoring /tmp usage -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV). On 01/19/2011 03:38 PM, Rob Munsch wrote:Okay, so DISK is not impressed with me and just monitoring the physical disk. I am running a client on a remote VPS, and would like to keep an eye on its /tmp, but not sure how or where to define that. Or if? Any tips appreciated. [df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev) **Rob Munsch** IT Administrator Philly**Car**Share XXX-XXX-XXXX x131 www.phillycarshare.org <http://www.phillycarshare.org>; Our Vision: A Philadelphia in which non-profit car sharing exceeds the convenience, flexibility, and affordability of car ownership.- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk03UeQACgkQmb+gadEcsb4aggCeLhcc9/QHS2EVOWQiThZibJXz KGEAnj8H+MJif0lHrYaakR8zI0JaUGlN =R3PO -----END PGP SIGNATURE-----
list Ryan Novosielski
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You might want to see if there's anything (like the DFCMD variable for example) that can be leveraged to fix this. Not sure where the filtering comes into play or if there's a way to loosen it without going to source. I know that it does work for ZFS though... Wouldn't the monitoring done by the "memory" test suffice for this specific purpose?
▸
On 01/19/2011 04:25 PM, Rob Munsch wrote:Yeah - In client data, df doesn't even show it. At the command line, tho, a plain "df" *does* show it - as Filesystem "none." I am assuming Xymon is quietly, and normally quite correctly, ignoring any output that doesn't show an actual physical file system. Has anyone tried monitoring any kind of RAMdisk before..?-----Original Message----- From: Ryan Novosielski [mailto:user-ae4522577e16@xymon.invalid] Sent: Wednesday, January 19, 2011 4:05 PM To: xymon at xymon.com Subject: Re: [xymon] Monitoring /tmp usageIt is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV). On 01/19/2011 03:38 PM, Rob Munsch wrote:Okay, so DISK is not impressed with me and just monitoring the physical disk. I am running a client on a remote VPS, and would like to keep an eye on its /tmp, but not sure how or where to define that. Or if? Any tips appreciated. [df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev) **Rob Munsch** IT Administrator Philly**Car**Share XXX-XXX-XXXX x131 www.phillycarshare.org <http://www.phillycarshare.org>; Our Vision: A Philadelphia in which non-profit car sharing exceeds the convenience, flexibility, and affordability of car ownership.
- -- - ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk03WkEACgkQmb+gadEcsb5uBwCdHEBxkuJTVbh/rCTBKSOs9tot
2jMAoKepobWUlHuDPS88ahszmPQfmT3W
=cADV
-----END PGP SIGNATURE-----
list Henrik Størner
▸
In <user-1049a8574fab@xymon.invalid> Ryan Novosielski <user-ae4522577e16@xymon.invalid> writes:
On 01/19/2011 03:38 PM, Rob Munsch wrote:[df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev)It is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV).
Precisely. The "df" data does not have info about /tmp, so you need to look at the Xymon client script running on the server to have it report data for non-physical filesystems. Look at the ~xymon/client/bin/xymonclient-OSNAME.sh script (or "hobbit" ditto). By default, non-physical filesystems are excluded. Regards, Henrik
list Rob Munsch
Ah gotcha. Silly as it is, to include tmpfs but leave the rest of the EXCLUDE intact, I take the current
cat /proc/filesystems | grep nodev | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'
and turn it into
cat /proc/filesystems | grep nodev | grep -v tmpfs | awk '{print $2}' | xargs echo | sed -e 's! ! -x !g'
and I seem to get the result I want. Thanks all :)
▸
-----Original Message----- From: Henrik "Størner [mailto:user-ce4a2c883f75@xymon.invalid] Sent: Thursday, January 20, 2011 7:23 AM To: xymon at xymon.com Subject: Re: [xymon] Monitoring /tmp usage In <user-1049a8574fab@xymon.invalid> Ryan Novosielski <user-ae4522577e16@xymon.invalid> writes:On 01/19/2011 03:38 PM, Rob Munsch wrote:[df] Filesystem 1024-blocks Used Available Capacity Mounted on /dev/hdv1 3768053780 1050316584 2717737196 28% / [mount] /dev/hdv1 on / type ufs (defaults) none on /proc type proc (defaults) none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev)It is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV).Precisely. The "df" data does not have info about /tmp, so you need to look at the Xymon client script running on the server to have it report data for non-physical filesystems. Look at the ~xymon/client/bin/xymonclient-OSNAME.sh script (or "hobbit" ditto). By default, non-physical filesystems are excluded. Regards, Henrik