cacti-user Mailing List for Cacti

Nevermind, I figured out my problem. Please disregard.

Had to change the graphs 'last' to 'average'

On Jan 29, 2009, at 9:54 AM, Charlie Reddington wrote:

> I am using using a sarparse utility found off the fourms. Everything  
> is working great except 2 graphs. I'm mearly going to concentrate on  
> one right now.
>
> On the graph, in debug mode, I get the following...
>
> ------------- SNIP --------------
> /usr/bin/rrdtool graph - \
> --imgformat=PNG \
> --start=-86400 \
> --end=-300 \
> --title="serv56.ord01 - SarParse - Memory Usage" \
> --base=1000 \
> --height=250 \
> --width=750 \
> --alt-autoscale-max \
> --lower-limit=0 \
> --vertical-label="kb" \
> --slope-mode \
> --font TITLE:12: \
> --font AXIS:8: \
> --font LEGEND:10: \
> --font UNIT:8: \
> DEF:a="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemused:LAST \
> DEF:b="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemused:MAX \
> DEF:c="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemfree:LAST \
> DEF:d="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemfree:MAX \
> DEF:e="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbbuffers:LAST \
> DEF:f="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbbuffers:MAX \
> DEF:g="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbcached:LAST \
> DEF:h="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbcached:MAX \
> DEF:i="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpused:LAST \
> DEF:j="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpused:MAX \
> DEF:ba="/var/www/cacti/rra/ 
> serv01_kbmemused_550.rrd":kbswpcad:AVERAGE \
> DEF:bb="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpcad:MAX \
> CDEF:cdefa=a,1024,* \
> CDEF:cdefc=b,1024,* \
> CDEF:cdefe=c,1024,* \
> CDEF:cdefg=d,1024,* \
> CDEF:cdefi=e,1024,* \
> CDEF:cdefbb=f,1024,* \
> CDEF:cdefbc=g,1024,* \
> CDEF:cdefbe=h,1024,* \
> CDEF:cdefbg=i,-1024,* \
> CDEF:cdefbh=i,1024,* \
> CDEF:cdefbi=j,1024,* \
> CDEF:cdefca=ba,-1024,* \
> CDEF:cdefcb=ba,1024,* \
> CDEF:cdefcd=bb,1024,* \
> AREA:cdefa#8D85F3FF:"Used\:"  \
> GPRINT:cdefa:LAST:"        Current\:%8.2lf%s"  \
> GPRINT:cdefc:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefc:MAX:"Maximum\:%8.2lf%s\n"  \
> AREA:cdefe#C4FD3DFF:"Free\:":STACK \
> GPRINT:cdefe:LAST:"        Current\:%8.2lf%s"  \
> GPRINT:cdefg:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefg:MAX:"Maximum\:%8.2lf%s\n"  \
> AREA:cdefi#55009DFF:"Kernel\:"  \
> GPRINT:cdefi:LAST:"      Current\:%8.2lf%s"  \
> GPRINT:f:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefbb:MAX:"Maximum\:%8.2lf%s\n"  \
> AREA:cdefbc#F5F800FF:"Kernel Cache\:":STACK \
> GPRINT:cdefbc:LAST:"Current\:%8.2lf%s"  \
> GPRINT:cdefbe:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefbe:MAX:"Maximum\:%8.2lf%s\n"  \
> AREA:cdefbg#FF5F00FF:"Swap Used\:"  \
> GPRINT:cdefbh:LAST:"   Current\:%8.2lf%s"  \
> GPRINT:cdefbi:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefbi:MAX:"Maximum\:%8.2lf%s\n"  \
> AREA:cdefca#FF0000FF:"Cached Swap\:"  \
> GPRINT:cdefcb:LAST:" Current\:%8.2lf%s"  \
> GPRINT:cdefcb:AVERAGE:"Average\:%8.2lf%s"  \
> GPRINT:cdefcd:MAX:"Maximum\:%8.2lf%s\n"
> RRDToolSays:
> Error: the rrd does not contain an rra matching the chosen CF
> ------------ End Snip --------------
>
> I have checked to make sure that the RRD file does indeed exist. I  
> have checked the log for any errors regarding this as well, with  
> nothing sticking out at me that this has an error.
>
> Any advise on where to look next?
>
> Charlie

I am using using a sarparse utility found off the fourms. Everything  
is working great except 2 graphs. I'm mearly going to concentrate on  
one right now.

On the graph, in debug mode, I get the following...

------------- SNIP --------------
/usr/bin/rrdtool graph - \
--imgformat=PNG \
--start=-86400 \
--end=-300 \
--title="serv56.ord01 - SarParse - Memory Usage" \
--base=1000 \
--height=250 \
--width=750 \
--alt-autoscale-max \
--lower-limit=0 \
--vertical-label="kb" \
--slope-mode \
--font TITLE:12: \
--font AXIS:8: \
--font LEGEND:10: \
--font UNIT:8: \
DEF:a="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemused:LAST \
DEF:b="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemused:MAX \
DEF:c="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemfree:LAST \
DEF:d="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbmemfree:MAX \
DEF:e="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbbuffers:LAST \
DEF:f="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbbuffers:MAX \
DEF:g="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbcached:LAST \
DEF:h="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbcached:MAX \
DEF:i="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpused:LAST \
DEF:j="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpused:MAX \
DEF:ba="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpcad:AVERAGE \
DEF:bb="/var/www/cacti/rra/serv01_kbmemused_550.rrd":kbswpcad:MAX \
CDEF:cdefa=a,1024,* \
CDEF:cdefc=b,1024,* \
CDEF:cdefe=c,1024,* \
CDEF:cdefg=d,1024,* \
CDEF:cdefi=e,1024,* \
CDEF:cdefbb=f,1024,* \
CDEF:cdefbc=g,1024,* \
CDEF:cdefbe=h,1024,* \
CDEF:cdefbg=i,-1024,* \
CDEF:cdefbh=i,1024,* \
CDEF:cdefbi=j,1024,* \
CDEF:cdefca=ba,-1024,* \
CDEF:cdefcb=ba,1024,* \
CDEF:cdefcd=bb,1024,* \
AREA:cdefa#8D85F3FF:"Used\:"  \
GPRINT:cdefa:LAST:"        Current\:%8.2lf%s"  \
GPRINT:cdefc:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefc:MAX:"Maximum\:%8.2lf%s\n"  \
AREA:cdefe#C4FD3DFF:"Free\:":STACK \
GPRINT:cdefe:LAST:"        Current\:%8.2lf%s"  \
GPRINT:cdefg:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefg:MAX:"Maximum\:%8.2lf%s\n"  \
AREA:cdefi#55009DFF:"Kernel\:"  \
GPRINT:cdefi:LAST:"      Current\:%8.2lf%s"  \
GPRINT:f:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefbb:MAX:"Maximum\:%8.2lf%s\n"  \
AREA:cdefbc#F5F800FF:"Kernel Cache\:":STACK \
GPRINT:cdefbc:LAST:"Current\:%8.2lf%s"  \
GPRINT:cdefbe:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefbe:MAX:"Maximum\:%8.2lf%s\n"  \
AREA:cdefbg#FF5F00FF:"Swap Used\:"  \
GPRINT:cdefbh:LAST:"   Current\:%8.2lf%s"  \
GPRINT:cdefbi:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefbi:MAX:"Maximum\:%8.2lf%s\n"  \
AREA:cdefca#FF0000FF:"Cached Swap\:"  \
GPRINT:cdefcb:LAST:" Current\:%8.2lf%s"  \
GPRINT:cdefcb:AVERAGE:"Average\:%8.2lf%s"  \
GPRINT:cdefcd:MAX:"Maximum\:%8.2lf%s\n"
RRDToolSays:
Error: the rrd does not contain an rra matching the chosen CF
------------ End Snip --------------

I have checked to make sure that the RRD file does indeed exist. I  
have checked the log for any errors regarding this as well, with  
nothing sticking out at me that this has an error.

Any advise on where to look next?

Charlie

Hello List,

I am using Cacti 0.8.6i.

I'd like to have a switch's / router's ifIndex (or port number) in the filename of the rrd Cacti creates.

As far as I see it, Cacti puts a random(? or auto increment) integer, that also serves as the ID in Cacti's database, behind the hostdescription as the file name for any newly created rrd file.
While this is a pretty easy system and works great for Cacti, I have the need to identify a certain port of a certain device only by the filename.

For example, I have a router with 20 GE ports, with the ifIndex ID's of 1 to 20. The router is named edge1.mynet.local.

So I'd like Cacti to automatically create the rrd for, let's say, port 17 as edge1_mynet_local_17.rrd or edge1_mynet_local_17_<DBID>.rrd.

While of course I am able to enter the rrd filename any time I create a single graph, I seem to be unable to control this when using the "SNMP - Interface Statistics" Data Query to monitor and graph a lot of ports at once.


A little background info:
Cacti's poller will collect the information from switches / routers. The rra directory is mounted read only over NFS on another host. This host will then use rrdtool and the .rrd files from Cacti to create graphs for certain ports.
That is why the software running on the other host needs to be able to identify a port only by the filename.


I see several options:

1.) There is an easy way to do this with Cacti: Perfect
2.) I need to change some code in Cacti: Good Option, not a big problem, can someone point me to the right file and line?
3.) I need the software on the graphing host to contact Cacti's database and get the port <-> ID assignment: Would work, but would love to not add an extra DB connection
4.) I have to edit every port/graph/rrd by hand: Not very appealing, I have to add several thousands of ports.
5.) A newer Version of Cacti can do this: Then I'll be glad to update. If not, I'd prefer to stick with the distribution packaged version.

I appreciate any hint that will guide me in the right direction.


Thank you,
Philipp

Peter,

Please log a bug at http://bugs.cacti.net and attach your patch.  Thanks 
for making Cacti a better tool!

Regards,

TheWitness

Peter Östlin wrote:
> I don't know if this is the proper forum but I have a question regarding
> ping.c, the ping_icmp function to be exact.
>
> If I read the code correctly we send a new icmp package each time we get
> a response which is not an echo reply or if it is from an other host. Is
> that really necessary? I have seen 'floods' of icmp packages which I
> trace back to this behaviour. The result is that we might send out more
> (possible way more) packages then the retry_count tell us to do.
>
>
> Attached is a patch that makes ping.c only send new package when the 
> previous timed out.
>
> Cheers
> /Peter
>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> ------------------------------------------------------------------------
>
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user

I don't know if this is the proper forum but I have a question regarding
ping.c, the ping_icmp function to be exact.

If I read the code correctly we send a new icmp package each time we get
a response which is not an echo reply or if it is from an other host. Is
that really necessary? I have seen 'floods' of icmp packages which I
trace back to this behaviour. The result is that we might send out more
(possible way more) packages then the retry_count tell us to do.


Attached is a patch that makes ping.c only send new package when the 
previous timed out.

Cheers
/Peter

Jackie,

That would be best.  It should be out tonight (I hope).

Larry
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Jackie Hunt <ja...@yu...>

Date: Mon, 26 Jan 2009 13:57:57 
To: <cac...@li...>
Subject: [cacti-user] export graphs with 1 minute polling



Hi all,

I'm trying to export a graph on cacti 0.8.7b which is using 1 minute polling.
I've disabled exporting all graphs, except for the one I want.  Then I enabled
exporting every x times, and found that my graph is exported every minute.  I'd
like to have it exported every 5 minutes.  

I saw on mantis there is a fix for this.  I tried updating the 
lib/graph_export.php file as indicated in:
 
http://bugs.cacti.net/view.php?id=1318

but that really messed things up.  It started exporting all the graphs
causing lots of timeouts.  Do I have to upgrade to 0.8.7c to get this
fixed?  Is there a manual way to export a graph that I can run as a crontab?
I've heard this mentioned but can't find a script to do this. 

Thanks for any info!

Jackie Hunt                                                       
ACNS                                    Voice:  (970) 663-3789     
Colorado State University               FAX:    (970) 491-1958
Fort Collins, CO  80523                 Email:  jac...@co...

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
cacti-user mailing list
cac...@li...
https://lists.sourceforge.net/lists/listinfo/cacti-user

Hi all,

I'm trying to export a graph on cacti 0.8.7b which is using 1 minute polling.
I've disabled exporting all graphs, except for the one I want.  Then I enabled
exporting every x times, and found that my graph is exported every minute.  I'd
like to have it exported every 5 minutes.  

I saw on mantis there is a fix for this.  I tried updating the 
lib/graph_export.php file as indicated in:
 
http://bugs.cacti.net/view.php?id=1318

but that really messed things up.  It started exporting all the graphs
causing lots of timeouts.  Do I have to upgrade to 0.8.7c to get this
fixed?  Is there a manual way to export a graph that I can run as a crontab?
I've heard this mentioned but can't find a script to do this. 

Thanks for any info!

