One other note -- can you recompile on each client system? One wonders if
there are some issues with dynamically linked libraries that might be
causing something that compiles okay on machine A to blow up on machine B.
This is something that the RPM, apt, yum, et al might prevent (if the
packages are maintained well), but you might get hosed if you are like me
and just scp a directory to a new client and then fire it up.
GLH
On 9/9/09, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:
Confirmed - PROCS works on the host in which the server is getting client
data from.
I compiled on each client individually (see the last link of my last
post). Exact same commands on each - literally copy/paste short of root
passwords. I will recompile the two failing clients tonight to see what
happens.
I wasn't aware of any client update. Assuming this is not default, but
still, is there a man page detailing this?
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
"When you have eliminated the impossible, that which remains, however
improbable, must be the truth."
--- Sir Arthur Conan Doyle
On Wed, Sep 9, 2009 at 4:07 PM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid>wrote:
Good. So if you tried PROC on "two" you should get something. Something
is deeply wrong on the other two hosts. And Xymon likes to silently ignore
errors.
My **guess** is that something crummy has happened to the failing
clients. Since there is not much to them they should be easy enough to
check out. Might be a good education.
Did you install from RPM, or compile your own copy of the client? Are
you able to reinstall the client piece from a known working source? Are you
using the "client update" piece where the client can fetch a tarball from
the server and install it on its own?
GLH
On 9/9/09, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:
Suggesting that the bbc is capable of labeling tests. The
hobbit-clients' data is staying clear.
two.myhost.com does have data and it is [ps] and
[msgs:/var/log/messages]
one.myhost.com and three.myhost.com has no data on the server.
hobbitclient.log is full of:
2009-09-09 14:38:44 Failed to get a message, terminating
$bb server.fqdn.com ping #this command works
hobbit-4.2.0
This is running a CentOS release 5.2 (Final) and CentOS release 5
(Final) respectively - "Red Hat Linux".
One thread on the archives was able to fix it by installing the Debian
package. Obviously I can't do that. The strange part is I executed the
exact same commands across all three - the same ones I put up here
http://en.wikibooks.org/wiki/System_Monitoring_with_Xymon/Administration_Guide/Compiling_on_CentOS
Perhaps there is a package missing of some sort? Is there a way to get
more detailed logs from the hobbitclient.log?
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
"When you have eliminated the impossible, that which remains, however
improbable, must be the truth."
--- Sir Arthur Conan Doyle
On Wed, Sep 9, 2009 at 3:34 PM, Greg Hubbard <user-435e16ecfd6a@xymon.invalid>wrote:
Then what was this all about? I guess I read it wrong.
*"However on an bbc 1.9i btf (better then free) client it is pushing
PROCs to the server:
#cat ~bbuser/bbc1.9i-btf/etc/bbwarnsetup.cfg:
...
PROCS="bbrun" # (YELLOW) WARN IF NOT RUNNING
PAGEPROC="cron" # (RED) PAGE IF NOT RUNNING
export PROCS PAGEPROC"
• What you might want to do is track down the "raw data" being sent by
these hosts to see if they contain a PROC secion. I think you can get to it
on each host through the
http://<xymon-server>/hobbit-cgi/bb-hostsvc.sh?CLIENT=<client<http://%3cxymon-server%3e/hobbit-cgi/bb-hostsvc.sh?CLIENT=%3Cclient>>;
link. On Solaris you would look for a [ps] header, then a list of
processes. This will show you that the data is getting pumped over. (For
Linux, etc. there might be something different).
And, if your config fragment is correct, you would not expect any PROC
checks for one or two, just for three, since you only defined them for three
and there are no PROC checks in the DEFAULT section.
--
Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3)
my advice is worth at least as much as what you are paying for it, or your
money cheerfully refunded.
--
Disclaimer: 1) all opinions are my own, 2) I may be completely wrong, 3)
my advice is worth at least as much as what you are paying for it, or your
money cheerfully refunded.