Fedora 8 Problem 🔗 link

On 6/8/10, Neil Franken <user-1689acfc5a3b@xymon.invalid> wrote:

Hi All

I got a old Fedora 8 box that I installed the xymon client on. I used
the RHEL packages provided by Buchan Milne(thanks for the local mirror)
and installed the xymon client using yum install xymon-client. However
when I run the runclient.sh I don't get any results I looked into the
/logs directory and found the following error.

Could not connect to bbd at 127.0.0.1:1984 - Connection refused

The install did not ask me for a BBhost file so I think the install
might have skipped this part. How do I change where the client is
reporting to? I looked at all the files in the client/etc directory but
could not find anything.

Regards
Neil

-- 

-----Original Message-----
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid] 
Sent: 08 June 2010 09:08 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Fedora 8 Problem

Try compiling it?

On 6/8/10, Neil Franken <user-1689acfc5a3b@xymon.invalid> wrote:

Hi All

I got a old Fedora 8 box that I installed the xymon client on. I used
the RHEL packages provided by Buchan Milne(thanks for the local
mirror)
and installed the xymon client using yum install xymon-client. However
when I run the runclient.sh I don't get any results I looked into the
/logs directory and found the following error.

Could not connect to bbd at 127.0.0.1:1984 - Connection refused

The install did not ask me for a BBhost file so I think the install
might have skipped this part. How do I change where the client is
reporting to? I looked at all the files in the client/etc directory
but
could not find anything.

Regards
Neil

-- 
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to
continue that counts."
--- Winston Churchill

Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

“Success is not final, failure is not fatal: it is the courage to
continue that counts.”
--- Winston Churchill

<user-1689acfc5a3b@xymon.invalid> wrote:

Is that the only way? There is no configuration file for this? Sorry
about the basic questions sometimes I just like to know as much as
possible.

Regards
Neil

-----Original Message-----
From: Josh Luthman [mailto:user-4c45a83f15cb@xymon.invalid]
Sent: 08 June 2010 09:08 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Fedora 8 Problem

Try compiling it?

On 6/8/10, Neil Franken <user-1689acfc5a3b@xymon.invalid> wrote:

Hi All

I got a old Fedora 8 box that I installed the xymon client on. I used
the RHEL packages provided by Buchan Milne(thanks for the local
mirror)
and installed the xymon client using yum install xymon-client. However
when I run the runclient.sh I don't get any results I looked into the
/logs directory and found the following error.

Could not connect to bbd at 127.0.0.1:1984 - Connection refused

The install did not ask me for a BBhost file so I think the install
might have skipped this part. How do I change where the client is
reporting to? I looked at all the files in the client/etc directory
but
could not find anything.

Regards
Neil

--
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX

"Success is not final, failure is not fatal: it is the courage to
continue that counts."
--- Winston Churchill

Hi All

I got a old Fedora 8 box that I installed the xymon client on. I used
the RHEL packages provided by Buchan Milne(thanks for the local mirror)
and installed the xymon client using yum install xymon-client. However
when I run the runclient.sh I don't get any results I looked into the
/logs directory and found the following error.

Could not connect to bbd at 127.0.0.1:1984 - Connection refused

The install did not ask me for a BBhost file so I think the install
might have skipped this part. How do I change where the client is
reporting to? I looked at all the files in the client/etc directory but
could not find anything. 
  

-----Original Message-----
From: David Baldwin [mailto:user-cbbf693f2c89@xymon.invalid] 
Sent: 08 June 2010 09:57 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Fedora 8 Problem

Neil,

Hi All

I got a old Fedora 8 box that I installed the xymon client on. I used
the RHEL packages provided by Buchan Milne(thanks for the local mirror)
and installed the xymon client using yum install xymon-client. However
when I run the runclient.sh I don't get any results I looked into the
/logs directory and found the following error.

Could not connect to bbd at 127.0.0.1:1984 - Connection refused

The install did not ask me for a BBhost file so I think the install
might have skipped this part. How do I change where the client is
reporting to? I looked at all the files in the client/etc directory but
could not find anything. 
  

You are probably looking for /etc/default/hobbit-client to configure the
address of the server.