Jackie Hunt                                                       
ACNS                                    Voice:  (970) 663-3789     
Colorado State University               FAX:    (970) 491-1958
Fort Collins, CO  80523                 Email:  jac...@co...

Larry:

On item 3 blow, what do you mean by optimize? Reindex? If yes, on what
field?

Thanks,

-h

-----Original Message-----
From: lar...@co... [mailto:lar...@co...] 
Sent: Friday, January 23, 2009 6:46 PM
To: Support requests/questions about cacti
Subject: Re: [cacti-user] performance impact of rebuilding the poller
cache

Do a few things.

1) Watch out for 087c of both cacti and spine
2) Deploy boost 2.1.  I will deploy 2.2 momentarily.
3) Optimize your poller_items table from time to time.  About once a
week or so.


Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Carlos Vicente <cvi...@ne...>

Date: Fri, 23 Jan 2009 14:50:53 
To: Support requests/questions about
cacti<cac...@li...>
Subject: [cacti-user] performance impact of rebuilding the poller cache


Hi all,

I run a fairly large Cacti installation with about 1,200 devices,
176,000 rrd files (using spine, of course).  I've observed a pattern
that I'm trying to understand.  At first, the poller runtime average
stays under 200 seconds.  Over a period of about three weeks, the poller
runtime starts to slowly increase to close to 300 seconds, to the point
where it can no longer finish within 300 seconds (my polling period),
and graphs start to show gaps.  The first time this happened, I tried a
number of tweaks (number of processes, number of threads per process,
etc) and none of them worked.  Then I manually rebuilt the poller cache,
and bingo! poller stats went back down to under 200 seconds.  This just
happened again today.   The question is, why exactly does this happen? 
>From what I read in the documentation, it doesn't seem like the poller
cache should be out of sync, nor affecting poller performance.

Thanks in advance,

cv

------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
cacti-user mailing list
cac...@li...
https://lists.sourceforge.net/lists/listinfo/cacti-user
------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
cacti-user mailing list
cac...@li...
https://lists.sourceforge.net/lists/listinfo/cacti-user

Do a few things.

1) Watch out for 087c of both cacti and spine
2) Deploy boost 2.1.  I will deploy 2.2 momentarily.
3) Optimize your poller_items table from time to time.  About once a week or so.


Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Carlos Vicente <cvi...@ne...>

Date: Fri, 23 Jan 2009 14:50:53 
To: Support requests/questions about cacti<cac...@li...>
Subject: [cacti-user] performance impact of rebuilding the poller cache


Hi all,

I run a fairly large Cacti installation with about 1,200 devices,
176,000 rrd files (using spine, of course).  I've observed a pattern
that I'm trying to understand.  At first, the poller runtime average
stays under 200 seconds.  Over a period of about three weeks, the poller
runtime starts to slowly increase to close to 300 seconds, to the point
where it can no longer finish within 300 seconds (my polling period),
and graphs start to show gaps.  The first time this happened, I tried a
number of tweaks (number of processes, number of threads per process,
etc) and none of them worked.  Then I manually rebuilt the poller cache,
and bingo! poller stats went back down to under 200 seconds.  This just
happened again today.   The question is, why exactly does this happen? 
>From what I read in the documentation, it doesn't seem like the poller
cache should be out of sync, nor affecting poller performance.

Thanks in advance,

cv

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
cacti-user mailing list
cac...@li...
https://lists.sourceforge.net/lists/listinfo/cacti-user

Hi all,

I run a fairly large Cacti installation with about 1,200 devices,
176,000 rrd files (using spine, of course).  I've observed a pattern
that I'm trying to understand.  At first, the poller runtime average
stays under 200 seconds.  Over a period of about three weeks, the poller
runtime starts to slowly increase to close to 300 seconds, to the point
where it can no longer finish within 300 seconds (my polling period),
and graphs start to show gaps.  The first time this happened, I tried a
number of tweaks (number of processes, number of threads per process,
etc) and none of them worked.  Then I manually rebuilt the poller cache,
and bingo! poller stats went back down to under 200 seconds.  This just
happened again today.   The question is, why exactly does this happen? 
>From what I read in the documentation, it doesn't seem like the poller
cache should be out of sync, nor affecting poller performance.

Thanks in advance,

cv

Hi,


There is a plugin to do this.

Check this thread:

http://forums.cacti.net/viewtopic.php?t=30695&highlight=Aggregate

-Sini

-
On 01/22/2009 10:34:33 AM, hsuan wrote:
> Dear all :
> 
> I have install cacti to receive my router SNMP data. The router have
> open 4
> interfaces.
> 
> Can I shown the 5 minute graph that summarize  the router's interface
> ( 4
> interfaces) traffic data ?
> 
>  
> 
>  
> 
> Best regards,
> 
>  
> 
> Vicky 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
> 

Dear all :

I have install cacti to receive my router SNMP data. The router have open 4
interfaces.

Can I shown the 5 minute graph that summarize  the router's interface ( 4
interfaces) traffic data ?

 

 

Best regards,

 

Vicky 

Dear all :

How can I create a graph that shown traffic in per second、traffic out per
second、Maximal 5 Minute Incoming Traffic、Maximal 5 Minute Outgoing Traffic
?

 

 

Best regards,

Vickyy 

Thank Dave for the feedback!

David Halik wrote:
> That did the trick. Compiled with -O2 under gcc and the buffer overflow 
> is gone.
>
> Thanks for your help!
> -Dave
>
> Larry Adams wrote:
>   
>> Change line 101 in poller.c to the following:
>>
>> char result_string[RESULTS_BUFFER+SMALL_BUFSIZE];
>>
>> Provide feedback.
>>
>> Thanks,
>>
>> Larry
>>
>> David Halik wrote:
>>   
>>     
>>> I think I know what is happening. I recompiled the svn checkout with gcc 
>>> optimization off and it magically worked. Adding optimization back in 
>>> causes it to fail with the same buffer overflow. Autoconf/configure are 
>>> throwing in a compile flag of -O2 which apparently is too much for the 
>>> code and breaks runtime. See the following gdb backtrace with 
>>> optimization on:
>>>
>>> (gdb) where
>>> #0  0x00000032e9830155 in raise () from /lib64/libc.so.6
>>> #1  0x00000032e9831bf0 in abort () from /lib64/libc.so.6
>>> #2  0x00000032e986a38b in __libc_message () from /lib64/libc.so.6
>>> #3  0x00000032e98e578f in __chk_fail () from /lib64/libc.so.6
>>> #4  0x00000032e98e4e9b in __vsnprintf_chk () from /lib64/libc.so.6
>>> #5  0x00000032e98e4d6b in __snprintf_chk () from /lib64/libc.so.6
>>> #6  0x0000000000408471 in poll_host (host_id=21) at poller.c:951
>>> #7  0x0000000000409d73 in child (arg=<value optimized out>) at poller.c:51
>>> #8  0x00000032eac062f7 in start_thread () from /lib64/libpthread.so.0
>>> #9  0x00000032e98d1e3d in clone () from /lib64/libc.so.6
>>>
>>> I'm not sure if line #7 is wrong, but that optimized value could 
>>> definitely be the problem. Either way, the compiler optimization is the 
>>> culprit.
>>>
>>> David Halik wrote:
>>>   
>>>     
>>>       
>>>> I grabbed the SVN checkout and unfortunately it hasn't helped at all:
>>>>
>>>> [root@prick ~]# spine
>>>> SPINE: Using spine config file [/etc/spine.conf]
>>>> SPINE: Version 0.8.7c starting
>>>> *** buffer overflow detected ***: spine terminated
>>>> ======= Backtrace: =========
>>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>>> /lib64/libc.so.6[0x32e98e4e9b]
>>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>>> spine[0x408471]
>>>> spine[0x409d73]
>>>> /lib64/libpthread.so.0[0x32eac062f7]
>>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>>>
>>>> It's definitely working for a second before dying, but the overflow is 
>>>> tripped up everytime:
>>>>
>>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[491] SNMP: v1: 
>>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>>> .1.3.6.1.2.1.2.2.1.10.10, value: 0
>>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[511] SNMP: v1: 
>>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>>> .1.3.6.1.2.1.2.2.1.10.12, value: 0
>>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[521] SNMP: v1: 
>>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>>> .1.3.6.1.2.1.2.2.1.10.13, value: 713544038
>>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[541] SNMP: v1: 
>>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>>> .1.3.6.1.2.1.2.2.1.10.15, value: 0
>>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[571] SNMP: v1: 
>>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>>> .1.3.6.1.2.1.2.2.1.10.18, value: 0
>>>> *** buffer overflow detected ***: spine terminated
>>>>
>>>>
>>>> Tim Eberhard wrote:
>>>>   
>>>>     
>>>>       
>>>>         
>>>>> I originally had that problem with the stable version of Spine on RHEL 5
>>>>> 64bit.
>>>>>
>>>>> Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
>>>>> Try the SVN version of spine and see if that resolves your issue.
>>>>>
>>>>> Good luck,
>>>>>
>>>>> -Tim Eberhard
>>>>>
>>>>> On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:
>>>>>
>>>>>   
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>>>> Hello all,
>>>>>>
>>>>>> Anyone else experiencing this? Google gave a me a few similar bugs from
>>>>>> older versions, but I didn't see any specific fix. I haven't been able
>>>>>> to run spine once without the buffer overflow and core dump. Debug shows
>>>>>> that it runs just fine and then dies at a certain point. I'll paste the
>>>>>> truncated message. If anyone wants the whole thing or any other
>>>>>> debugging please let me know. Any help would be appreciated, thanks.
>>>>>>
>>>>>> System: Centos 5 - 64bit
>>>>>>
>>>>>> [root@prick include]# /usr/bin/spine --verbosity=10
>>>>>> SPINE: Using spine config file [/etc/spine.conf]
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>>> settings WHERE name = 'path_webroot''
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>>> settings WHERE name = 'path_cactilog''
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
>>>>>> variable is /var/www/cacti/script_server.php
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
>>>>>> variable is /var/www/cacti/log/cacti.log
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>>> settings WHERE name = 'log_destination''
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
>>>>>> variable is 3 (SYSLOG)
>>>>>> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>>>> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>>>> was 23, errno was 0, total_time was 7.8678
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
>>>>>> Host is Alive
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>>>> was 23, errno was 0, total_time was 52.9289
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
>>>>>> Host is Alive
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>>>> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>>>> host_id=12'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>>>> host_id=21'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
>>>>>> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
>>>>>> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
>>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
>>>>>> returned the following File Descriptor 9
>>>>>> *** buffer overflow detected ***: /usr/bin/spine terminated
>>>>>> ======= Backtrace: =========
>>>>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>>>>> /lib64/libc.so.6[0x32e98e4e9b]
>>>>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>>>>> /usr/bin/spine[0x40984f]
>>>>>> /usr/bin/spine[0x409b63]
>>>>>> /lib64/libpthread.so.0[0x32eac062f7]
>>>>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>>>>> ======= Memory map: ========
>>>>>> 00400000-00412000 r-xp 00000000 ca:02 709057
>>>>>> /usr/bin/spine
>>>>>> 00611000-00613000 rw-p 00011000 ca:02 709057
>>>>>> /usr/bin/spine
>>>>>> 00613000-00615000 rw-p 00613000 00:00 0
>>>>>> 00812000-00814000 rw-p 00012000 ca:02 709057
>>>>>> /usr/bin/spine
>>>>>> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
>>>>>> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
>>>>>> 41fbe000-429be000 rw-p 41fbe000 00:00 0
>>>>>> 429be000-429bf000 ---p 429be000 00:00 0
>>>>>> 429bf000-433bf000 rw-p 429bf000 00:00 0
>>>>>> 433bf000-433c0000 ---p 433bf000 00:00 0
>>>>>> 433c0000-43dc0000 rw-p 433c0000 00:00 0
>>>>>> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
>>>>>> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
>>>>>> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
>>>>>> /lib64/ld-2.5.so
>>>>>> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
>>>>>> /lib64/ld-2.5.so
>>>>>> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
>>>>>> /lib64/ld-2.5.so
>>>>>> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
>>>>>> /lib64/libc-2.5.so
>>>>>> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
>>>>>> /lib64/libc-2.5.so
>>>>>> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
>>>>>> /lib64/libc-2.5.so
>>>>>> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
>>>>>> /lib64/libc-2.5.so
>>>>>> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
>>>>>> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
>>>>>> /lib64/libdl-2.5.so
>>>>>> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
>>>>>> /lib64/libdl-2.5.so
>>>>>> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
>>>>>> /lib64/libdl-2.5.so
>>>>>> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
>>>>>> /lib64/libdl-2.5.so
>>>>>> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
>>>>>> /lib64/libm-2.5.so
>>>>>> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
>>>>>> /lib64/libm-2.5.so
>>>>>> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
>>>>>> /lib64/libm-2.5.so
>>>>>> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
>>>>>> /lib64/libm-2.5.so
>>>>>> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
>>>>>> /lib64/libselinux.so.1
>>>>>> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
>>>>>> /lib64/libselinux.so.1
>>>>>> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
>>>>>> /lib64/libselinux.so.1
>>>>>> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
>>>>>> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
>>>>>> /lib64/libsepol.so.1
>>>>>> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
>>>>>> /lib64/libsepol.so.1
>>>>>> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
>>>>>> /lib64/libsepol.so.1
>>>>>> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
>>>>>> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
>>>>>> /lib64/libpthread-2.5.so
>>>>>> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
>>>>>> /lib64/libpthread-2.5.so
>>>>>> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
>>>>>> /lib64/libpthread-2.5.so
>>>>>> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
>>>>>> /lib64/libpthread-2.5.so
>>>>>> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
>>>>>> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
>>>>>> /usr/lib64/libz.so.1.2.3
>>>>>> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
>>>>>> /usr/lib64/libz.so.1.2.3
>>>>>> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
>>>>>> /usr/lib64/libz.so.1.2.3
>>>>>> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
>>>>>> /lib64/libnsl-2.5.so
>>>>>> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
>>>>>> /lib64/libnsl-2.5.so
>>>>>> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
>>>>>> /lib64/libnsl-2.5.so
>>>>>> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
>>>>>> /lib64/libnsl-2.5.so
>>>>>> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
>>>>>> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
>>>>>> /lib64/libresolv-2.5.so
>>>>>> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
>>>>>> /lib64/libresolv-2.5.so
>>>>>> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
>>>>>> /lib64/libresolv-2.5.so
>>>>>> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
>>>>>> /lib64/libresolv-2.5.so
>>>>>> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
>>>>>> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
>>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>>> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
>>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>>> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
>>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>>> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
>>>>>> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
>>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>>> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
>>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>>> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
>>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>>> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
>>>>>> /lib64/libcrypto.so.0.9.8b
>>>>>> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
>>>>>> /lib64/libcrypto.so.0.9.8b
>>>>>> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
>>>>>> /lib64/libcrypto.so.0.9.8b
>>>>>> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
>>>>>> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
>>>>>> /lib64/libcom_err.so.2.1
>>>>>> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
>>>>>> /lib64/libcom_err.so.2.1
>>>>>> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
>>>>>> /lib64/libcom_err.so.2.1
>>>>>> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
>>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>>> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
>>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>>> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
>>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>>> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
>>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>>> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
>>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>>> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
>>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>>> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
>>>>>> /usr/lib64/libkrb5.so.3.3
>>>>>> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
>>>>>> /usr/lib64/libkrb5.so.3.3
>>>>>> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
>>>>>> /usr/lib64/libkrb5.so.3.3
>>>>>> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
>>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>>> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
>>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>>> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
>>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>>> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
>>>>>> /lib64/libkeyutils-1.2.so
>>>>>> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
>>>>>> /lib64/libkeyutils-1.2.so
>>>>>> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
>>>>>> /lib64/libkeyutils-1.2.so
>>>>>> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
>>>>>> /lib64/libssl.so.0.9.8b
>>>>>> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
>>>>>> /lib64/libssl.so.0.9.8b
>>>>>> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
>>>>>> /lib64/libssl.so.0.9.8b
>>>>>> 339c000000-339c009000 r-xp 00000000 ca:02 244682
>>>>>> /lib64/libcrypt-2.5.so
>>>>>> 339c009000-339c208000 ---p 00009000 ca:02 244682
>>>>>> /lib64/libcrypt-2.5.so
>>>>>> 339c208000-339c209000 r--p 00008000 ca:02 244682
>>>>>> /lib64/libcrypt-2.5.so
>>>>>> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
>>>>>> /lib64/libcrypt-2.5.so
>>>>>> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
>>>>>> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
>>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>>> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
>>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>>> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
>>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>>> 339c773000-339c774000 rw-p 339c773000 00:00 0
>>>>>> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
>>>>>> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
>>>>>> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
>>>>>> /lib64/libnss_files-2.5.so
>>>>>> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
>>>>>> /lib64/libnss_files-2.5.so
>>>>>> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
>>>>>> /lib64/libnss_files-2.5.so
>>>>>> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
>>>>>> /lib64/libnss_files-2.5.so
>>>>>> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
>>>>>> /usr/lib/locale/locale-archive
>>>>>> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
>>>>>> [stack]
>>>>>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>>>>>> [vdso]
>>>>>> Aborted (core dumped)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> ================================
>>>>>> David Halik
>>>>>> System Administrator
>>>>>> OIT-CSS Rutgers University
>>>>>> dh...@jl...
>>>>>> ================================
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> This SF.net email is sponsored by:
>>>>>> SourcForge Community
>>>>>> SourceForge wants to tell your story.
>>>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>>>> _______________________________________________
>>>>>> cacti-user mailing list
>>>>>> cac...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>>>>
>>>>>>     
>>>>>>       
>>>>>>         
>>>>>>           
>>>>>>             
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by:
>>>>> SourcForge Community
>>>>> SourceForge wants to tell your story.
>>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>>> _______________________________________________
>>>>> cacti-user mailing list
>>>>> cac...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>>>   
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>>   
>>>>     
>>>>       
>>>>         
>>>   
>>>     
>>>       
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> cacti-user mailing list
>> cac...@li...
>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>   
>>     
>
>
>   

