On a closer look I see you configured SNMPv2 and that your host does not 
support 
the Counter64 OIDs.

So please use SNMPv1 on it.

Javier

[EMAIL PROTECTED] wrote:
> 
> SELinux is enabled on the system running jffnms.  It is not enabled on 
> the system with the physical interfaces.
> 
> It's only the physical interfaces from the polled hosts that are 
> affected.  ALL physical interfaces fail to have data retrieved.  The 
> other kinds of interfaces (disk, CPU, memory) store data and display 
> graphs.
> 
> ----------
> Bob Diss
> Applications Manager
> Follett Library Resources
> [EMAIL PROTECTED]
> 
> 
> 
> *"Kory" <[EMAIL PROTECTED]>*
> Sent by: [EMAIL PROTECTED]
> 
> 06/09/06 03:57 PM
> 
>       
> To
>       <[EMAIL PROTECTED]>, <jffnms-users@lists.sourceforge.net>
> cc
>       
> Subject
>       Re: [jffnms-users] Problem with physical interfaces / rrd files       
>  notpopulated
> 
> 
>       
> 
> 
> 
> 
> 
> Check to make sure that SELinux is disabled or at least not affecting 
> your jffnms operations.
>  
> Thanks,
> Kory Knopp
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] *On Behalf Of 
> [EMAIL PROTECTED]
> Sent:* Friday, June 09, 2006 1:09 PM*
> To:* [EMAIL PROTECTED]
> Subject:* [jffnms-users] Problem with physical interfaces / rrd files 
> notpopulated
>  
> 
> Hi all.  I seem to be having a problem that's frequently reported, but 
> the solutions mentioned in the mail archives don't work for me.  I've 
> just installed a fresh copy of JFFNMS 0.8.2 on my RedHat Fedora Core 
> 3-based system.  Install went smooth - configured users, zones, hosts. 
>  Auto-discovery found my interfaces, including disk, memory, and network 
> interfaces.  The problem is that the graphs for the network interfaces 
> do not get created.  Instead, I get the message "The RRDTool files for 
> Interface ID 27 (from Host ID 3), has not been created by the Poller 
> Process yet".
> 
> I'm aware that this is a common message, and that the 
> frequently-suggested remedy is to downgrade the version of rrdtool in 
> use and then delete the *.rrd files so that they can be re-created. 
>  I've backed my rrdtool version back from 1.2.13 to 1.0.49, and then 
> back to 1.0.39, and deleted the *.rrd files for the network interfaces, 
> but no luck.
> 
> It seems that the rrd files for the other interfaces have values stored 
> in them.  However, when I "rrdtool dump" the interface-#-0.rrd file for 
> a network interface, I see that the "last update" value never changes, 
> and that there are no values stored in the database (all the rows are 
> "NaN").  The files do get created, but no values are ever placed in them.
> 
> I've run the polling process by hand, and it reports no errors.  I've 
> run all the other processes as well (consolidate, rrd_analyzer, 
> cleanup_raw_tables, autodiscovery_interfaces, autodiscovery_network, 
> tftp_get_host_config) -- these report no errors as well.
> 
> I've verified permissions on the directory where jffnms is installed, 
> and ensured that the file permissions on the *.rrd files for the network 
> interfaces are the same as those for non-network interfaces.
> 
> I've checked in the apache log for errors - none reported.
> 
> I've checked in the jffnms/logs directory for error log files - none 
> present.
> 
> I've run the polling process by hand for the individual host/interface 
> affected (php -q poller.php host# interface#) - it does not updated the 
> related *.rrd files.  The output of this is included below:
> 
> [EMAIL PROTECTED] engine]# php poller.php 3 27
> 14:07:35  :  H   3 : Poller Start : 19 Items.
> 14:07:35  :  H   3 :  I  27 :  P  10 : verify_interface_number(): 2 -> 
> verify_interface_number(): interfacenumber not changed (time P:5.04 | 2.19)
> 14:07:35  :  H   3 :  I  27 :  P  15 : 
> cisco_snmp_ping_start:cisco_snmp_ping_start(): -1 -> buffer(): 1 (time 
> P:1.42 | 0.44)
> 14:07:35  :  H   3 :  I  27 :  P  16 : interface_oper_status(8): up -> 
> alarm(3,,180): Nothing was done (time P:4.59 | 2.06)
> 14:07:35  :  H   3 :  I  27 :  P  17 : interface_admin_status(7): up -> 
> db(show_rootmap,down=2|up=1,0): 0 (time P:2.57 | 0.59)
> 14:07:35  :  H   3 :  I  27 :  P  20 : snmp_counter:input(.1.3..6.2): 
>  -> buffer(): 2 (time P:1.56 | 0.26)
> 14:07:35  :  H   3 :  I  27 :  P  25 : 
> snmp_counter:inpackets(.1.3..7.2):  -> buffer(): 3 (time P:1.17 | 0.26)
> 14:07:35  :  H   3 :  I  27 :  P  30 : snmp_counter:output(.1.3..0.2): 
>  -> buffer(): 4 (time P:1.16 | 0.26)
> 14:07:35  :  H   3 :  I  27 :  P  35 : 
> snmp_counter:outpackets(.1.3..1.2):  -> buffer(): 5 (time P:1.16 | 0.26)
> 14:07:35  :  H   3 :  I  27 :  P  40 : 
> snmp_counter:outputerrors(.1.3..0.2): 0 -> buffer(): 6 (time P:2.12 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  45 : 
> snmp_counter:inputerrors(.1.3..4.2): 0 -> buffer(): 7 (time P:2.09 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  46 : snmp_counter:drops(.1.3..9.2): 0 
> -> buffer(): 8 (time P:2.09 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  47 : db:bandwidthin(band..tes): 
> 12500000 -> buffer(): 9 (time P:0.38 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  48 : db:bandwidthout(band..tes): 
> 12500000 -> buffer(): 10 (time P:0.19 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  50 : cisco_snmp_ping_wait(): -1 -> 
> no_backend(): 0 (time P:0.57 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  55 : 
> cisco_snmp_ping_get_pl:packetloss(): 0 -> buffer(): 11 (time P:0.49 | 0.26)
> 14:07:35  :  H   3 :  I  27 :  P  60 : cisco_snmp_ping_get_rtt:rtt(): 0 
> -> buffer(): 12 (time P:0.43 | 0.27)
> 14:07:35  :  H   3 :  I  27 :  P  65 : cisco_snmp_ping_end(): -1 -> 
> no_backend(): 0 (time P:0.41 | 0.19)
> 14:07:35  :  H   3 :  I  27 :  P  80 : no_poller(): 0 -> rrd(*): 
> inputerrors:0 - outputerrors:0 - rtt:0 - packetloss:0 - drops:0 - 
> bandwidthin:12500000 - bandwidthout:12500000 (time P:0.25 | 45.14)
> 14:07:35  :  H   3 :  I  27 :  P LPD : last_poll_date(): 1149880055 -> 
> db(last_poll_date): 1 (time P:0.37 | 5.28)
> 14:07:35  :  H   3 : Poller End, Total Time: 113.13 msec.
> 
> What can I try next?
> 
> ----------
> Bob Diss
> Applications Manager
> Follett Library Resources
> [EMAIL PROTECTED]
> 
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.3/359 - Release Date: 6/8/2006
> 
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.8.3/359 - Release Date: 
> 6/8/2006_______________________________________________
> jffnms-users mailing list
> jffnms-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jffnms-users
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> jffnms-users mailing list
> jffnms-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jffnms-users

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Javier Szyszlican, Project Leader, JFFNMS
[EMAIL PROTECTED]

I hope JFFNMS or I were helpful to you, if you
can, please donate at http://jffnms.org/donate



_______________________________________________
jffnms-users mailing list
jffnms-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jffnms-users

Reply via email to