If that's not it, go from first principles - either check what is in
/etc/init.d/hobbit-client (or xymon-client) or list the installed files.
On my system I get:
# rpm -ql hobbit-client
/etc/default/hobbit-client
/etc/init.d/hobbit-client
/usr/lib/hobbit/client
/usr/lib/hobbit/client/bin
/usr/lib/hobbit/client/bin/bb
/usr/lib/hobbit/client/bin/bbcmd
/usr/lib/hobbit/client/bin/bbdigest
/usr/lib/hobbit/client/bin/bbhostgrep
/usr/lib/hobbit/client/bin/bbhostshow
/usr/lib/hobbit/client/bin/clientupdate
/usr/lib/hobbit/client/bin/hobbitclient-aix.sh
/usr/lib/hobbit/client/bin/hobbitclient-darwin.sh
/usr/lib/hobbit/client/bin/hobbitclient-freebsd.sh
/usr/lib/hobbit/client/bin/hobbitclient-hp-ux.sh
/usr/lib/hobbit/client/bin/hobbitclient-irix.sh
/usr/lib/hobbit/client/bin/hobbitclient-linux.sh
/usr/lib/hobbit/client/bin/hobbitclient-netbsd.sh
/usr/lib/hobbit/client/bin/hobbitclient-openbsd.sh
/usr/lib/hobbit/client/bin/hobbitclient-osf1.sh
/usr/lib/hobbit/client/bin/hobbitclient-sco_sv.sh
/usr/lib/hobbit/client/bin/hobbitclient-sunos.sh
/usr/lib/hobbit/client/bin/hobbitclient.sh
/usr/lib/hobbit/client/bin/hobbitlaunch
/usr/lib/hobbit/client/bin/logfetch
/usr/lib/hobbit/client/bin/msgcache
/usr/lib/hobbit/client/bin/orcahobbit
/usr/lib/hobbit/client/etc
/usr/lib/hobbit/client/etc/clientlaunch.cfg
/usr/lib/hobbit/client/etc/hobbitclient.cfg
/usr/lib/hobbit/client/etc/localclient.cfg
/usr/lib/hobbit/client/ext
/usr/lib/hobbit/client/logs
/usr/lib/hobbit/client/runclient.sh
/usr/lib/hobbit/client/tmp
/usr/share/doc/hobbit-client-4.2.3
/usr/share/doc/hobbit-client-4.2.3/COPYING
/usr/share/doc/hobbit-client-4.2.3/CREDITS
/usr/share/doc/hobbit-client-4.2.3/Changes
/usr/share/doc/hobbit-client-4.2.3/README
/usr/share/doc/hobbit-client-4.2.3/README.CLIENT
/usr/share/doc/hobbit-client-4.2.3/RELEASENOTES
/var/log/hobbit

David.

-- 
David Baldwin - IT Unit
Australian Sports Commission          www.ausport.gov.au
Tel 02 62147830 Fax 02 62141830       PO Box 176 Belconnen ACT 2616
user-cbbf693f2c89@xymon.invalid          Leverrier Street Bruce ACT 2617


Keep up to date with what's happening in Australian sport visit http://www.ausport.gov.au

This message is intended for the addressee named and may contain confidential and privileged information. If you are not the intended recipient please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you receive this message in error, please delete it and notify the sender.

On Wednesday, 9 June 2010 00:24:27 user-1ccd046c8510@xymon.invalid wrote:

As I use perl mostly for interfacing to hobbit for tests, reports etc I
have quite a number of perl modules floating around.

Given that CPAN is the easiest way to upload, install manage etc, I have
installed the modules there.

I have created a top level Module called Xymon which is simple a place
holder.

So far I have uploaded Xymon::Client which provides a perl interface to
sending status updates:

#!/usr/bin/perl

use Xymon::Client;

my $xymon = Xymon::Client->new(.......);

$xymon->send(.....);

Documentation for this is included on cpan and when you install the
module.

The other module I have installed is Xymon::Monitor::Informix which tests
connectivity to remote Informix Databases
This updates a test called database for servers that run informix
databases and lists the status of each database on the status screen.

I have quite a few more to add but I was hoping that anyone else that has
perl scripts, May add them there as modules. If help is required
I can assist.

Some of the upcoming releases of modules include:
        Xymon::Server which provides an interface to the various server
environment variables + some utility functions such as redrawing the
screen.

        Xymon::Server::History which returns a hash of all events for all
or selected servers - I currently use this for generating excel reports.
        Xymon::Server::Clients which provides an interface to the
hobbitclient.cfg file and includes a web interface.
        Xymon::Server::Alerts which provides an interface
hobbit-alerts.cfg

        Xymon::Monitor::MSSQL which provides a status test for sql server
databases
        Xymon::Monitor::Oracle which provides a status test for oracle
servers
        Xymon::Monitor::SunContainer which provides a way fo testing
Containers running on a Solaris node.

There are a few others that I have but that is enough for now.

