From mehmet at icann.org Mon Mar 1 04:42:42 2010 From: mehmet at icann.org (Mehmet Akcin) Date: Sun, 28 Feb 2010 20:42:42 -0800 Subject: [dsc] DSC RPM for CentOS Message-ID: Does anyone have RPM for CentOS 5.X for latest DSC?.. I thought I would ask before starting to build on..., if noone has it.. I will try to build one :) Let me know please mehmet From tobias at linuxdingsda.de Mon Mar 1 08:31:25 2010 From: tobias at linuxdingsda.de (Tobias Winter) Date: Mon, 01 Mar 2010 09:31:25 +0100 Subject: [dsc] DSC RPM for CentOS In-Reply-To: References: Message-ID: <4B8B7B5D.50508@linuxdingsda.de> On 03/01/2010 05:42 AM, Mehmet Akcin wrote: > Does anyone have RPM for CentOS 5.X for latest DSC?.. Sorry, no, but I could offer you .deb-packages for the svn-head-versoin of the collector. (lenny 32 and 64 bit) -- Tobias From tobias at linuxdingsda.de Wed Mar 3 12:41:49 2010 From: tobias at linuxdingsda.de (Tobias Winter) Date: Wed, 03 Mar 2010 13:41:49 +0100 Subject: [dsc] dsc presenter bug? Message-ID: <4B8E590D.4040109@linuxdingsda.de> Hey there, initially I tested dsc with two nameservers. We quickly decided to enroll it on multiple server, after which I ran into some complications. In my current presenter setup, there are 32 nameservers in one global group. The Qtypes plot over one week works fine for all nodes. However the By Node plot over one week only plots the first 4 days and after that simply displays white space. http://linuxdingsda.de/~wintix/bynode_bork.png When selection fewer days it is working perfectly. Any idea where the data gets killed? I have been through the presenter code, but couldn't figure it out. Cheers Tobias From tobias at linuxdingsda.de Wed Mar 3 16:11:35 2010 From: tobias at linuxdingsda.de (Tobias Winter) Date: Wed, 03 Mar 2010 17:11:35 +0100 Subject: [dsc] dsc presenter bug? In-Reply-To: <02f701cabae7$289251d0$79b6f570$@pe> References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> Message-ID: <4B8E8A37.40402@linuxdingsda.de> On 03/03/2010 04:35 PM, Jose Romero wrote: > Hi, > > I have installed the dsc-200911111630.tar DSC version and I see a similar > problem but in my case it's in the "Source Ports Graph". Same here. I just took 'By Node' as example because I assume the data gets lost at the same portion of code for the various types of graphs. I so far ~ruled out a out-of-memory-kill of ploticus. My best guess is that an array is out of space or something. Cheers Tobias From wessels at measurement-factory.com Wed Mar 3 17:45:14 2010 From: wessels at measurement-factory.com (Duane Wessels) Date: Wed, 3 Mar 2010 10:45:14 -0700 (MST) Subject: [dsc] dsc presenter bug? In-Reply-To: <4B8E8A37.40402@linuxdingsda.de> References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> <4B8E8A37.40402@linuxdingsda.de> Message-ID: On Wed, 3 Mar 2010, Tobias Winter wrote: > On 03/03/2010 04:35 PM, Jose Romero wrote: >> Hi, >> >> I have installed the dsc-200911111630.tar DSC version and I see a similar >> problem but in my case it's in the "Source Ports Graph". > Same here. I just took 'By Node' as example because I assume the data > gets lost at the same portion of code for the various types of graphs. > > I so far ~ruled out a out-of-memory-kill of ploticus. > > My best guess is that an array is out of space or something. Its a good possibility that ploticus is complaining about too much data (but we don't see it because its stderr is lost). In grapher.pm you'll find this line: ploticus_arg("-maxrows", "20000"); you might try doubing that. Note however that ploticus has other default limits that might be a factor. To debug more in ploticus.pm find the function ploticus_begin and then add something like "2>/tmp/ploticus.stderr" to the end of the $cmd that gets spawned. DW From jromero at rcp.pe Wed Mar 3 19:53:31 2010 From: jromero at rcp.pe (Jose Romero) Date: Wed, 3 Mar 2010 14:53:31 -0500 Subject: [dsc] dsc presenter bug? In-Reply-To: References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> <4B8E8A37.40402@linuxdingsda.de> Message-ID: <03d501cabb0b$33a1b330$9ae51990$@pe> Hi Duane, I modified in grapher.pm ploticus_arg("-maxrows", "20000") to ploticus_arg("-maxrows", "40000") and the problem continue (only with Source Ports graph) I added "2>/tmp/ploticus.stderr" in ploticus.pm and I see the following in the ploticus.stderr file: pl proc getdata: error 406: Data input truncated... too many data fields (try raising -maxfields) cat: stdout: Broken pipe I don't Know where put the -maxfields argument and its value. Can you help me? Regards Jose -----Mensaje original----- De: Duane Wessels [mailto:wessels at measurement-factory.com] Enviado el: Mi?rcoles, 03 de Marzo de 2010 12:45 p.m. Para: Tobias Winter CC: Jose Romero; dsc at measurement-factory.com Asunto: Re: [dsc] dsc presenter bug? On Wed, 3 Mar 2010, Tobias Winter wrote: > On 03/03/2010 04:35 PM, Jose Romero wrote: >> Hi, >> >> I have installed the dsc-200911111630.tar DSC version and I see a similar >> problem but in my case it's in the "Source Ports Graph". > Same here. I just took 'By Node' as example because I assume the data > gets lost at the same portion of code for the various types of graphs. > > I so far ~ruled out a out-of-memory-kill of ploticus. > > My best guess is that an array is out of space or something. Its a good possibility that ploticus is complaining about too much data (but we don't see it because its stderr is lost). In grapher.pm you'll find this line: ploticus_arg("-maxrows", "20000"); you might try doubing that. Note however that ploticus has other default limits that might be a factor. To debug more in ploticus.pm find the function ploticus_begin and then add something like "2>/tmp/ploticus.stderr" to the end of the $cmd that gets spawned. DW From tobias at linuxdingsda.de Wed Mar 3 19:59:37 2010 From: tobias at linuxdingsda.de (Tobias Winter) Date: Wed, 03 Mar 2010 20:59:37 +0100 Subject: [dsc] dsc presenter bug? In-Reply-To: <03d501cabb0b$33a1b330$9ae51990$@pe> References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> <4B8E8A37.40402@linuxdingsda.de> <03d501cabb0b$33a1b330$9ae51990$@pe> Message-ID: <4B8EBFA9.80804@linuxdingsda.de> Hey, Yay, that works! :) > I don't Know where put the -maxfields argument and its value. Can you help Just put it in grapher.pm like that: ploticus_arg("-maxrows", "2000000"); ploticus_arg("-maxfields", "2000000"); Thank you for providing the debug output and the hint. Cheers Tobias From jromero at rcp.pe Wed Mar 3 20:12:56 2010 From: jromero at rcp.pe (Jose Romero) Date: Wed, 3 Mar 2010 15:12:56 -0500 Subject: [dsc] dsc presenter bug? In-Reply-To: <4B8EBFA9.80804@linuxdingsda.de> References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> <4B8E8A37.40402@linuxdingsda.de> <03d501cabb0b$33a1b330$9ae51990$@pe> <4B8EBFA9.80804@linuxdingsda.de> Message-ID: <03e801cabb0d$ea0d9c90$be28d5b0$@pe> Thanks a lot Tobias, it's works. Thanks Duane too Cheers Jose -----Mensaje original----- De: Tobias Winter [mailto:tobias at linuxdingsda.de] Enviado el: Mi?rcoles, 03 de Marzo de 2010 03:00 p.m. Para: Jose Romero CC: 'Duane Wessels'; dsc at measurement-factory.com Asunto: Re: [dsc] dsc presenter bug? Hey, Yay, that works! :) > I don't Know where put the -maxfields argument and its value. Can you help Just put it in grapher.pm like that: ploticus_arg("-maxrows", "2000000"); ploticus_arg("-maxfields", "2000000"); Thank you for providing the debug output and the hint. Cheers Tobias From wessels at measurement-factory.com Wed Mar 3 23:55:07 2010 From: wessels at measurement-factory.com (Duane Wessels) Date: Wed, 3 Mar 2010 16:55:07 -0700 (MST) Subject: [dsc] dsc presenter bug? In-Reply-To: <4B8EBFA9.80804@linuxdingsda.de> References: <4B8E590D.4040109@linuxdingsda.de> <02f701cabae7$289251d0$79b6f570$@pe> <4B8E8A37.40402@linuxdingsda.de> <03d501cabb0b$33a1b330$9ae51990$@pe> <4B8EBFA9.80804@linuxdingsda.de> Message-ID: On Wed, 3 Mar 2010, Tobias Winter wrote: > Hey, > > Yay, that works! :) > >> I don't Know where put the -maxfields argument and its value. Can you help > Just put it in grapher.pm like that: > > ploticus_arg("-maxrows", "2000000"); > ploticus_arg("-maxfields", "2000000"); Glad that fixed it. I've committed these changes to the repository.