That did the trick. Compiled with -O2 under gcc and the buffer overflow 
is gone.

Thanks for your help!
-Dave

Larry Adams wrote:
> Change line 101 in poller.c to the following:
>
> char result_string[RESULTS_BUFFER+SMALL_BUFSIZE];
>
> Provide feedback.
>
> Thanks,
>
> Larry
>
> David Halik wrote:
>   
>> I think I know what is happening. I recompiled the svn checkout with gcc 
>> optimization off and it magically worked. Adding optimization back in 
>> causes it to fail with the same buffer overflow. Autoconf/configure are 
>> throwing in a compile flag of -O2 which apparently is too much for the 
>> code and breaks runtime. See the following gdb backtrace with 
>> optimization on:
>>
>> (gdb) where
>> #0  0x00000032e9830155 in raise () from /lib64/libc.so.6
>> #1  0x00000032e9831bf0 in abort () from /lib64/libc.so.6
>> #2  0x00000032e986a38b in __libc_message () from /lib64/libc.so.6
>> #3  0x00000032e98e578f in __chk_fail () from /lib64/libc.so.6
>> #4  0x00000032e98e4e9b in __vsnprintf_chk () from /lib64/libc.so.6
>> #5  0x00000032e98e4d6b in __snprintf_chk () from /lib64/libc.so.6
>> #6  0x0000000000408471 in poll_host (host_id=21) at poller.c:951
>> #7  0x0000000000409d73 in child (arg=<value optimized out>) at poller.c:51
>> #8  0x00000032eac062f7 in start_thread () from /lib64/libpthread.so.0
>> #9  0x00000032e98d1e3d in clone () from /lib64/libc.so.6
>>
>> I'm not sure if line #7 is wrong, but that optimized value could 
>> definitely be the problem. Either way, the compiler optimization is the 
>> culprit.
>>
>> David Halik wrote:
>>   
>>     
>>> I grabbed the SVN checkout and unfortunately it hasn't helped at all:
>>>
>>> [root@prick ~]# spine
>>> SPINE: Using spine config file [/etc/spine.conf]
>>> SPINE: Version 0.8.7c starting
>>> *** buffer overflow detected ***: spine terminated
>>> ======= Backtrace: =========
>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>> /lib64/libc.so.6[0x32e98e4e9b]
>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>> spine[0x408471]
>>> spine[0x409d73]
>>> /lib64/libpthread.so.0[0x32eac062f7]
>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>>
>>> It's definitely working for a second before dying, but the overflow is 
>>> tripped up everytime:
>>>
>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[491] SNMP: v1: 
>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>> .1.3.6.1.2.1.2.2.1.10.10, value: 0
>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[511] SNMP: v1: 
>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>> .1.3.6.1.2.1.2.2.1.10.12, value: 0
>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[521] SNMP: v1: 
>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>> .1.3.6.1.2.1.2.2.1.10.13, value: 713544038
>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[541] SNMP: v1: 
>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>> .1.3.6.1.2.1.2.2.1.10.15, value: 0
>>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[571] SNMP: v1: 
>>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>>> .1.3.6.1.2.1.2.2.1.10.18, value: 0
>>> *** buffer overflow detected ***: spine terminated
>>>
>>>
>>> Tim Eberhard wrote:
>>>   
>>>     
>>>       
>>>> I originally had that problem with the stable version of Spine on RHEL 5
>>>> 64bit.
>>>>
>>>> Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
>>>> Try the SVN version of spine and see if that resolves your issue.
>>>>
>>>> Good luck,
>>>>
>>>> -Tim Eberhard
>>>>
>>>> On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:
>>>>
>>>>   
>>>>     
>>>>       
>>>>         
>>>>> Hello all,
>>>>>
>>>>> Anyone else experiencing this? Google gave a me a few similar bugs from
>>>>> older versions, but I didn't see any specific fix. I haven't been able
>>>>> to run spine once without the buffer overflow and core dump. Debug shows
>>>>> that it runs just fine and then dies at a certain point. I'll paste the
>>>>> truncated message. If anyone wants the whole thing or any other
>>>>> debugging please let me know. Any help would be appreciated, thanks.
>>>>>
>>>>> System: Centos 5 - 64bit
>>>>>
>>>>> [root@prick include]# /usr/bin/spine --verbosity=10
>>>>> SPINE: Using spine config file [/etc/spine.conf]
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>> settings WHERE name = 'path_webroot''
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>> settings WHERE name = 'path_cactilog''
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
>>>>> variable is /var/www/cacti/script_server.php
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
>>>>> variable is /var/www/cacti/log/cacti.log
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>>> settings WHERE name = 'log_destination''
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
>>>>> variable is 3 (SYSLOG)
>>>>> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>>> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>>> was 23, errno was 0, total_time was 7.8678
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
>>>>> Host is Alive
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>>> was 23, errno was 0, total_time was 52.9289
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
>>>>> Host is Alive
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>>> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>>> host_id=12'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>>> host_id=21'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
>>>>> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
>>>>> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
>>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
>>>>> returned the following File Descriptor 9
>>>>> *** buffer overflow detected ***: /usr/bin/spine terminated
>>>>> ======= Backtrace: =========
>>>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>>>> /lib64/libc.so.6[0x32e98e4e9b]
>>>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>>>> /usr/bin/spine[0x40984f]
>>>>> /usr/bin/spine[0x409b63]
>>>>> /lib64/libpthread.so.0[0x32eac062f7]
>>>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>>>> ======= Memory map: ========
>>>>> 00400000-00412000 r-xp 00000000 ca:02 709057
>>>>> /usr/bin/spine
>>>>> 00611000-00613000 rw-p 00011000 ca:02 709057
>>>>> /usr/bin/spine
>>>>> 00613000-00615000 rw-p 00613000 00:00 0
>>>>> 00812000-00814000 rw-p 00012000 ca:02 709057
>>>>> /usr/bin/spine
>>>>> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
>>>>> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
>>>>> 41fbe000-429be000 rw-p 41fbe000 00:00 0
>>>>> 429be000-429bf000 ---p 429be000 00:00 0
>>>>> 429bf000-433bf000 rw-p 429bf000 00:00 0
>>>>> 433bf000-433c0000 ---p 433bf000 00:00 0
>>>>> 433c0000-43dc0000 rw-p 433c0000 00:00 0
>>>>> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
>>>>> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
>>>>> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
>>>>> /lib64/ld-2.5.so
>>>>> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
>>>>> /lib64/ld-2.5.so
>>>>> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
>>>>> /lib64/ld-2.5.so
>>>>> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
>>>>> /lib64/libc-2.5.so
>>>>> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
>>>>> /lib64/libc-2.5.so
>>>>> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
>>>>> /lib64/libc-2.5.so
>>>>> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
>>>>> /lib64/libc-2.5.so
>>>>> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
>>>>> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
>>>>> /lib64/libdl-2.5.so
>>>>> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
>>>>> /lib64/libdl-2.5.so
>>>>> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
>>>>> /lib64/libdl-2.5.so
>>>>> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
>>>>> /lib64/libdl-2.5.so
>>>>> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
>>>>> /lib64/libm-2.5.so
>>>>> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
>>>>> /lib64/libm-2.5.so
>>>>> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
>>>>> /lib64/libm-2.5.so
>>>>> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
>>>>> /lib64/libm-2.5.so
>>>>> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
>>>>> /lib64/libselinux.so.1
>>>>> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
>>>>> /lib64/libselinux.so.1
>>>>> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
>>>>> /lib64/libselinux.so.1
>>>>> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
>>>>> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
>>>>> /lib64/libsepol.so.1
>>>>> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
>>>>> /lib64/libsepol.so.1
>>>>> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
>>>>> /lib64/libsepol.so.1
>>>>> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
>>>>> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
>>>>> /lib64/libpthread-2.5.so
>>>>> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
>>>>> /lib64/libpthread-2.5.so
>>>>> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
>>>>> /lib64/libpthread-2.5.so
>>>>> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
>>>>> /lib64/libpthread-2.5.so
>>>>> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
>>>>> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
>>>>> /usr/lib64/libz.so.1.2.3
>>>>> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
>>>>> /usr/lib64/libz.so.1.2.3
>>>>> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
>>>>> /usr/lib64/libz.so.1.2.3
>>>>> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
>>>>> /lib64/libnsl-2.5.so
>>>>> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
>>>>> /lib64/libnsl-2.5.so
>>>>> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
>>>>> /lib64/libnsl-2.5.so
>>>>> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
>>>>> /lib64/libnsl-2.5.so
>>>>> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
>>>>> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
>>>>> /lib64/libresolv-2.5.so
>>>>> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
>>>>> /lib64/libresolv-2.5.so
>>>>> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
>>>>> /lib64/libresolv-2.5.so
>>>>> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
>>>>> /lib64/libresolv-2.5.so
>>>>> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
>>>>> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
>>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>>> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
>>>>> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
>>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>>> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
>>>>> /lib64/libcrypto.so.0.9.8b
>>>>> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
>>>>> /lib64/libcrypto.so.0.9.8b
>>>>> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
>>>>> /lib64/libcrypto.so.0.9.8b
>>>>> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
>>>>> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
>>>>> /lib64/libcom_err.so.2.1
>>>>> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
>>>>> /lib64/libcom_err.so.2.1
>>>>> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
>>>>> /lib64/libcom_err.so.2.1
>>>>> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
>>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>>> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
>>>>> /usr/lib64/libkrb5support.so.0.1
>>>>> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
>>>>> /usr/lib64/libkrb5.so.3.3
>>>>> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
>>>>> /usr/lib64/libkrb5.so.3.3
>>>>> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
>>>>> /usr/lib64/libkrb5.so.3.3
>>>>> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
>>>>> /usr/lib64/libk5crypto.so.3.1
>>>>> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
>>>>> /lib64/libkeyutils-1.2.so
>>>>> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
>>>>> /lib64/libkeyutils-1.2.so
>>>>> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
>>>>> /lib64/libkeyutils-1.2.so
>>>>> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
>>>>> /lib64/libssl.so.0.9.8b
>>>>> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
>>>>> /lib64/libssl.so.0.9.8b
>>>>> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
>>>>> /lib64/libssl.so.0.9.8b
>>>>> 339c000000-339c009000 r-xp 00000000 ca:02 244682
>>>>> /lib64/libcrypt-2.5.so
>>>>> 339c009000-339c208000 ---p 00009000 ca:02 244682
>>>>> /lib64/libcrypt-2.5.so
>>>>> 339c208000-339c209000 r--p 00008000 ca:02 244682
>>>>> /lib64/libcrypt-2.5.so
>>>>> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
>>>>> /lib64/libcrypt-2.5.so
>>>>> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
>>>>> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
>>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>>> 339c773000-339c774000 rw-p 339c773000 00:00 0
>>>>> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
>>>>> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
>>>>> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
>>>>> /lib64/libnss_files-2.5.so
>>>>> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
>>>>> /lib64/libnss_files-2.5.so
>>>>> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
>>>>> /lib64/libnss_files-2.5.so
>>>>> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
>>>>> /lib64/libnss_files-2.5.so
>>>>> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
>>>>> /usr/lib/locale/locale-archive
>>>>> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
>>>>> [stack]
>>>>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>>>>> [vdso]
>>>>> Aborted (core dumped)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ================================
>>>>> David Halik
>>>>> System Administrator
>>>>> OIT-CSS Rutgers University
>>>>> dh...@jl...
>>>>> ================================
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> This SF.net email is sponsored by:
>>>>> SourcForge Community
>>>>> SourceForge wants to tell your story.
>>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>>> _______________________________________________
>>>>> cacti-user mailing list
>>>>> cac...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>>>
>>>>>     
>>>>>       
>>>>>         
>>>>>           
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by:
>>>> SourcForge Community
>>>> SourceForge wants to tell your story.
>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>> _______________________________________________
>>>> cacti-user mailing list
>>>> cac...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>>   
>>>>     
>>>>       
>>>>         
>>>   
>>>     
>>>       
>>   
>>     
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
>   


