Cactid frustrations
Moderators: Developers, Moderators
Cactid frustrations
After some fun with Ubuntu and its cacti repositories I know in future I will be manually compiling and installing cacti if I ever have to do it! At least that way I'll be more confident about how exactly its setup.
I've replaced an old BSD based dying server with a nice shiny new Ubuntu based one. Unfortunately Cactid refuses to run properly on this box. Following some comments on here about issues with the default repository build (0.8.6f) I've downloaded and compiled my own of 0.8.6i.. unfortunately this still comes up with the same issue.
I think I know whats going on and it relates to no longer existant interfaces / SNMP devices on the switch in question.
an output from tcpdump is what started to cause suspicions in this regard (I've removed sensitive data):
:/usr/share/cacti/site# tcpdump -ieth0 -n port snmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
19:16:08.116827 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(28) .1.3.6.1.2.1.1.3.0
19:16:08.118915 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(32) .1.3.6.1.2.1.1.3.0=2041250959
19:16:08.119703 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(28) .1.3.6.1.2.1.1.3.0
19:16:08.121219 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(32) .1.3.6.1.2.1.1.3.0=2041250959
19:16:08.122434 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(94) .1.3.6.1.2.1.2.2.1.10.1 .1.3.6.1[|snmp]
19:16:08.124917 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(94) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.1= .1.3.6.1[|snmp]
19:16:08.124987 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(78) .1.3.6.1.2.1.2.2.1.10.10 .1.3.6.1[|snmp]
19:16:08.127138 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(78) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.10= .1.3.6.1[|snmp]
19:16:08.127183 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(62) .1.3.6.1.2.1.2.2.1.10.11 .1.3.6.1[|snmp]
19:16:08.129070 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(62) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.11= .1.3.6.1[|snmp]
19:16:08.129116 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(46) .1.3.6.1.2.1.2.2.1.10.12 .1.3.6.1[|snmp]
19:16:08.131428 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(46) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.12= .1.3.6.1[|snmp]
19:16:08.131468 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(30) .1.3.6.1.2.1.2.2.1.10.13
19:16:08.133111 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(30) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.13=
19:16:08.133520 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(30) .1.3.6.1.2.1.2.2.1.10.14
19:16:08.135006 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(30) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.14=
This is using my custom build of cactid. It returns the following (again confidential data removed):
/usr/local/cactid/bin/cdb# /usr/local/cactid/bin/cactid --verbosity=DEBUG 79 79
CACTID: Using cactid config file [/etc/cactid.conf]
CACTID: Version 0.8.6i starting
CACTID: Host[79] DS[6063] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6072] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6073] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6074] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6075] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6076] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
Yes.. I know 50,000ms is a rather large figure I was trying to confirm my suspicions.
It produces that result very quickly and then stops, so it seems like if it doesn't get a happy response back from the switch, even though the switch is alive, cactid stops? I would guess this was put in with the intention that Cactid wouldn't waste time polling a dead device? Its not exactly dead, it is actually responding to the poller, it just doesn't have any data for those interfaces any more!
I really would like to get this working and shift away from cmd.php if I can!
If anyone has any suggestions on how to clean up the switch I'd love to hear them too.. I'd really rather avoid deleting and re-creating the switch if at all possible, as I'd like to keep all the history for the interfaces.
I've replaced an old BSD based dying server with a nice shiny new Ubuntu based one. Unfortunately Cactid refuses to run properly on this box. Following some comments on here about issues with the default repository build (0.8.6f) I've downloaded and compiled my own of 0.8.6i.. unfortunately this still comes up with the same issue.
I think I know whats going on and it relates to no longer existant interfaces / SNMP devices on the switch in question.
an output from tcpdump is what started to cause suspicions in this regard (I've removed sensitive data):
:/usr/share/cacti/site# tcpdump -ieth0 -n port snmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
19:16:08.116827 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(28) .1.3.6.1.2.1.1.3.0
19:16:08.118915 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(32) .1.3.6.1.2.1.1.3.0=2041250959
19:16:08.119703 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(28) .1.3.6.1.2.1.1.3.0
19:16:08.121219 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(32) .1.3.6.1.2.1.1.3.0=2041250959
19:16:08.122434 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(94) .1.3.6.1.2.1.2.2.1.10.1 .1.3.6.1[|snmp]
19:16:08.124917 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(94) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.1= .1.3.6.1[|snmp]
19:16:08.124987 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(78) .1.3.6.1.2.1.2.2.1.10.10 .1.3.6.1[|snmp]
19:16:08.127138 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(78) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.10= .1.3.6.1[|snmp]
19:16:08.127183 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(62) .1.3.6.1.2.1.2.2.1.10.11 .1.3.6.1[|snmp]
19:16:08.129070 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(62) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.11= .1.3.6.1[|snmp]
19:16:08.129116 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(46) .1.3.6.1.2.1.2.2.1.10.12 .1.3.6.1[|snmp]
19:16:08.131428 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(46) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.12= .1.3.6.1[|snmp]
19:16:08.131468 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(30) .1.3.6.1.2.1.2.2.1.10.13
19:16:08.133111 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(30) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.13=
19:16:08.133520 IP lo.ca.l.ip.52671 > rem.ote.ip.add.161: C=<our community> GetRequest(30) .1.3.6.1.2.1.2.2.1.10.14
19:16:08.135006 IP rem.ote.ip.add.161 > lo.ca.l.ip.52671: C=<our community> GetResponse(30) noSuchName@1 .1.3.6.1.2.1.2.2.1.10.14=
This is using my custom build of cactid. It returns the following (again confidential data removed):
/usr/local/cactid/bin/cdb# /usr/local/cactid/bin/cactid --verbosity=DEBUG 79 79
CACTID: Using cactid config file [/etc/cactid.conf]
CACTID: Version 0.8.6i starting
CACTID: Host[79] DS[6063] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6072] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6073] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6074] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6075] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
CACTID: Host[79] DS[6076] WARNING: SNMP timeout detected [50000 ms], ignoring host '<remote-switch>'
Yes.. I know 50,000ms is a rather large figure I was trying to confirm my suspicions.
It produces that result very quickly and then stops, so it seems like if it doesn't get a happy response back from the switch, even though the switch is alive, cactid stops? I would guess this was put in with the intention that Cactid wouldn't waste time polling a dead device? Its not exactly dead, it is actually responding to the poller, it just doesn't have any data for those interfaces any more!
I really would like to get this working and shift away from cmd.php if I can!
If anyone has any suggestions on how to clean up the switch I'd love to hear them too.. I'd really rather avoid deleting and re-creating the switch if at all possible, as I'd like to keep all the history for the interfaces.
- TheWitness
- Developer
- Posts: 17007
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Hmm, that's quite odd. Can you please download and build the SVN version of the product (BRANCH_0_8_6) and then can we do an online "GotoMeeting" conference sometime Thursday?
I am in the Eastern Time Zone. Detroit, MI. What do you think? This is definately a bug, but I would like to do this live.
TheWitness
I am in the Eastern Time Zone. Detroit, MI. What do you think? This is definately a bug, but I would like to do this live.
TheWitness
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
I'm trying to use the SVN build of the cactid, but its failing on make?
Makefile syntax isn't something I've delved into to be honest!
The commands I ran:
Which returns:
Makefile:204: *** missing separator. Stop.
*shrug*
Same occurs from a "make install"
Line 204 for me reads:
@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cactid.Po@am__quote@
I've attached a copy
Makefile syntax isn't something I've delved into to be honest!
The commands I ran:
Code: Select all
svn checkout svn://svn.cacti.net/var/svnroot/cacti/branches/BRANCH_0_8_6
cd /BRANCH_0_8_6/cactid
aclocal
autoconf
./configure
make
Makefile:204: *** missing separator. Stop.
*shrug*
Same occurs from a "make install"
Line 204 for me reads:
@AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/cactid.Po@am__quote@
I've attached a copy
- TheWitness
- Developer
- Posts: 17007
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Hmm. Well maybe there is a GotoMeeting in our future...
TheWitness
TheWitness
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Garp,
Please let me know the outcome of this, as your error symptoms seem very similar to my own. Here's my thread:
http://forums.cacti.net/viewtopic.php?t=20523
Thanks!
Please let me know the outcome of this, as your error symptoms seem very similar to my own. Here's my thread:
http://forums.cacti.net/viewtopic.php?t=20523
Thanks!
2x Xeon 3.4Ghz / 4GB RAM
Cacti Version - 0.8.6j
Poller Type - cactid CVS
Server Info - RHEL5
Web Server - Apache/2.2.3-6 (Unix)
PHP/5.1.6-12
MySQL - 5.0.22.-2.1
RRDTool - 1.2.23
SNMP - 5.3-1.14.0.1
Cacti Version - 0.8.6j
Poller Type - cactid CVS
Server Info - RHEL5
Web Server - Apache/2.2.3-6 (Unix)
PHP/5.1.6-12
MySQL - 5.0.22.-2.1
RRDTool - 1.2.23
SNMP - 5.3-1.14.0.1
Okay, I finally got a chance to look at this further.
Grabbed the SVN version, ran the bootstrap, configured, compiled and installed it.
root@<server>:/home/<user>/BRANCH_0_8_6/cactid# /usr/local/cactid/bin/cactid -v
CACTID 0.8.6i Copyright 2002-2006 by The Cacti Group
Okay, so thats good (I hope). The apt version gets installed elsewhere.
root@<server>:/home/<user>/BRANCH_0_8_6/cactid# /usr/local/cactid/bin/cactid --verbosity=DEBUG 79 79
CACTID: Using cactid config file [/etc/cactid.conf]
CACTID: Version 0.8.6i starting
CACTID: Host[79] DS[6063] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6072] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6073] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6074] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6075] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6076] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Time: 1.4180 s, Threads: 8, Hosts: 2
It looks like the latest SVN version of CACTID does the same as the released version of CACTID *shrug*
just running CACTID without locking it down to that specific host I know came up with an error last time and I can see that CACTID will poll devices succesfully, it does still seem to come down to that if the first thing it polls isn't active, even if it gets a response back from the remote device it gives up. It certainly doesn't reach that deliberately stupidly high timeout
Grabbed the SVN version, ran the bootstrap, configured, compiled and installed it.
root@<server>:/home/<user>/BRANCH_0_8_6/cactid# /usr/local/cactid/bin/cactid -v
CACTID 0.8.6i Copyright 2002-2006 by The Cacti Group
Okay, so thats good (I hope). The apt version gets installed elsewhere.
root@<server>:/home/<user>/BRANCH_0_8_6/cactid# /usr/local/cactid/bin/cactid --verbosity=DEBUG 79 79
CACTID: Using cactid config file [/etc/cactid.conf]
CACTID: Version 0.8.6i starting
CACTID: Host[79] DS[6063] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6072] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6073] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6074] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6075] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Host[79] DS[6076] WARNING: SNMP timeout detected [50000 ms], ignoring host 'remote.host'
CACTID: Time: 1.4180 s, Threads: 8, Hosts: 2
It looks like the latest SVN version of CACTID does the same as the released version of CACTID *shrug*
just running CACTID without locking it down to that specific host I know came up with an error last time and I can see that CACTID will poll devices succesfully, it does still seem to come down to that if the first thing it polls isn't active, even if it gets a response back from the remote device it gives up. It certainly doesn't reach that deliberately stupidly high timeout
OIDs Per SNMP Get Request
I was seeing this exact same thing on various platforms...Netscaler, SonicWall iNOC, Foundry ServerIrons, and yes...CatOS...
My fix was to keep backing down my OIDs per SNMP Get Request until they all vanished. Now I run the following:
Concurrent Processes: 4
Max Threads: 15
PHP Script Servers: 4
Timeout: 5
Max SNMP OID's Per SNMP Get Request: 20
Had it at 30, but Netscalers didn't like that...
-Dave
My fix was to keep backing down my OIDs per SNMP Get Request until they all vanished. Now I run the following:
Concurrent Processes: 4
Max Threads: 15
PHP Script Servers: 4
Timeout: 5
Max SNMP OID's Per SNMP Get Request: 20
Had it at 30, but Netscalers didn't like that...
-Dave
Who is online
Users browsing this forum: No registered users and 0 guests