Re: Can't locate RRDs.pm or HTML/Template.pm

I did a clear reinstallation using RPMs. It worked
now.  
It is a good learning experience for me.
Thanks for all your help!

--- Lupe Christoph <lupe@xxxxxxxxxxxxxxxxx> wrote:

> On Wednesday, 2006-12-13 at 21:09:35 -0800, Victor
> wrote:
> 
> > Thanks for your help. Following your advice, I
> > installed those RPMs and now got Munin basically
> work.
> > Now the problem is I couldn't get plugin work.
> Could
> > you point out what was wrong? --  I hope this is
> my
> > last post on this thread:)
> > This is what I did:
> > 1. I created file plugin.conf under
> > $CONFDIR/plugin-conf.d
> > which contains very simple config:
> > [cpu]
> > user root
> 
> Is /proc/stat only readable by root on CentOS?
> 
> > 2. I put the plugin script cpu (copied from Munin
> > installation) under $CONFDIR/plugins
> 
> Please use "munin-node-configure --shell" to
> generate commands to
> install plugins. If you want to blindly accept the
> suggestions, just
> pipe the output into sh.
> 
> > 3. Restart munin-node (I have two Munin instances
> > installed because of the RPM installation. I use
> the
> > instance installed by rpm (1.2.4) as the server
> and
> > the previously installed instance (1.3.2) as the
> > client/node)
> 
> Why didn't you just use the same version? I would
> also be better to
> remove all versions of Munin completely and start
> from a clean slate.
> You have probably mixed the two releases.
> 
> > 4. I did NOT modify munin.conf (because it should
> > graph all unless we specify "[service].graph no".
> I
> > also tried adding "cpu.lable cpu" etc to
> munin.conf.
> 
> Why did you do that?
> 
> > It didn't work.
> 
> What did not work?
> 
> > 5. Manually execute munin-cron. Then I found below
> in
> > the munin-node.log
> 
> > 2006/12/13-20:59:36 CONNECT TCP Peer:
> > "127.0.0.1:47574" Local: "127.0.0.1:4949"
> > Insecure directory in $ENV{PATH} while running
> with -T
> > switch at ./munin-node line 482, <STDIN> line 2.
> > 2006/12/13-20:59:36 [30074] Plugin "cpu" exited
> with
> > status 2304. ----
> > Insecure directory in $ENV{PATH} while running
> with -T
> > switch at ./munin-node line 482, <STDIN> line 3.
> > 2006/12/13-20:59:36 [30074] Plugin "cpu" exited
> with
> > status 2304. ----
> 
> Please use munin-run --debug cpu to see more.
> 
> > 6. In the browser http://localhost/munin
> > I didn't see any graph. i.e., if I click the
> localhost
> > link, no graph shows up.
> 
> > Did I miss any plugin config? 
> 
> Dunno. You are doing so many strange things that run
> against the normal
> way of installing and running Munin that I can't
> tell.
> 
> Lupe Christoph
> -- 
> | You know we're sitting on four million pounds of
> fuel, one nuclear     |
> | weapon and a thing that has 270,000 moving parts
> built by the lowest   |
> | bidder. Makes you feel good, doesn't it?          
>                     |
> | Rockhound in "Armageddon", 1998, about the Space
> Shuttle               |
> 



 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV