Resources for “A System Monitoring Dashboard”
Listings for this Article: ftp.linuxjournal.com/pub/lj/listings/issue137/8216.tgz
GNU wget: www.gnu.org/software/wget/wget.html
Bash Reference Manual: www.gnu.org/software/bash/manual/bashref.html
SMTP.pm: search.cpan.org/~gbarr/libnet-1.19/Net/SMTP.pm
“How to Send Email with Perl's Net::SMTP”: perl.about.com/b/a/007039.htm
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Designing Electronics with Linux
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Kernel Problem
4 hours 48 min ago - BASH script to log IPs on public web server
9 hours 15 min ago - DynDNS
12 hours 51 min ago - Reply to comment | Linux Journal
13 hours 23 min ago - All the articles you talked
15 hours 47 min ago - All the articles you talked
15 hours 50 min ago - All the articles you talked
15 hours 51 min ago - myip
20 hours 16 min ago - Keeping track of IP address
22 hours 7 min ago - Roll your own dynamic dns
1 day 3 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




Comments
scripts could be improved, tested more thoroughly
I read the article and looked forward to trying out the scripts. It seemed like just what we need. Some very good ideas in here but the scripts should probably be tested on a more common distro and checked for compliance with FHS.
I spent a few minutes to try testing the scripts and soon decided it was not worth the effort. Please let us know if the scripts have been fixed.
First... have the scripts gone through a unix2dos filter?? Why?
For example:
debian@:~/test$ ./monitor_web.sh
: bad interpreter: No such file or directory
debian@:~/test$ hexdump -C monitor_web.sh |head -n 1
00000000 23 21 2f 62 69 6e 2f 62 61 73 68 0d 0a 23 0d 0a |#!/bin/bash..#..|
Note the "0d 0a" AKA CR-LF which confused the bash shell interpreter.
After using unix2dos to remove these... I noticed some necessary editing to do in the monitor_disk.sh script:
GREP="/sbin/grep"
MOUNT="/sbin/mount"
AWK="/usr/bin/awk"
... why bother.... normally these are in the path... if it is really necessary to put the commands in variables... why not make it easy for readers and use locations that will just work. or even better, use "which" to set your variables. grep and mount are usually not in /sbin.
After this, I noticed that one script requires ksh. Not a big deal but, not mentioned in the article.
Thanks for the ideas though. I may consider writing a simple ssh based monitoring system.
In defence of the author:
In defence of the author: ("these things are usually on the path...")
These are intended to be run by cron, where the normal user path may not be available. It is customary to supply an explicit path in such cases (which will, naturally, vary with the system).
RE: scripts could be improved, tested more thoroughly
Hi. Thanks for the feedback! That's the whole point of Open Source, full disclosure of code, and making it better!
As the author of the scripts they are presented as a soluton, not a product. The goal, of course, is to please as many customers as possible, and that's not always possible.
I will report great success at my company so far, which is why I wrote the article! Here' an external link for the the latest updates to these scripts:
http://monitorsuite.sourceforge.net
I personally support these in my spare time. Don't hesitate to contact me at my current email address, I welcome all feedback!
Regards,
-John
Agreed.
I, too, downloaded the scripts as they looked like a great starting point for monitoring my systems, and, sadly, I have to agree with the poster before me that these scripts are replete with bugs. Even the way they were archived is broken. It appears the author made a big no-no: he made 'innocuous' last-minute changes which he did not test, perhaps to meet the LJ deadline, and ended up submitting very broken scripts.
In addition to the problems the poster above mentions, such basic things as forgetting to put a hash mark before a comment, and not putting a space between flags are found in at least the monitor_web.sh script. I've not tested the others yet.
Author: please do fix these problems and re-post.