Hi all,
After weeks of passing my Mon query around Varian, no was able to
answer my question regarding an OID value to use for monitoring the HAL on a
Unity+ system. There is a Mon monitor called ps.monitor that greps the
remote machines ps -ef output and could be used to see if Acqproc is
running, but it would mean enabling the systat service in inetd.conf which
is generally considered a security no-no. Thus, I still don't have an
answer.
The good news is that I have everything else running pretty well
(ping, telnet, ftp, ssh, httpd, diskspace, and hpnp (printer) monitors
running smoothly sending e-mail and/or pager alerts when something isn't
right). Since several people asked that I post a summary of the setup I'm
using, here it is:
1) RedHat Linux 7.1 installed on an old Pentium 200; server installation,
with Perl 5.6 (must be >= 5.005_01).
2) Install the UCD SNMP (>= 3.6.3) library is available from
ftp://ucd-snmp.ucdavis.edu/ if you didn't when you insstalled RedHat. I
think it installs by default
3) Secured it as well as I know how by disabling ftp, telnet, sendmail, etc.
and installing Tripwire, and SSH.
4) Installed mon-0.38.21 available from: http://www.kernel.org/software/mon/
N.B. In the install file it says:
The "mon" daemon uses Perl 5.n, where n >=
005_01. Older versions of
Perl had problems with Sys::Syslog under Linux, and
had dated versions of
Text::ParseWords. Mon also requires that *.ph be
created from the system
header files. Normally this is done manually during
Perl installation
by these means:
cd /usr/include
h2ph *.h sys/*.h
However, if you're running Linux you may need to run
cd /usr/include
h2ph *.h sys/*.h asm/*.h
If you try to run mon and Perl complains with the
"did you run h2ph?"
message, then chances are this step wasn't done.
I found that I had to run:
h2ph *.h sys/*.h asm/*.h bits/*.h
or some of the Perl modules failed thier tests during the
make/install.
5) Installed fping from:
ftp://ftp.kernel.org/pub/software/admin/mon/fping-2.2b1.tar.gz (a better
way to send out lots of pings).
6) Installed required Perl modules to make everything work (there were a few
more required than were listed in the mon INSTALL file. At least to get all
the monitors I wanted to use, working):
from: http://www.kernel.org/software/mon/
Mon::*
from: http://search.cpan.org (type in the name, search, and
download the .gz file)
Time::Period
Time::HiRes
Convert::BER
Expect
SNMP version 4.2.0
IO::Stty
IO::Tty
Bundle::libnet
Filesys::DiskSpace for diskspace.monitor
Net::Telnet for telnet.monitor
7) Installed QuickPage which is freely available from
http://www.qpage.org
For qpage, the number you use in the configuration file isn't the
pager number, it's your paging company's local "modem number" or "IXO/TAP
number". This is an important distinction. Just call them and ask for it.
8) Found and installed an ssh.monitor at:
http://www.dulug.duke.edu/~skvidal/openssh-fix/ssh.monitor
9) Put the supplied mon and qpage start scripts in /etc/init.d and added
links from rc3.d.
That's the gist of it. Hope I didn't forget anything major. It
took a bit of tinkering and fiddling to get everything to work but now, if
we choose (ie. bring the pager home), we can be on top of things 24/7/365.
John Tomaszewski
NMR Facility Asst. Mgr.
IU, Chemistry Dept.
(812) 855-4478
<<Tomaszewski, John W..vcf>>
Received on Fri Jun 08 2001 - 14:48:22 MST