-- 
================================
David Halik
System Administrator
OIT-CSS Rutgers University
dh...@jl...
================================

Hi Vicky, list,

I think that's not possible. At least implementing an automation to do it.

But what do you think would be the benefit of such a graph? The timeline
would be the greatest available - the yearly one. Would you like to see the
monthly part as a shorter graph (approx. 1/12 of the yearly one)?

Remember the collected data in the used RRD will most likely be condensed in
several RRAs and if you'd like daily data over the last year you'd need a
rra providing such data.

Don't know if this really helps but would like to hear from you regarding
the mentioned benefit.

Regards,
Marcel

On Wed, Jan 21, 2009 at 3:04 AM, hsuan <hs...@nc...> wrote:

> Hi all :
>
> In cacti the daily/weekly/monthly/yearly traffic data are represent four
> graph. Is it possible to present daily/weekly/monthly/yearly traffic data
> in
> a graph ?
>
>
>
>
>
> Best regard,
>
> Vicky
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
>

Hi all :

In cacti the daily/weekly/monthly/yearly traffic data are represent four
graph. Is it possible to present daily/weekly/monthly/yearly traffic data in
a graph ?

 

 

Best regard,

Vicky 

Change line 101 in poller.c to the following:

char result_string[RESULTS_BUFFER+SMALL_BUFSIZE];

Provide feedback.

Thanks,

Larry

David Halik wrote:
> I think I know what is happening. I recompiled the svn checkout with gcc 
> optimization off and it magically worked. Adding optimization back in 
> causes it to fail with the same buffer overflow. Autoconf/configure are 
> throwing in a compile flag of -O2 which apparently is too much for the 
> code and breaks runtime. See the following gdb backtrace with 
> optimization on:
>
> (gdb) where
> #0  0x00000032e9830155 in raise () from /lib64/libc.so.6
> #1  0x00000032e9831bf0 in abort () from /lib64/libc.so.6
> #2  0x00000032e986a38b in __libc_message () from /lib64/libc.so.6
> #3  0x00000032e98e578f in __chk_fail () from /lib64/libc.so.6
> #4  0x00000032e98e4e9b in __vsnprintf_chk () from /lib64/libc.so.6
> #5  0x00000032e98e4d6b in __snprintf_chk () from /lib64/libc.so.6
> #6  0x0000000000408471 in poll_host (host_id=21) at poller.c:951
> #7  0x0000000000409d73 in child (arg=<value optimized out>) at poller.c:51
> #8  0x00000032eac062f7 in start_thread () from /lib64/libpthread.so.0
> #9  0x00000032e98d1e3d in clone () from /lib64/libc.so.6
>
> I'm not sure if line #7 is wrong, but that optimized value could 
> definitely be the problem. Either way, the compiler optimization is the 
> culprit.
>
> David Halik wrote:
>   
>> I grabbed the SVN checkout and unfortunately it hasn't helped at all:
>>
>> [root@prick ~]# spine
>> SPINE: Using spine config file [/etc/spine.conf]
>> SPINE: Version 0.8.7c starting
>> *** buffer overflow detected ***: spine terminated
>> ======= Backtrace: =========
>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>> /lib64/libc.so.6[0x32e98e4e9b]
>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>> spine[0x408471]
>> spine[0x409d73]
>> /lib64/libpthread.so.0[0x32eac062f7]
>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>
>> It's definitely working for a second before dying, but the overflow is 
>> tripped up everytime:
>>
>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[491] SNMP: v1: 
>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>> .1.3.6.1.2.1.2.2.1.10.10, value: 0
>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[511] SNMP: v1: 
>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>> .1.3.6.1.2.1.2.2.1.10.12, value: 0
>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[521] SNMP: v1: 
>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>> .1.3.6.1.2.1.2.2.1.10.13, value: 713544038
>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[541] SNMP: v1: 
>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>> .1.3.6.1.2.1.2.2.1.10.15, value: 0
>> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[571] SNMP: v1: 
>> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
>> .1.3.6.1.2.1.2.2.1.10.18, value: 0
>> *** buffer overflow detected ***: spine terminated
>>
>>
>> Tim Eberhard wrote:
>>   
>>     
>>> I originally had that problem with the stable version of Spine on RHEL 5
>>> 64bit.
>>>
>>> Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
>>> Try the SVN version of spine and see if that resolves your issue.
>>>
>>> Good luck,
>>>
>>> -Tim Eberhard
>>>
>>> On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:
>>>
>>>   
>>>     
>>>       
>>>> Hello all,
>>>>
>>>> Anyone else experiencing this? Google gave a me a few similar bugs from
>>>> older versions, but I didn't see any specific fix. I haven't been able
>>>> to run spine once without the buffer overflow and core dump. Debug shows
>>>> that it runs just fine and then dies at a certain point. I'll paste the
>>>> truncated message. If anyone wants the whole thing or any other
>>>> debugging please let me know. Any help would be appreciated, thanks.
>>>>
>>>> System: Centos 5 - 64bit
>>>>
>>>> [root@prick include]# /usr/bin/spine --verbosity=10
>>>> SPINE: Using spine config file [/etc/spine.conf]
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>> settings WHERE name = 'path_webroot''
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>> settings WHERE name = 'path_cactilog''
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
>>>> variable is /var/www/cacti/script_server.php
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
>>>> variable is /var/www/cacti/log/cacti.log
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>>> settings WHERE name = 'log_destination''
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
>>>> variable is 3 (SYSLOG)
>>>> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>> was 23, errno was 0, total_time was 7.8678
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
>>>> Host is Alive
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>>> was 23, errno was 0, total_time was 52.9289
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
>>>> Host is Alive
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>>> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>> host_id=12'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>>> host_id=21'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
>>>> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
>>>> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
>>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
>>>> returned the following File Descriptor 9
>>>> *** buffer overflow detected ***: /usr/bin/spine terminated
>>>> ======= Backtrace: =========
>>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>>> /lib64/libc.so.6[0x32e98e4e9b]
>>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>>> /usr/bin/spine[0x40984f]
>>>> /usr/bin/spine[0x409b63]
>>>> /lib64/libpthread.so.0[0x32eac062f7]
>>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>>> ======= Memory map: ========
>>>> 00400000-00412000 r-xp 00000000 ca:02 709057
>>>> /usr/bin/spine
>>>> 00611000-00613000 rw-p 00011000 ca:02 709057
>>>> /usr/bin/spine
>>>> 00613000-00615000 rw-p 00613000 00:00 0
>>>> 00812000-00814000 rw-p 00012000 ca:02 709057
>>>> /usr/bin/spine
>>>> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
>>>> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
>>>> 41fbe000-429be000 rw-p 41fbe000 00:00 0
>>>> 429be000-429bf000 ---p 429be000 00:00 0
>>>> 429bf000-433bf000 rw-p 429bf000 00:00 0
>>>> 433bf000-433c0000 ---p 433bf000 00:00 0
>>>> 433c0000-43dc0000 rw-p 433c0000 00:00 0
>>>> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
>>>> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
>>>> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
>>>> /lib64/ld-2.5.so
>>>> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
>>>> /lib64/ld-2.5.so
>>>> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
>>>> /lib64/ld-2.5.so
>>>> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
>>>> /lib64/libc-2.5.so
>>>> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
>>>> /lib64/libc-2.5.so
>>>> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
>>>> /lib64/libc-2.5.so
>>>> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
>>>> /lib64/libc-2.5.so
>>>> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
>>>> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
>>>> /lib64/libdl-2.5.so
>>>> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
>>>> /lib64/libdl-2.5.so
>>>> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
>>>> /lib64/libdl-2.5.so
>>>> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
>>>> /lib64/libdl-2.5.so
>>>> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
>>>> /lib64/libm-2.5.so
>>>> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
>>>> /lib64/libm-2.5.so
>>>> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
>>>> /lib64/libm-2.5.so
>>>> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
>>>> /lib64/libm-2.5.so
>>>> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
>>>> /lib64/libselinux.so.1
>>>> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
>>>> /lib64/libselinux.so.1
>>>> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
>>>> /lib64/libselinux.so.1
>>>> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
>>>> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
>>>> /lib64/libsepol.so.1
>>>> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
>>>> /lib64/libsepol.so.1
>>>> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
>>>> /lib64/libsepol.so.1
>>>> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
>>>> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
>>>> /lib64/libpthread-2.5.so
>>>> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
>>>> /lib64/libpthread-2.5.so
>>>> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
>>>> /lib64/libpthread-2.5.so
>>>> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
>>>> /lib64/libpthread-2.5.so
>>>> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
>>>> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
>>>> /usr/lib64/libz.so.1.2.3
>>>> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
>>>> /usr/lib64/libz.so.1.2.3
>>>> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
>>>> /usr/lib64/libz.so.1.2.3
>>>> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
>>>> /lib64/libnsl-2.5.so
>>>> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
>>>> /lib64/libnsl-2.5.so
>>>> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
>>>> /lib64/libnsl-2.5.so
>>>> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
>>>> /lib64/libnsl-2.5.so
>>>> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
>>>> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
>>>> /lib64/libresolv-2.5.so
>>>> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
>>>> /lib64/libresolv-2.5.so
>>>> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
>>>> /lib64/libresolv-2.5.so
>>>> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
>>>> /lib64/libresolv-2.5.so
>>>> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
>>>> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
>>>> /usr/lib64/libnetsnmp.so.10.0.1
>>>> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
>>>> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
>>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>>> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
>>>> /lib64/libcrypto.so.0.9.8b
>>>> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
>>>> /lib64/libcrypto.so.0.9.8b
>>>> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
>>>> /lib64/libcrypto.so.0.9.8b
>>>> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
>>>> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
>>>> /lib64/libcom_err.so.2.1
>>>> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
>>>> /lib64/libcom_err.so.2.1
>>>> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
>>>> /lib64/libcom_err.so.2.1
>>>> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
>>>> /usr/lib64/libgssapi_krb5.so.2.2
>>>> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
>>>> /usr/lib64/libkrb5support.so.0.1
>>>> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
>>>> /usr/lib64/libkrb5support.so.0.1
>>>> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
>>>> /usr/lib64/libkrb5support.so.0.1
>>>> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
>>>> /usr/lib64/libkrb5.so.3.3
>>>> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
>>>> /usr/lib64/libkrb5.so.3.3
>>>> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
>>>> /usr/lib64/libkrb5.so.3.3
>>>> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
>>>> /usr/lib64/libk5crypto.so.3.1
>>>> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
>>>> /usr/lib64/libk5crypto.so.3.1
>>>> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
>>>> /usr/lib64/libk5crypto.so.3.1
>>>> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
>>>> /lib64/libkeyutils-1.2.so
>>>> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
>>>> /lib64/libkeyutils-1.2.so
>>>> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
>>>> /lib64/libkeyutils-1.2.so
>>>> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
>>>> /lib64/libssl.so.0.9.8b
>>>> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
>>>> /lib64/libssl.so.0.9.8b
>>>> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
>>>> /lib64/libssl.so.0.9.8b
>>>> 339c000000-339c009000 r-xp 00000000 ca:02 244682
>>>> /lib64/libcrypt-2.5.so
>>>> 339c009000-339c208000 ---p 00009000 ca:02 244682
>>>> /lib64/libcrypt-2.5.so
>>>> 339c208000-339c209000 r--p 00008000 ca:02 244682
>>>> /lib64/libcrypt-2.5.so
>>>> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
>>>> /lib64/libcrypt-2.5.so
>>>> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
>>>> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
>>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>>> 339c773000-339c774000 rw-p 339c773000 00:00 0
>>>> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
>>>> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
>>>> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
>>>> /lib64/libnss_files-2.5.so
>>>> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
>>>> /lib64/libnss_files-2.5.so
>>>> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
>>>> /lib64/libnss_files-2.5.so
>>>> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
>>>> /lib64/libnss_files-2.5.so
>>>> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
>>>> /usr/lib/locale/locale-archive
>>>> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
>>>> [stack]
>>>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>>>> [vdso]
>>>> Aborted (core dumped)
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> ================================
>>>> David Halik
>>>> System Administrator
>>>> OIT-CSS Rutgers University
>>>> dh...@jl...
>>>> ================================
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> This SF.net email is sponsored by:
>>>> SourcForge Community
>>>> SourceForge wants to tell your story.
>>>> http://p.sf.net/sfu/sf-spreadtheword
>>>> _______________________________________________
>>>> cacti-user mailing list
>>>> cac...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>>
>>>>     
>>>>       
>>>>         
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> cacti-user mailing list
>>> cac...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>   
>>>     
>>>       
>>   
>>     
>
>
>   

