[mrtg] SNMP_Session error

[Nick Price]

Hi Niall

I use 1 configuration file per user, and output to a folder only the user has access to

Each config file can have 1 or more devices in it.

I don't get how to run mrtg with multiple .cfg files

I don't get the bit in the documentation about the S file in /etc/rc3.d   how do I know what number after the S to use and do I need to place in all the rc*.d directories.

Having never done this before, the only other thing I install is Nagios and it comes with an install-daemon.


Nick



-----Original Message-----
From: mrtg [mailto:mrtg-bounces+np121=hotmail.com at lists.oetiker.ch] On Behalf Of Niall O'Reilly
Sent: Tuesday, January 03, 2017 17:56
To: mrtg at lists.oetiker.ch
Subject: Re: [mrtg] SNMP_Session error



On 3 Jan 2017, at 15:17, Nick Price wrote:

> I use contrab because the output of every device is sent to a 
> different folder, so that the owner of that device is the only person 
> (except mrtgadmin) that can view it.

   I guess you're specifying the folder in the MRTG configuration file.
   If so, you can continue to do this in the same way.

   Do you use a single configuration file, or a separate one for each device,
   or some other approach?

> I have never set up mrtg as a daemon and not sure how to achieve the 
> same results as with crontab.

   It's explained in the section headed "RunAsDaemon" in the configuration reference
   (http://oss.oetiker.ch/mrtg/doc/mrtg-reference.en.html).  The 'Target' sections
   can remain unchanged.

> What has changes in the later version of perl that wasn't in fedora 22 
> where I didn't have this problem

   I can't be sure, as I'm not currently running any OS from the RedHat family
   (RHEL, CentOS, Fedora).  I have only Debian/Ubuntu and FreeBSD.  I suspect
   that a Perl module has been installed in two places and references to both
   are somehow (either explicitly or implicitly) being made by MRTG.  
This can
   come about through an accidental interaction between your approach to managing
   the packages involved and the release-engineering practice of the package
   and distribution developers.  Unfortunately, there is a risk of such an
   interaction at any version transition; I'm not sure it's useful to ask what
   has changed at this particular milestone.

> Any help setting it up to run as a daemon or a cure for the error 
> would help please.

   If you have just one configuration file and a corresponding single crontab
   entry, the transition to daemon mode is fairly simple.  You just need to
   obtain and install a starter script and follow the instructions for
   "RunAsDaemon".

> I'm not a Linux expert nor do I write perl, I just install and use

   I understand. 8-)

   Best regards,
   Niall O'Reilly

_______________________________________________
mrtg mailing list
mrtg at lists.oetiker.ch
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg