novell.forge.mrtgext.public
  Home FAQ Contact Sign in
novell.forge.mrtgext.public only
 
Advanced search
February 2007
motuwethfrsasuw
   1234 5
567891011 6
12131415161718 7
19202122232425 8
262728     9
2007
 Jan   Feb   Mar   Apr 
 May   Jun   Jul   Aug 
 Sep   Oct   Nov   Dec 
2007 2006    
total
novell.forge.mrtgext.public Profile…
RELATED GROUPS

POPULAR GROUPS

more...

 Up
  secure transmission and transmission of monitoring info         


Author: hyphen1
Date: Dec 1, 2006 10:03

Hello,

I've setup the MRTGext in a couple test environments. It seems to work
fine. In terms of production environments, I looked through the documents
and there's no mention of the transmission method from server agents to
the collecting monitoring server (using only the supplied perl scripts).
It seems to build in the mrtg.cfg file on the local server then passed
the info somehow to the collecting monitoring server to build the HTML
page.

also there's no mention of access rights to the local servers once the
MRTGext.nlm is loaded.

maybe they can e built into the readme.

_h
1 Comment
  Cluster features         


Author: tbiles
Date: Jul 25, 2006 09:53

I'm wondering if mrtgext is (or can be made) cluster aware, so that you
can monitor the cluster status, as well as clustered volumes. It seems to
be a "server centric" application, which is fine for most things.

Thanks.
2 Comments
  MRTGEXT setup problems         


Author: MChandler
Date: Jul 21, 2006 11:50

I'm not sure what's going on now. but I thought that I edited it on my
windows machine before putting it on my FC5 box and somehow contaminated
it with hidden characters like ^M. I was getting errors like:

-bash: ./nwextcfg.pl: /usr/bin/perl^M: bad interpreter: No such file or
directory

So I download it straight to the FC5 box and unzipped it there. same
error.

I then came across something to convert dos to unix format, dos2unix and
that cured that error.

But now when I run it, it puts a carriage return or linefeed each line
after the server name, like this:
Show full article (2.06Kb)
1 Comment