I think I know what is happening. I recompiled the svn checkout with gcc 
optimization off and it magically worked. Adding optimization back in 
causes it to fail with the same buffer overflow. Autoconf/configure are 
throwing in a compile flag of -O2 which apparently is too much for the 
code and breaks runtime. See the following gdb backtrace with 
optimization on:

(gdb) where
#0  0x00000032e9830155 in raise () from /lib64/libc.so.6
#1  0x00000032e9831bf0 in abort () from /lib64/libc.so.6
#2  0x00000032e986a38b in __libc_message () from /lib64/libc.so.6
#3  0x00000032e98e578f in __chk_fail () from /lib64/libc.so.6
#4  0x00000032e98e4e9b in __vsnprintf_chk () from /lib64/libc.so.6
#5  0x00000032e98e4d6b in __snprintf_chk () from /lib64/libc.so.6
#6  0x0000000000408471 in poll_host (host_id=21) at poller.c:951
#7  0x0000000000409d73 in child (arg=<value optimized out>) at poller.c:51
#8  0x00000032eac062f7 in start_thread () from /lib64/libpthread.so.0
#9  0x00000032e98d1e3d in clone () from /lib64/libc.so.6

I'm not sure if line #7 is wrong, but that optimized value could 
definitely be the problem. Either way, the compiler optimization is the 
culprit.

David Halik wrote:
> I grabbed the SVN checkout and unfortunately it hasn't helped at all:
>
> [root@prick ~]# spine
> SPINE: Using spine config file [/etc/spine.conf]
> SPINE: Version 0.8.7c starting
> *** buffer overflow detected ***: spine terminated
> ======= Backtrace: =========
> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
> /lib64/libc.so.6[0x32e98e4e9b]
> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
> spine[0x408471]
> spine[0x409d73]
> /lib64/libpthread.so.0[0x32eac062f7]
> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>
> It's definitely working for a second before dying, but the overflow is 
> tripped up everytime:
>
> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[491] SNMP: v1: 
> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
> .1.3.6.1.2.1.2.2.1.10.10, value: 0
> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[511] SNMP: v1: 
> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
> .1.3.6.1.2.1.2.2.1.10.12, value: 0
> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[521] SNMP: v1: 
> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
> .1.3.6.1.2.1.2.2.1.10.13, value: 713544038
> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[541] SNMP: v1: 
> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
> .1.3.6.1.2.1.2.2.1.10.15, value: 0
> 01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[571] SNMP: v1: 
> servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
> .1.3.6.1.2.1.2.2.1.10.18, value: 0
> *** buffer overflow detected ***: spine terminated
>
>
> Tim Eberhard wrote:
>   
>> I originally had that problem with the stable version of Spine on RHEL 5
>> 64bit.
>>
>> Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
>> Try the SVN version of spine and see if that resolves your issue.
>>
>> Good luck,
>>
>> -Tim Eberhard
>>
>> On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:
>>
>>   
>>     
>>> Hello all,
>>>
>>> Anyone else experiencing this? Google gave a me a few similar bugs from
>>> older versions, but I didn't see any specific fix. I haven't been able
>>> to run spine once without the buffer overflow and core dump. Debug shows
>>> that it runs just fine and then dies at a certain point. I'll paste the
>>> truncated message. If anyone wants the whole thing or any other
>>> debugging please let me know. Any help would be appreciated, thanks.
>>>
>>> System: Centos 5 - 64bit
>>>
>>> [root@prick include]# /usr/bin/spine --verbosity=10
>>> SPINE: Using spine config file [/etc/spine.conf]
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>> settings WHERE name = 'path_webroot''
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>> settings WHERE name = 'path_cactilog''
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
>>> variable is /var/www/cacti/script_server.php
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
>>> variable is /var/www/cacti/log/cacti.log
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>>> settings WHERE name = 'log_destination''
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
>>> variable is 3 (SYSLOG)
>>> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>> was 23, errno was 0, total_time was 7.8678
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
>>> Host is Alive
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>>> was 23, errno was 0, total_time was 52.9289
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
>>> Host is Alive
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>>> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>> host_id=12'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>>> host_id=21'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
>>> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
>>> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
>>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
>>> returned the following File Descriptor 9
>>> *** buffer overflow detected ***: /usr/bin/spine terminated
>>> ======= Backtrace: =========
>>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>>> /lib64/libc.so.6[0x32e98e4e9b]
>>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>>> /usr/bin/spine[0x40984f]
>>> /usr/bin/spine[0x409b63]
>>> /lib64/libpthread.so.0[0x32eac062f7]
>>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>>> ======= Memory map: ========
>>> 00400000-00412000 r-xp 00000000 ca:02 709057
>>> /usr/bin/spine
>>> 00611000-00613000 rw-p 00011000 ca:02 709057
>>> /usr/bin/spine
>>> 00613000-00615000 rw-p 00613000 00:00 0
>>> 00812000-00814000 rw-p 00012000 ca:02 709057
>>> /usr/bin/spine
>>> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
>>> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
>>> 41fbe000-429be000 rw-p 41fbe000 00:00 0
>>> 429be000-429bf000 ---p 429be000 00:00 0
>>> 429bf000-433bf000 rw-p 429bf000 00:00 0
>>> 433bf000-433c0000 ---p 433bf000 00:00 0
>>> 433c0000-43dc0000 rw-p 433c0000 00:00 0
>>> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
>>> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
>>> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
>>> /lib64/ld-2.5.so
>>> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
>>> /lib64/ld-2.5.so
>>> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
>>> /lib64/ld-2.5.so
>>> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
>>> /lib64/libc-2.5.so
>>> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
>>> /lib64/libc-2.5.so
>>> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
>>> /lib64/libc-2.5.so
>>> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
>>> /lib64/libc-2.5.so
>>> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
>>> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
>>> /lib64/libdl-2.5.so
>>> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
>>> /lib64/libdl-2.5.so
>>> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
>>> /lib64/libdl-2.5.so
>>> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
>>> /lib64/libdl-2.5.so
>>> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
>>> /lib64/libm-2.5.so
>>> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
>>> /lib64/libm-2.5.so
>>> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
>>> /lib64/libm-2.5.so
>>> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
>>> /lib64/libm-2.5.so
>>> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
>>> /lib64/libselinux.so.1
>>> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
>>> /lib64/libselinux.so.1
>>> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
>>> /lib64/libselinux.so.1
>>> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
>>> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
>>> /lib64/libsepol.so.1
>>> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
>>> /lib64/libsepol.so.1
>>> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
>>> /lib64/libsepol.so.1
>>> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
>>> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
>>> /lib64/libpthread-2.5.so
>>> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
>>> /lib64/libpthread-2.5.so
>>> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
>>> /lib64/libpthread-2.5.so
>>> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
>>> /lib64/libpthread-2.5.so
>>> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
>>> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
>>> /usr/lib64/libz.so.1.2.3
>>> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
>>> /usr/lib64/libz.so.1.2.3
>>> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
>>> /usr/lib64/libz.so.1.2.3
>>> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
>>> /lib64/libnsl-2.5.so
>>> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
>>> /lib64/libnsl-2.5.so
>>> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
>>> /lib64/libnsl-2.5.so
>>> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
>>> /lib64/libnsl-2.5.so
>>> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
>>> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
>>> /lib64/libresolv-2.5.so
>>> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
>>> /lib64/libresolv-2.5.so
>>> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
>>> /lib64/libresolv-2.5.so
>>> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
>>> /lib64/libresolv-2.5.so
>>> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
>>> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
>>> /usr/lib64/libnetsnmp.so.10.0.1
>>> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
>>> /usr/lib64/libnetsnmp.so.10.0.1
>>> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
>>> /usr/lib64/libnetsnmp.so.10.0.1
>>> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
>>> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
>>> /lib64/libgcc_s-4.1.2-20080102.so.1
>>> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
>>> /lib64/libcrypto.so.0.9.8b
>>> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
>>> /lib64/libcrypto.so.0.9.8b
>>> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
>>> /lib64/libcrypto.so.0.9.8b
>>> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
>>> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
>>> /lib64/libcom_err.so.2.1
>>> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
>>> /lib64/libcom_err.so.2.1
>>> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
>>> /lib64/libcom_err.so.2.1
>>> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
>>> /usr/lib64/libgssapi_krb5.so.2.2
>>> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
>>> /usr/lib64/libgssapi_krb5.so.2.2
>>> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
>>> /usr/lib64/libgssapi_krb5.so.2.2
>>> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
>>> /usr/lib64/libkrb5support.so.0.1
>>> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
>>> /usr/lib64/libkrb5support.so.0.1
>>> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
>>> /usr/lib64/libkrb5support.so.0.1
>>> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
>>> /usr/lib64/libkrb5.so.3.3
>>> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
>>> /usr/lib64/libkrb5.so.3.3
>>> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
>>> /usr/lib64/libkrb5.so.3.3
>>> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
>>> /usr/lib64/libk5crypto.so.3.1
>>> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
>>> /usr/lib64/libk5crypto.so.3.1
>>> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
>>> /usr/lib64/libk5crypto.so.3.1
>>> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
>>> /lib64/libkeyutils-1.2.so
>>> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
>>> /lib64/libkeyutils-1.2.so
>>> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
>>> /lib64/libkeyutils-1.2.so
>>> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
>>> /lib64/libssl.so.0.9.8b
>>> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
>>> /lib64/libssl.so.0.9.8b
>>> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
>>> /lib64/libssl.so.0.9.8b
>>> 339c000000-339c009000 r-xp 00000000 ca:02 244682
>>> /lib64/libcrypt-2.5.so
>>> 339c009000-339c208000 ---p 00009000 ca:02 244682
>>> /lib64/libcrypt-2.5.so
>>> 339c208000-339c209000 r--p 00008000 ca:02 244682
>>> /lib64/libcrypt-2.5.so
>>> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
>>> /lib64/libcrypt-2.5.so
>>> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
>>> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
>>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>>> 339c773000-339c774000 rw-p 339c773000 00:00 0
>>> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
>>> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
>>> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
>>> /lib64/libnss_files-2.5.so
>>> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
>>> /lib64/libnss_files-2.5.so
>>> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
>>> /lib64/libnss_files-2.5.so
>>> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
>>> /lib64/libnss_files-2.5.so
>>> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
>>> /usr/lib/locale/locale-archive
>>> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
>>> [stack]
>>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>>> [vdso]
>>> Aborted (core dumped)
>>>
>>>
>>>
>>>
>>> --
>>> ================================
>>> David Halik
>>> System Administrator
>>> OIT-CSS Rutgers University
>>> dh...@jl...
>>> ================================
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>> _______________________________________________
>>> cacti-user mailing list
>>> cac...@li...
>>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>>
>>>     
>>>       
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> cacti-user mailing list
>> cac...@li...
>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>   
>>     
>
>
>   


