Performance data & other issues

[Steve Dickey]

All:

I am new to the list and hoping to get some help with a new installation.
I have just setup and configured nagios and have a couple dozen hosts that
have been monitored for about 48 hours.  I have a couple of issues that I am
hoping someone can help me with:

1. None of the hosts show any uptime when I go to look at the availability
and trend reports.  All time is shown as Indeterminate???  What am I missing
here?

2. I have been unable to find the check process command that will allow for
the nagios interface to correcly check the active process and also to
restart it from the interface.  I have been doing a "service nagios restart"
after I make changes.

3.  This is a Nagat question:  I keep getting a Hostgroup of "Array" when I
try to edit any of the hosts.  This appears to be a bug but it seems that it
would be prevalent in LOTS of installations and fixed so I am convinced I
have done something wrong but can not figure it out.  Anyone have any ideas
about this?

4. Any suggestions for way to manage hosts & services other than Nagat?

Thanks in advance.

scd
----- Original Message ----- 
From: "Cal Evans" <cal at calevans.com>
To: <skip at pobox.com>
Cc: <nagios-users at lists.sourceforge.net>
Sent: Saturday, September 06, 2003 6:01 PM
Subject: Re: [Nagios-users] check_mailq changes for exim?


> Skip Montanaro wrote:
>
> >     >> Before I exercise my feeble Perl skills, does anyone have mods
for
> >     >> the check_mailq plugin which will check exim's mail queue?
> >
> >     Cal> I actually wrote one, in bash, got completely finished with it
and
> >     Cal> began testing before I remembered that you have to be an root
to
> >     Cal> execute exim -bp? I'm not really keen on making nagios an admin
for
> >     Cal> my mail server so I'm currently in 'thinking' mode on this one.
> >
> >     Cal> I'm open to suggestions though.
> >
> > I did a little reading of the exim spec.txt file today and saw that
there's
> > an option (queue_list_requires_admin) which, when set false, allows mere
> > mortals to list the mail queue.  I'm not an exim user, just trying to
> > monitor a system that runs it, so take this suggestion with a grain of
> > salt.  I doubt there'd be a huge security hole opened up as a result,
but
> > the restriction is probably there for a reason.
> >
> > Skip
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> Yes, this did the trick.  Now my check_exim_queue.sh works like a charm.
>   I'm still a little wary of the security ramifications of this but for
> now it seems to be ok.
>
> Thanks for the heads up.
>
> =C=
>
> -- 
> * Cal Evans
> * http://www.eicc.com
> * We take care of your IT,
> * So you can take care of your business.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null