BTW we still use a database to store all information about our servers and
routers and then use this to generate the bbhosts and include files. This
includes
a screen under INFO for a host that provides this information within
hobbit. 

Allows us to do advanced searching based on other parameters,
using an advanced search
web screen within hobbit.

Last time I spoke of the database there seemed to be very little interest
in it so it has stayed where it is and hasn't been used anywhere else.

and use it for a web
based outages application. When an outage is logged, not only does it send
an email
to subscribed users with details of the servers and the applications, it
also automagically disables that host(s) in hobbit for the period of the
outage.

On Wednesday, 9 June 2010 00:24:27 user-1ccd046c8510@xymon.invalid 
wrote:

As I use perl mostly for interfacing to hobbit for tests, reports etc 

I

have quite a number of perl modules floating around.

Given that CPAN is the easiest way to upload, install manage etc, I 
have
installed the modules there.

Well, it's fine for distribution, installation is debatable (I usually use the distro package manager, but my distro has > 2000 CPAN modules).

However, where should the VCS for this be? How about a perl subdirectory 
on 
xymon svn on SF?

I have created a top level Module called Xymon which is simple a place
holder.

So far I have uploaded Xymon::Client which provides a perl interface 
to
sending status updates:

I started on one a few months ago, but no one seemed interested at the 
time. 
The next thing I needed for myself was an interface to parsing bb-hosts 
to a 
page structure.

I've attached what I had.

#!/usr/bin/perl
use Xymon::Client;
my $xymon = Xymon::Client->new(.......);
$xymon->send(.....);
Documentation for this is included on cpan and when you install the
module.
The other module I have installed is Xymon::Monitor::Informix which 
tests
connectivity to remote Informix Databases

This updates a test called database for servers that run informix
databases and lists the status of each database on the status screen.

How does this compared to dbcheck.pl from http://hobbit-perl-
cl.sourceforge.net/ ?

I have quite a few more to add but I was hoping that anyone else that 
has
perl scripts, May add them there as modules. If help is required

I can assist.

Well, I was aiming to port some of mine to my Xymon::Client module.

Some of the upcoming releases of modules include:
        Xymon::Server which provides an interface to the various 
server
environment variables + some utility functions such as redrawing the
screen.

I don't know if it should draw the screen, however if it can parse 
various 
config files and provide structures that can be used to compose a view 
in a 
templating system, that would be better.

For example, to provide an Ajax view, redrawing the screen itself in 
perl is 
useless, but providing the structure in JSON is useful ....

        Xymon::Server::History which returns a hash of all events for 
all
or selected servers - I currently use this for generating excel 
reports.
        Xymon::Server::Clients which provides an interface to the
hobbitclient.cfg file and includes a web interface.
        Xymon::Server::Alerts which provides an interface
hobbit-alerts.cfg

        Xymon::Monitor::MSSQL which provides a status test for sql 
server
databases

        Xymon::Monitor::Oracle which provides a status test for oracle
servers
        Xymon::Monitor::SunContainer which provides a way fo testing
Containers running on a Solaris node.

There are a few others that I have but that is enough for now.
BTW we still use a database to store all information about our servers 
and
routers and then use this to generate the bbhosts and include files. 

This

includes
a screen under INFO for a host that provides this information within
hobbit. 

Well, in devmon, I have some work in my local checkout which populates 
some 
discover-related information into a database (e.g., cdp neighbours, IPs, 

routes).

Allows us to do advanced searching based on other parameters,
using an advanced search
web screen within hobbit.

Last time I spoke of the database there seemed to be very little 
interest
in it so it has stayed where it is and hasn't been used anywhere else.

I think having a database is useful. I think there was resistance to 
having 
all the monitoring depend on a database.

For example, if configuration information is to be in a database, 

dumped out, so that no matter what happens to the database, monitoring 
will 
work.

We have applications tied to servers in the database

Well, service dependency information should be captured, in order to 
easily 
provide a services view. While this can be hacked in at present with the 

combo-test, a better view is required (amongst other issues).

and use it for a web
based outages application. When an outage is logged, not only does it 
send
an email
to subscribed users with details of the servers and the applications, 
it
also automagically disables that host(s) in hobbit for the period of 
the
outage.

Well, this should probably be migrated onto the developer list, and I think we should discuss the goals before finalising requirements/design etc.

This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

Buchan Milne wrote:

On Wednesday, 9 June 2010 00:24:27 user-1ccd046c8510@xymon.invalid wrote:
  

BTW we still use a database to store all information about our servers and
routers and then use this to generate the bbhosts and include files. This
includes
a screen under INFO for a host that provides this information within
hobbit.     

Well, in devmon, I have some work in my local checkout which populates some discover-related information into a database (e.g., cdp neighbours, IPs, routes).

  

Allows us to do advanced searching based on other parameters,
using an advanced search
web screen within hobbit.

Last time I spoke of the database there seemed to be very little interest
in it so it has stayed where it is and hasn't been used anywhere else.
    

I think having a database is useful. I think there was resistance to having all the monitoring depend on a database.
  

Buchan Milne wrote:

On Wednesday, 9 June 2010 00:24:27 user-1ccd046c8510@xymon.invalid 
wrote:

BTW we still use a database to store all information about our 
servers and
routers and then use this to generate the bbhosts and include files. 

This

includes
a screen under INFO for a host that provides this information within
hobbit. >> >

Well, in devmon, I have some work in my local checkout which populates 
some 
discover-related information into a database (e.g., cdp neighbours, 

IPs, 

routes).

Allows us to do advanced searching based on other parameters,
using an advanced search
web screen within hobbit.

Last time I spoke of the database there seemed to be very little 
interest
in it so it has stayed where it is and hasn't been used anywhere 
else.

I think having a database is useful. I think there was resistance to 
having 
all the monitoring depend on a database.
I think that at quite a few sites a database is used to generate the xymon configuration files, thus using a database for monitoring purposes 

is perhaps not an such a big issue. In my case, the use of an additional 

database for monitoring only is not feasible.  There is a database, used 

by many applications, maintained by a lot of people, which I should use for the monitoring application as well. There must be some real benefits 

in order to justify the (partial)  duplication of information and the additional maintenance efforts.

Regards,
  Wim Nelis.

*******************************************************************************************************

The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.

*******************************************************************************************************

This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

user-1ccd046c8510@xymon.invalid wrote:

The problem or tangible benefits are to provide an easier way of handling hosts, laying them out in pages by
categories such as location, application etc. This becomes a real issue when the number of hosts is large.

The other benefit I see is that it makes hobbit look a lot more professional and enterprise ready if multiple users
can change / add / remove hosts without having to rely on an admin with vi to modify the files. Even if the data is coming from
other locations such as an asset database, it is usually easier to write a database to database interface. (I am now ducking in order
to avoid the incoming flames).

We have 20 or more IT staff who add servers and it is all done through the database interface. Commits to hobbit from the database
are made only when one of 3 people go into the database application and verify the changes. This is a trade off between many hands
on the bbhosts file and the other side which require the hobbit admins to have to type everything.

I found that even when we had two or three people editing the bbhosts, that I couldn't trust that someone wouldn;t screw the file up.

We never ever touch the bbhosts file now.

I think maybe a seperate project outside of hobbit is the way to go here. Just create a db application and interface to hobbit
and then people can choose to use it or not. I just know that I am being continually harassed by the helpdesk manager because in his
view the helpdesk application can do all of this (which I know is not true). It is just easy for him at the moment to run down hobbit in front
of the IT Director because he calls it a toy cmpared to apps with db frontends.

"W.J.M. Nelis" <user-f4ccfde53c0d@xymon.invalid> wrote on 10/06/2010 06:19:43 PM:

[image removed]

Re: [hobbit] CPAN Modules

W.J.M. Nelis

to:

user-ae9b8668bcde@xymon.invalid

10/06/2010 06:24 PM

Please respond to hobbit

Buchan Milne wrote:

On Wednesday, 9 June 2010 00:24:27 user-1ccd046c8510@xymon.invalid wrote:

BTW we still use a database to store all information about our servers and
routers and then use this to generate the bbhosts and include files. This
includes
a screen under INFO for a host that provides this information within
hobbit.

Well, in devmon, I have some work in my local checkout which populates some
discover-related information into a database (e.g., cdp neighbours, IPs,
routes).

Allows us to do advanced searching based on other parameters,
using an advanced search
web screen within hobbit.

Last time I spoke of the database there seemed to be very little interest
in it so it has stayed where it is and hasn't been used anywhere else.

I think having a database is useful. I think there was resistance to having
all the monitoring depend on a database.

I think that at quite a few sites a database is used to generate the
xymon configuration files, thus using a database for monitoring purposes
is perhaps not an such a big issue. In my case, the use of an additional
database for monitoring only is not feasible.  There is a database, used
by many applications, maintained by a lot of people, which I should use
for the monitoring application as well. There must be some real benefits
in order to justify the (partial)  duplication of information and the
additional maintenance efforts.

Regards,
  Wim Nelis.

*******************************************************************************************************
The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages.
*******************************************************************************************************