-- 
================================
David Halik
System Administrator
OIT-CSS Rutgers University
dh...@jl...
================================

I grabbed the SVN checkout and unfortunately it hasn't helped at all:

[root@prick ~]# spine
SPINE: Using spine config file [/etc/spine.conf]
SPINE: Version 0.8.7c starting
*** buffer overflow detected ***: spine terminated
======= Backtrace: =========
/lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
/lib64/libc.so.6[0x32e98e4e9b]
/lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
spine[0x408471]
spine[0x409d73]
/lib64/libpthread.so.0[0x32eac062f7]
/lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]

It's definitely working for a second before dying, but the overflow is 
tripped up everytime:

01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[491] SNMP: v1: 
servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
.1.3.6.1.2.1.2.2.1.10.10, value: 0
01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[511] SNMP: v1: 
servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
.1.3.6.1.2.1.2.2.1.10.12, value: 0
01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[521] SNMP: v1: 
servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
.1.3.6.1.2.1.2.2.1.10.13, value: 713544038
01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[541] SNMP: v1: 
servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
.1.3.6.1.2.1.2.2.1.10.15, value: 0
01/20/2009 04:53:38 PM - SPINE: Poller[0] Host[21] DS[571] SNMP: v1: 
servants-sw2.rutgers.edu, dsname: traffic_in, oid: 
.1.3.6.1.2.1.2.2.1.10.18, value: 0
*** buffer overflow detected ***: spine terminated


Tim Eberhard wrote:
> I originally had that problem with the stable version of Spine on RHEL 5
> 64bit.
>
> Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
> Try the SVN version of spine and see if that resolves your issue.
>
> Good luck,
>
> -Tim Eberhard
>
> On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:
>
>   
>> Hello all,
>>
>> Anyone else experiencing this? Google gave a me a few similar bugs from
>> older versions, but I didn't see any specific fix. I haven't been able
>> to run spine once without the buffer overflow and core dump. Debug shows
>> that it runs just fine and then dies at a certain point. I'll paste the
>> truncated message. If anyone wants the whole thing or any other
>> debugging please let me know. Any help would be appreciated, thanks.
>>
>> System: Centos 5 - 64bit
>>
>> [root@prick include]# /usr/bin/spine --verbosity=10
>> SPINE: Using spine config file [/etc/spine.conf]
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>> settings WHERE name = 'path_webroot''
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>> settings WHERE name = 'path_cactilog''
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
>> variable is /var/www/cacti/script_server.php
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
>> variable is /var/www/cacti/log/cacti.log
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
>> settings WHERE name = 'log_destination''
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
>> variable is 3 (SYSLOG)
>> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>> was 23, errno was 0, total_time was 7.8678
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
>> Host is Alive
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
>> was 23, errno was 0, total_time was 52.9289
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
>> Host is Alive
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
>> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>> host_id=12'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
>> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
>> host_id=21'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
>> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
>> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
>> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
>> returned the following File Descriptor 9
>> *** buffer overflow detected ***: /usr/bin/spine terminated
>> ======= Backtrace: =========
>> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
>> /lib64/libc.so.6[0x32e98e4e9b]
>> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
>> /usr/bin/spine[0x40984f]
>> /usr/bin/spine[0x409b63]
>> /lib64/libpthread.so.0[0x32eac062f7]
>> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
>> ======= Memory map: ========
>> 00400000-00412000 r-xp 00000000 ca:02 709057
>> /usr/bin/spine
>> 00611000-00613000 rw-p 00011000 ca:02 709057
>> /usr/bin/spine
>> 00613000-00615000 rw-p 00613000 00:00 0
>> 00812000-00814000 rw-p 00012000 ca:02 709057
>> /usr/bin/spine
>> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
>> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
>> 41fbe000-429be000 rw-p 41fbe000 00:00 0
>> 429be000-429bf000 ---p 429be000 00:00 0
>> 429bf000-433bf000 rw-p 429bf000 00:00 0
>> 433bf000-433c0000 ---p 433bf000 00:00 0
>> 433c0000-43dc0000 rw-p 433c0000 00:00 0
>> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
>> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
>> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
>> /lib64/ld-2.5.so
>> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
>> /lib64/ld-2.5.so
>> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
>> /lib64/ld-2.5.so
>> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
>> /lib64/libc-2.5.so
>> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
>> /lib64/libc-2.5.so
>> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
>> /lib64/libc-2.5.so
>> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
>> /lib64/libc-2.5.so
>> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
>> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
>> /lib64/libdl-2.5.so
>> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
>> /lib64/libdl-2.5.so
>> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
>> /lib64/libdl-2.5.so
>> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
>> /lib64/libdl-2.5.so
>> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
>> /lib64/libm-2.5.so
>> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
>> /lib64/libm-2.5.so
>> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
>> /lib64/libm-2.5.so
>> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
>> /lib64/libm-2.5.so
>> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
>> /lib64/libselinux.so.1
>> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
>> /lib64/libselinux.so.1
>> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
>> /lib64/libselinux.so.1
>> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
>> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
>> /lib64/libsepol.so.1
>> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
>> /lib64/libsepol.so.1
>> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
>> /lib64/libsepol.so.1
>> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
>> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
>> /lib64/libpthread-2.5.so
>> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
>> /lib64/libpthread-2.5.so
>> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
>> /lib64/libpthread-2.5.so
>> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
>> /lib64/libpthread-2.5.so
>> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
>> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
>> /usr/lib64/libz.so.1.2.3
>> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
>> /usr/lib64/libz.so.1.2.3
>> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
>> /usr/lib64/libz.so.1.2.3
>> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
>> /lib64/libnsl-2.5.so
>> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
>> /lib64/libnsl-2.5.so
>> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
>> /lib64/libnsl-2.5.so
>> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
>> /lib64/libnsl-2.5.so
>> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
>> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
>> /lib64/libresolv-2.5.so
>> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
>> /lib64/libresolv-2.5.so
>> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
>> /lib64/libresolv-2.5.so
>> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
>> /lib64/libresolv-2.5.so
>> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
>> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
>> /usr/lib64/libnetsnmp.so.10.0.1
>> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
>> /usr/lib64/libnetsnmp.so.10.0.1
>> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
>> /usr/lib64/libnetsnmp.so.10.0.1
>> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
>> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
>> /lib64/libgcc_s-4.1.2-20080102.so.1
>> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
>> /lib64/libgcc_s-4.1.2-20080102.so.1
>> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
>> /lib64/libgcc_s-4.1.2-20080102.so.1
>> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
>> /lib64/libcrypto.so.0.9.8b
>> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
>> /lib64/libcrypto.so.0.9.8b
>> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
>> /lib64/libcrypto.so.0.9.8b
>> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
>> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
>> /lib64/libcom_err.so.2.1
>> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
>> /lib64/libcom_err.so.2.1
>> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
>> /lib64/libcom_err.so.2.1
>> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
>> /usr/lib64/libgssapi_krb5.so.2.2
>> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
>> /usr/lib64/libgssapi_krb5.so.2.2
>> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
>> /usr/lib64/libgssapi_krb5.so.2.2
>> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
>> /usr/lib64/libkrb5support.so.0.1
>> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
>> /usr/lib64/libkrb5support.so.0.1
>> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
>> /usr/lib64/libkrb5support.so.0.1
>> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
>> /usr/lib64/libkrb5.so.3.3
>> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
>> /usr/lib64/libkrb5.so.3.3
>> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
>> /usr/lib64/libkrb5.so.3.3
>> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
>> /usr/lib64/libk5crypto.so.3.1
>> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
>> /usr/lib64/libk5crypto.so.3.1
>> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
>> /usr/lib64/libk5crypto.so.3.1
>> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
>> /lib64/libkeyutils-1.2.so
>> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
>> /lib64/libkeyutils-1.2.so
>> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
>> /lib64/libkeyutils-1.2.so
>> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
>> /lib64/libssl.so.0.9.8b
>> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
>> /lib64/libssl.so.0.9.8b
>> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
>> /lib64/libssl.so.0.9.8b
>> 339c000000-339c009000 r-xp 00000000 ca:02 244682
>> /lib64/libcrypt-2.5.so
>> 339c009000-339c208000 ---p 00009000 ca:02 244682
>> /lib64/libcrypt-2.5.so
>> 339c208000-339c209000 r--p 00008000 ca:02 244682
>> /lib64/libcrypt-2.5.so
>> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
>> /lib64/libcrypt-2.5.so
>> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
>> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
>> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
>> 339c773000-339c774000 rw-p 339c773000 00:00 0
>> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
>> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
>> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
>> /lib64/libnss_files-2.5.so
>> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
>> /lib64/libnss_files-2.5.so
>> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
>> /lib64/libnss_files-2.5.so
>> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
>> /lib64/libnss_files-2.5.so
>> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
>> /usr/lib/locale/locale-archive
>> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
>> [stack]
>> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
>> [vdso]
>> Aborted (core dumped)
>>
>>
>>
>>
>> --
>> ================================
>> David Halik
>> System Administrator
>> OIT-CSS Rutgers University
>> dh...@jl...
>> ================================
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
>> _______________________________________________
>> cacti-user mailing list
>> cac...@li...
>> https://lists.sourceforge.net/lists/listinfo/cacti-user
>>
>>     
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
>   


-- 
================================
David Halik
System Administrator
OIT-CSS Rutgers University
dh...@jl...
================================

Artur Renato Araujo da Silva wrote:
> Hi,
> 
> I would like to sum the interface traffic from differents devices. Is it 
> possible to use/make a template to do it?

No, a template won't do. A template always is associated to a single host.

But you may use the AGGREGATE plugin. It has just benn published as V0.70.
Please see the plugin forum at http://forums.cacti.net

Reinhard

I originally had that problem with the stable version of Spine on RHEL 5
64bit.

Larry(TheWitness) fixed it in a later version that was uploaded to the svn.
Try the SVN version of spine and see if that resolves your issue.

Good luck,

-Tim Eberhard

On Tue, Jan 20, 2009 at 1:01 PM, David Halik <dh...@jl...> wrote:

>
> Hello all,
>
> Anyone else experiencing this? Google gave a me a few similar bugs from
> older versions, but I didn't see any specific fix. I haven't been able
> to run spine once without the buffer overflow and core dump. Debug shows
> that it runs just fine and then dies at a certain point. I'll paste the
> truncated message. If anyone wants the whole thing or any other
> debugging please let me know. Any help would be appreciated, thanks.
>
> System: Centos 5 - 64bit
>
> [root@prick include]# /usr/bin/spine --verbosity=10
> SPINE: Using spine config file [/etc/spine.conf]
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
> settings WHERE name = 'path_webroot''
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
> settings WHERE name = 'path_cactilog''
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server
> variable is /var/www/cacti/script_server.php
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog
> variable is /var/www/cacti/log/cacti.log
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM
> settings WHERE name = 'log_destination''
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination
> variable is 3 (SYSLOG)
> <<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
> SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
> was 23, errno was 0, total_time was 7.8678
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP:
> Host is Alive
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code
> was 23, errno was 0, total_time was 52.9289
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP:
> Host is Alive
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item
> SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
> host_id=12'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT
> data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE
> host_id=21'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1
> items in the auto reindex cache for 'servants-sw1.rutgers.edu'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1
> items in the auto reindex cache for 'servants-sw2.rutgers.edu'
> 01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN
> returned the following File Descriptor 9
> *** buffer overflow detected ***: /usr/bin/spine terminated
> ======= Backtrace: =========
> /lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
> /lib64/libc.so.6[0x32e98e4e9b]
> /lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
> /usr/bin/spine[0x40984f]
> /usr/bin/spine[0x409b63]
> /lib64/libpthread.so.0[0x32eac062f7]
> /lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
> ======= Memory map: ========
> 00400000-00412000 r-xp 00000000 ca:02 709057
> /usr/bin/spine
> 00611000-00613000 rw-p 00011000 ca:02 709057
> /usr/bin/spine
> 00613000-00615000 rw-p 00613000 00:00 0
> 00812000-00814000 rw-p 00012000 ca:02 709057
> /usr/bin/spine
> 0bea0000-0bff8000 rw-p 0bea0000 00:00 0
> 41fbd000-41fbe000 ---p 41fbd000 00:00 0
> 41fbe000-429be000 rw-p 41fbe000 00:00 0
> 429be000-429bf000 ---p 429be000 00:00 0
> 429bf000-433bf000 rw-p 429bf000 00:00 0
> 433bf000-433c0000 ---p 433bf000 00:00 0
> 433c0000-43dc0000 rw-p 433c0000 00:00 0
> 43dc0000-43dc1000 ---p 43dc0000 00:00 0
> 43dc1000-447c1000 rw-p 43dc1000 00:00 0
> 32e9400000-32e941a000 r-xp 00000000 ca:02 244651
> /lib64/ld-2.5.so
> 32e961a000-32e961b000 r--p 0001a000 ca:02 244651
> /lib64/ld-2.5.so
> 32e961b000-32e961c000 rw-p 0001b000 ca:02 244651
> /lib64/ld-2.5.so
> 32e9800000-32e994a000 r-xp 00000000 ca:02 244652
> /lib64/libc-2.5.so
> 32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652
> /lib64/libc-2.5.so
> 32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652
> /lib64/libc-2.5.so
> 32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652
> /lib64/libc-2.5.so
> 32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
> 32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654
> /lib64/libdl-2.5.so
> 32e9c02000-32e9e02000 ---p 00002000 ca:02 244654
> /lib64/libdl-2.5.so
> 32e9e02000-32e9e03000 r--p 00002000 ca:02 244654
> /lib64/libdl-2.5.so
> 32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654
> /lib64/libdl-2.5.so
> 32ea000000-32ea082000 r-xp 00000000 ca:02 244659
> /lib64/libm-2.5.so
> 32ea082000-32ea281000 ---p 00082000 ca:02 244659
> /lib64/libm-2.5.so
> 32ea281000-32ea282000 r--p 00081000 ca:02 244659
> /lib64/libm-2.5.so
> 32ea282000-32ea283000 rw-p 00082000 ca:02 244659
> /lib64/libm-2.5.so
> 32ea400000-32ea415000 r-xp 00000000 ca:02 244664
> /lib64/libselinux.so.1
> 32ea415000-32ea615000 ---p 00015000 ca:02 244664
> /lib64/libselinux.so.1
> 32ea615000-32ea617000 rw-p 00015000 ca:02 244664
> /lib64/libselinux.so.1
> 32ea617000-32ea618000 rw-p 32ea617000 00:00 0
> 32ea800000-32ea83b000 r-xp 00000000 ca:02 244663
> /lib64/libsepol.so.1
> 32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663
> /lib64/libsepol.so.1
> 32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663
> /lib64/libsepol.so.1
> 32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
> 32eac00000-32eac15000 r-xp 00000000 ca:02 244657
> /lib64/libpthread-2.5.so
> 32eac15000-32eae14000 ---p 00015000 ca:02 244657
> /lib64/libpthread-2.5.so
> 32eae14000-32eae15000 r--p 00014000 ca:02 244657
> /lib64/libpthread-2.5.so
> 32eae15000-32eae16000 rw-p 00015000 ca:02 244657
> /lib64/libpthread-2.5.so
> 32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
> 32eb000000-32eb014000 r-xp 00000000 ca:02 708212
> /usr/lib64/libz.so.1.2.3
> 32eb014000-32eb213000 ---p 00014000 ca:02 708212
> /usr/lib64/libz.so.1.2.3
> 32eb213000-32eb214000 rw-p 00013000 ca:02 708212
> /usr/lib64/libz.so.1.2.3
> 32eb800000-32eb815000 r-xp 00000000 ca:02 244661
> /lib64/libnsl-2.5.so
> 32eb815000-32eba14000 ---p 00015000 ca:02 244661
> /lib64/libnsl-2.5.so
> 32eba14000-32eba15000 r--p 00014000 ca:02 244661
> /lib64/libnsl-2.5.so
> 32eba15000-32eba16000 rw-p 00015000 ca:02 244661
> /lib64/libnsl-2.5.so
> 32eba16000-32eba18000 rw-p 32eba16000 00:00 0
> 32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662
> /lib64/libresolv-2.5.so
> 32ebc11000-32ebe11000 ---p 00011000 ca:02 244662
> /lib64/libresolv-2.5.so
> 32ebe11000-32ebe12000 r--p 00011000 ca:02 244662
> /lib64/libresolv-2.5.so
> 32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662
> /lib64/libresolv-2.5.so
> 32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
> 32ec000000-32ec08f000 r-xp 00000000 ca:02 701357
> /usr/lib64/libnetsnmp.so.10.0.1
> 32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357
> /usr/lib64/libnetsnmp.so.10.0.1
> 32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357
> /usr/lib64/libnetsnmp.so.10.0.1
> 32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
> 32ec400000-32ec40d000 r-xp 00000000 ca:02 244660
> /lib64/libgcc_s-4.1.2-20080102.so.1
> 32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660
> /lib64/libgcc_s-4.1.2-20080102.so.1
> 32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660
> /lib64/libgcc_s-4.1.2-20080102.so.1
> 32ec800000-32ec925000 r-xp 00000000 ca:02 244667
> /lib64/libcrypto.so.0.9.8b
> 32ec925000-32ecb25000 ---p 00125000 ca:02 244667
> /lib64/libcrypto.so.0.9.8b
> 32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667
> /lib64/libcrypto.so.0.9.8b
> 32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
> 32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666
> /lib64/libcom_err.so.2.1
> 32ecc02000-32ece01000 ---p 00002000 ca:02 244666
> /lib64/libcom_err.so.2.1
> 32ece01000-32ece02000 rw-p 00001000 ca:02 244666
> /lib64/libcom_err.so.2.1
> 32ed400000-32ed42c000 r-xp 00000000 ca:02 708986
> /usr/lib64/libgssapi_krb5.so.2.2
> 32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986
> /usr/lib64/libgssapi_krb5.so.2.2
> 32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986
> /usr/lib64/libgssapi_krb5.so.2.2
> 32ed800000-32ed808000 r-xp 00000000 ca:02 707933
> /usr/lib64/libkrb5support.so.0.1
> 32ed808000-32eda07000 ---p 00008000 ca:02 707933
> /usr/lib64/libkrb5support.so.0.1
> 32eda07000-32eda08000 rw-p 00007000 ca:02 707933
> /usr/lib64/libkrb5support.so.0.1
> 32edc00000-32edc8f000 r-xp 00000000 ca:02 708985
> /usr/lib64/libkrb5.so.3.3
> 32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985
> /usr/lib64/libkrb5.so.3.3
> 32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985
> /usr/lib64/libkrb5.so.3.3
> 32ee000000-32ee024000 r-xp 00000000 ca:02 708984
> /usr/lib64/libk5crypto.so.3.1
> 32ee024000-32ee223000 ---p 00024000 ca:02 708984
> /usr/lib64/libk5crypto.so.3.1
> 32ee223000-32ee225000 rw-p 00023000 ca:02 708984
> /usr/lib64/libk5crypto.so.3.1
> 32ee400000-32ee402000 r-xp 00000000 ca:02 244665
> /lib64/libkeyutils-1.2.so
> 32ee402000-32ee601000 ---p 00002000 ca:02 244665
> /lib64/libkeyutils-1.2.so
> 32ee601000-32ee602000 rw-p 00001000 ca:02 244665
> /lib64/libkeyutils-1.2.so
> 32eec00000-32eec43000 r-xp 00000000 ca:02 244668
> /lib64/libssl.so.0.9.8b
> 32eec43000-32eee43000 ---p 00043000 ca:02 244668
> /lib64/libssl.so.0.9.8b
> 32eee43000-32eee49000 rw-p 00043000 ca:02 244668
> /lib64/libssl.so.0.9.8b
> 339c000000-339c009000 r-xp 00000000 ca:02 244682
> /lib64/libcrypt-2.5.so
> 339c009000-339c208000 ---p 00009000 ca:02 244682
> /lib64/libcrypt-2.5.so
> 339c208000-339c209000 r--p 00008000 ca:02 244682
> /lib64/libcrypt-2.5.so
> 339c209000-339c20a000 rw-p 00009000 ca:02 244682
> /lib64/libcrypt-2.5.so
> 339c20a000-339c238000 rw-p 339c20a000 00:00 0
> 339c400000-339c52c000 r-xp 00000000 ca:02 709080
> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
> 339c52c000-339c72b000 ---p 0012c000 ca:02 709080
> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
> 339c72b000-339c773000 rw-p 0012b000 ca:02 709080
> /usr/lib64/mysql/libmysqlclient_r.so.15.0.0
> 339c773000-339c774000 rw-p 339c773000 00:00 0
> 2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
> 2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
> 2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432
> /lib64/libnss_files-2.5.so
> 2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432
> /lib64/libnss_files-2.5.so
> 2b510e164000-2b510e165000 r--p 00009000 ca:02 244432
> /lib64/libnss_files-2.5.so
> 2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432
> /lib64/libnss_files-2.5.so
> 2b510e166000-2b5111734000 r--p 00000000 ca:02 704414
> /usr/lib/locale/locale-archive
> 7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0
> [stack]
> ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
> [vdso]
> Aborted (core dumped)
>
>
>
>
> --
> ================================
> David Halik
> System Administrator
> OIT-CSS Rutgers University
> dh...@jl...
> ================================
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
>

Hi,

I would like to sum the interface traffic from differents devices. Is it 
possible to use/make a template to do it?

Thanks,
Artur

Hello all,

Anyone else experiencing this? Google gave a me a few similar bugs from 
older versions, but I didn't see any specific fix. I haven't been able 
to run spine once without the buffer overflow and core dump. Debug shows 
that it runs just fine and then dies at a certain point. I'll paste the 
truncated message. If anyone wants the whole thing or any other 
debugging please let me know. Any help would be appreciated, thanks.

System: Centos 5 - 64bit

