snmp and mrtg

[Brian Kelsay]

I'm guessing you have some sort of permission issue with usr/bin/rateup.
Does it run as root or does a user need to be created with permissions for
the program to run?  I've seen databases and webservers that needed this.
This may sound dumb, but it jumped out at me after seeing the error msgs.
Brian Kelsay

> -----Original Message-----
> From: Eric Rossiter [mailto:rossiter at discoverynet.com]
> Sent: Wednesday, April 25, 2001 12:58 PM
> To: kclug at kclug.org
> Subject: snmp and mrtg
> 
> 
> Ok, did everything Mike suggested...still no go. The cron entry I made
> returns the following lines in email:
> 
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_1
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_1 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_1.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_1.log to
> 192.168.10.2_1.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_2
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_2 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_2.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_2.log to
> 192.168.10.2_2.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_4
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_4 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_4.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_4.log to
> 192.168.10.2_4.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_5
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_5 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_5.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_5.log to
> 192.168.10.2_5.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_6
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_6 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_6.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_6.log to
> 192.168.10.2_6.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_9
> Rateup WARNING: /usr/bin/rateup The backup log file for 
> 192.168.10.2_9 was
> invalid as well
> Rateup WARNING: /usr/bin/rateup Can't remove 
> 192.168.10.2_9.old updating log
> file
> Rateup WARNING: /usr/bin/rateup Can't rename 192.168.10.2_9.log to
> 192.168.10.2_9.old updating log file
> Rateup WARNING: /usr/bin/rateup could not read the primary 
> log file for
> 192.168.10.2_10
> 
> etc., etc....
> 
> Cron fired off two emails, five minutes apart, and now 
> nothing for over 30
> minutes.....
> 
> I'm lost, I'm frustrated, and like everything else I try to do in
> Linux...I'll give this up after three days of banging my head 
> against the
> wall.....
> 
> Thanks for letting me rant.... =)
> 
> Eric
> 
> 
> 
> majordomo at kclug.org
>