[root@prick include]# /usr/bin/spine --verbosity=10
SPINE: Using spine config file [/etc/spine.conf]
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM 
settings WHERE name = 'path_webroot''
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM 
settings WHERE name = 'path_cactilog''
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_php_server 
variable is /var/www/cacti/script_server.php
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The path_cactilog 
variable is /var/www/cacti/log/cacti.log
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT value FROM 
settings WHERE name = 'log_destination''
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: The log_destination 
variable is 3 (SYSLOG)
<<<<<<<<<<<<<<SNIP>>>>>>>>>>>>>>>>>
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item 
SET rrd_next_step=rrd_next_step-300 WHERE host_id=1'
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code 
was 23, errno was 0, total_time was 7.8678
01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] PING: Result TCP: 
Host is Alive
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: TCP Ping return_code 
was 23, errno was 0, total_time was 52.9289
01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] PING: Result TCP: 
Host is Alive
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'UPDATE poller_item 
SET rrd_next_step=rrd_step-300 WHERE rrd_next_step < 0 and host_id=1'
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT 
data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE 
host_id=12'
01/20/2009 01:58:47 PM - SPINE: Poller[0] DEBUG: SQL:'SELECT 
data_query_id, action, op, assert_value, arg1 FROM poller_reindex WHERE 
host_id=21'
01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[12] RECACHE: Processing 1 
items in the auto reindex cache for 'servants-sw1.rutgers.edu'
01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[21] RECACHE: Processing 1 
items in the auto reindex cache for 'servants-sw2.rutgers.edu'
01/20/2009 01:58:47 PM - SPINE: Poller[0] Host[1] DEBUG: The POPEN 
returned the following File Descriptor 9
*** buffer overflow detected ***: /usr/bin/spine terminated
======= Backtrace: =========
/lib64/libc.so.6(__chk_fail+0x2f)[0x32e98e578f]
/lib64/libc.so.6[0x32e98e4e9b]
/lib64/libc.so.6(__snprintf_chk+0x7b)[0x32e98e4d6b]
/usr/bin/spine[0x40984f]
/usr/bin/spine[0x409b63]
/lib64/libpthread.so.0[0x32eac062f7]
/lib64/libc.so.6(clone+0x6d)[0x32e98d1e3d]
======= Memory map: ========
00400000-00412000 r-xp 00000000 ca:02 709057                             
/usr/bin/spine
00611000-00613000 rw-p 00011000 ca:02 709057                             
/usr/bin/spine
00613000-00615000 rw-p 00613000 00:00 0
00812000-00814000 rw-p 00012000 ca:02 709057                             
/usr/bin/spine
0bea0000-0bff8000 rw-p 0bea0000 00:00 0
41fbd000-41fbe000 ---p 41fbd000 00:00 0
41fbe000-429be000 rw-p 41fbe000 00:00 0
429be000-429bf000 ---p 429be000 00:00 0
429bf000-433bf000 rw-p 429bf000 00:00 0
433bf000-433c0000 ---p 433bf000 00:00 0
433c0000-43dc0000 rw-p 433c0000 00:00 0
43dc0000-43dc1000 ---p 43dc0000 00:00 0
43dc1000-447c1000 rw-p 43dc1000 00:00 0
32e9400000-32e941a000 r-xp 00000000 ca:02 244651                         
/lib64/ld-2.5.so
32e961a000-32e961b000 r--p 0001a000 ca:02 244651                         
/lib64/ld-2.5.so
32e961b000-32e961c000 rw-p 0001b000 ca:02 244651                         
/lib64/ld-2.5.so
32e9800000-32e994a000 r-xp 00000000 ca:02 244652                         
/lib64/libc-2.5.so
32e994a000-32e9b4a000 ---p 0014a000 ca:02 244652                         
/lib64/libc-2.5.so
32e9b4a000-32e9b4e000 r--p 0014a000 ca:02 244652                         
/lib64/libc-2.5.so
32e9b4e000-32e9b4f000 rw-p 0014e000 ca:02 244652                         
/lib64/libc-2.5.so
32e9b4f000-32e9b54000 rw-p 32e9b4f000 00:00 0
32e9c00000-32e9c02000 r-xp 00000000 ca:02 244654                         
/lib64/libdl-2.5.so
32e9c02000-32e9e02000 ---p 00002000 ca:02 244654                         
/lib64/libdl-2.5.so
32e9e02000-32e9e03000 r--p 00002000 ca:02 244654                         
/lib64/libdl-2.5.so
32e9e03000-32e9e04000 rw-p 00003000 ca:02 244654                         
/lib64/libdl-2.5.so
32ea000000-32ea082000 r-xp 00000000 ca:02 244659                         
/lib64/libm-2.5.so
32ea082000-32ea281000 ---p 00082000 ca:02 244659                         
/lib64/libm-2.5.so
32ea281000-32ea282000 r--p 00081000 ca:02 244659                         
/lib64/libm-2.5.so
32ea282000-32ea283000 rw-p 00082000 ca:02 244659                         
/lib64/libm-2.5.so
32ea400000-32ea415000 r-xp 00000000 ca:02 244664                         
/lib64/libselinux.so.1
32ea415000-32ea615000 ---p 00015000 ca:02 244664                         
/lib64/libselinux.so.1
32ea615000-32ea617000 rw-p 00015000 ca:02 244664                         
/lib64/libselinux.so.1
32ea617000-32ea618000 rw-p 32ea617000 00:00 0
32ea800000-32ea83b000 r-xp 00000000 ca:02 244663                         
/lib64/libsepol.so.1
32ea83b000-32eaa3b000 ---p 0003b000 ca:02 244663                         
/lib64/libsepol.so.1
32eaa3b000-32eaa3c000 rw-p 0003b000 ca:02 244663                         
/lib64/libsepol.so.1
32eaa3c000-32eaa46000 rw-p 32eaa3c000 00:00 0
32eac00000-32eac15000 r-xp 00000000 ca:02 244657                         
/lib64/libpthread-2.5.so
32eac15000-32eae14000 ---p 00015000 ca:02 244657                         
/lib64/libpthread-2.5.so
32eae14000-32eae15000 r--p 00014000 ca:02 244657                         
/lib64/libpthread-2.5.so
32eae15000-32eae16000 rw-p 00015000 ca:02 244657                         
/lib64/libpthread-2.5.so
32eae16000-32eae1a000 rw-p 32eae16000 00:00 0
32eb000000-32eb014000 r-xp 00000000 ca:02 708212                         
/usr/lib64/libz.so.1.2.3
32eb014000-32eb213000 ---p 00014000 ca:02 708212                         
/usr/lib64/libz.so.1.2.3
32eb213000-32eb214000 rw-p 00013000 ca:02 708212                         
/usr/lib64/libz.so.1.2.3
32eb800000-32eb815000 r-xp 00000000 ca:02 244661                         
/lib64/libnsl-2.5.so
32eb815000-32eba14000 ---p 00015000 ca:02 244661                         
/lib64/libnsl-2.5.so
32eba14000-32eba15000 r--p 00014000 ca:02 244661                         
/lib64/libnsl-2.5.so
32eba15000-32eba16000 rw-p 00015000 ca:02 244661                         
/lib64/libnsl-2.5.so
32eba16000-32eba18000 rw-p 32eba16000 00:00 0
32ebc00000-32ebc11000 r-xp 00000000 ca:02 244662                         
/lib64/libresolv-2.5.so
32ebc11000-32ebe11000 ---p 00011000 ca:02 244662                         
/lib64/libresolv-2.5.so
32ebe11000-32ebe12000 r--p 00011000 ca:02 244662                         
/lib64/libresolv-2.5.so
32ebe12000-32ebe13000 rw-p 00012000 ca:02 244662                         
/lib64/libresolv-2.5.so
32ebe13000-32ebe15000 rw-p 32ebe13000 00:00 0
32ec000000-32ec08f000 r-xp 00000000 ca:02 701357                         
/usr/lib64/libnetsnmp.so.10.0.1
32ec08f000-32ec28f000 ---p 0008f000 ca:02 701357                         
/usr/lib64/libnetsnmp.so.10.0.1
32ec28f000-32ec293000 rw-p 0008f000 ca:02 701357                         
/usr/lib64/libnetsnmp.so.10.0.1
32ec293000-32ec2c7000 rw-p 32ec293000 00:00 0
32ec400000-32ec40d000 r-xp 00000000 ca:02 244660                         
/lib64/libgcc_s-4.1.2-20080102.so.1
32ec40d000-32ec60d000 ---p 0000d000 ca:02 244660                         
/lib64/libgcc_s-4.1.2-20080102.so.1
32ec60d000-32ec60e000 rw-p 0000d000 ca:02 244660                         
/lib64/libgcc_s-4.1.2-20080102.so.1
32ec800000-32ec925000 r-xp 00000000 ca:02 244667                         
/lib64/libcrypto.so.0.9.8b
32ec925000-32ecb25000 ---p 00125000 ca:02 244667                         
/lib64/libcrypto.so.0.9.8b
32ecb25000-32ecb44000 rw-p 00125000 ca:02 244667                         
/lib64/libcrypto.so.0.9.8b
32ecb44000-32ecb48000 rw-p 32ecb44000 00:00 0
32ecc00000-32ecc02000 r-xp 00000000 ca:02 244666                         
/lib64/libcom_err.so.2.1
32ecc02000-32ece01000 ---p 00002000 ca:02 244666                         
/lib64/libcom_err.so.2.1
32ece01000-32ece02000 rw-p 00001000 ca:02 244666                         
/lib64/libcom_err.so.2.1
32ed400000-32ed42c000 r-xp 00000000 ca:02 708986                         
/usr/lib64/libgssapi_krb5.so.2.2
32ed42c000-32ed62c000 ---p 0002c000 ca:02 708986                         
/usr/lib64/libgssapi_krb5.so.2.2
32ed62c000-32ed62e000 rw-p 0002c000 ca:02 708986                         
/usr/lib64/libgssapi_krb5.so.2.2
32ed800000-32ed808000 r-xp 00000000 ca:02 707933                         
/usr/lib64/libkrb5support.so.0.1
32ed808000-32eda07000 ---p 00008000 ca:02 707933                         
/usr/lib64/libkrb5support.so.0.1
32eda07000-32eda08000 rw-p 00007000 ca:02 707933                         
/usr/lib64/libkrb5support.so.0.1
32edc00000-32edc8f000 r-xp 00000000 ca:02 708985                         
/usr/lib64/libkrb5.so.3.3
32edc8f000-32ede8f000 ---p 0008f000 ca:02 708985                         
/usr/lib64/libkrb5.so.3.3
32ede8f000-32ede93000 rw-p 0008f000 ca:02 708985                         
/usr/lib64/libkrb5.so.3.3
32ee000000-32ee024000 r-xp 00000000 ca:02 708984                         
/usr/lib64/libk5crypto.so.3.1
32ee024000-32ee223000 ---p 00024000 ca:02 708984                         
/usr/lib64/libk5crypto.so.3.1
32ee223000-32ee225000 rw-p 00023000 ca:02 708984                         
/usr/lib64/libk5crypto.so.3.1
32ee400000-32ee402000 r-xp 00000000 ca:02 244665                         
/lib64/libkeyutils-1.2.so
32ee402000-32ee601000 ---p 00002000 ca:02 244665                         
/lib64/libkeyutils-1.2.so
32ee601000-32ee602000 rw-p 00001000 ca:02 244665                         
/lib64/libkeyutils-1.2.so
32eec00000-32eec43000 r-xp 00000000 ca:02 244668                         
/lib64/libssl.so.0.9.8b
32eec43000-32eee43000 ---p 00043000 ca:02 244668                         
/lib64/libssl.so.0.9.8b
32eee43000-32eee49000 rw-p 00043000 ca:02 244668                         
/lib64/libssl.so.0.9.8b
339c000000-339c009000 r-xp 00000000 ca:02 244682                         
/lib64/libcrypt-2.5.so
339c009000-339c208000 ---p 00009000 ca:02 244682                         
/lib64/libcrypt-2.5.so
339c208000-339c209000 r--p 00008000 ca:02 244682                         
/lib64/libcrypt-2.5.so
339c209000-339c20a000 rw-p 00009000 ca:02 244682                         
/lib64/libcrypt-2.5.so
339c20a000-339c238000 rw-p 339c20a000 00:00 0
339c400000-339c52c000 r-xp 00000000 ca:02 709080                         
/usr/lib64/mysql/libmysqlclient_r.so.15.0.0
339c52c000-339c72b000 ---p 0012c000 ca:02 709080                         
/usr/lib64/mysql/libmysqlclient_r.so.15.0.0
339c72b000-339c773000 rw-p 0012b000 ca:02 709080                         
/usr/lib64/mysql/libmysqlclient_r.so.15.0.0
339c773000-339c774000 rw-p 339c773000 00:00 0
2b510df3c000-2b510df3f000 rw-p 2b510df3c000 00:00 0
2b510df47000-2b510df51000 rw-p 2b510df47000 00:00 0
2b510df5b000-2b510df65000 r-xp 00000000 ca:02 244432                     
/lib64/libnss_files-2.5.so
2b510df65000-2b510e164000 ---p 0000a000 ca:02 244432                     
/lib64/libnss_files-2.5.so
2b510e164000-2b510e165000 r--p 00009000 ca:02 244432                     
/lib64/libnss_files-2.5.so
2b510e165000-2b510e166000 rw-p 0000a000 ca:02 244432                     
/lib64/libnss_files-2.5.so
2b510e166000-2b5111734000 r--p 00000000 ca:02 704414                     
/usr/lib/locale/locale-archive
7fff9cb58000-7fff9cb6e000 rw-p 7fff9cb58000 00:00 0                      
[stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0                  
[vdso]
Aborted (core dumped)




-- 
================================
David Halik
System Administrator
OIT-CSS Rutgers University
dh...@jl...
================================

Excellent suggestion. I do currently run this plugin and they do use it
which is one of the reasons this came to be.  They had been plotting the
data in an excel graph over time and that graph looked much different than
cacti.

While I understand why/how cacti averages I can say that with the ebb and
flow of network usage it doesn't hold true to the usage over time. At the
end of the day that is the problem I'm trying to solve.

Thank you all for your input thus far!

-Tim Eberhard

On Mon, Jan 19, 2009 at 10:59 AM, Reinhard Scheck <
Rei...@te...> wrote:

> You MAY instead want to look at the REPORTIT plugin, the swiss knife for
> capacity planners
>
> Reinhard
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> cacti-user mailing list
> cac...@li...
> https://lists.sourceforge.net/lists/listinfo/cacti-user
>