On Sat, Oct 20, 2012 at 11:03 AM, Vishal Gupta <[email protected]>wrote:
> Mark,
>
> I have two Exadata Rack, on the new rack dm52 it works (with threads -
> 1.79), but it does not work on one of the older racks dm51 (threads 1.07).
>
> so can I assume you'll be able to upgrade the threads package on dm51? I
guess that version of colplot was so old i hadn't yet been reporting the
threads version. I also see you didn't install ReadKey. w/o it you can
only dynamically change colmux columns by typing in the column number and
hitting enter. with it you can use the arrow keys! install it and you
won't regret it.
I use colplot a lot as well, it helps me so much in quickly identifying the
> resource hogger. Once i get the idea about which resource was used too much
> and during what time period, then i drill deeper into my database level
> statistics to see what was using excessive resource. ColPlot a great help
> to quickly visualise the data. I collect data from 88 servers ( 4 Exadata
> Racks x 22 servers) into single NFS location and use colplot to graph it.
>
that is exactly what I do. we run collectl in the cloud at a 1-sec
monitoring interval and recently I've been using colplot to generate
probably thousands of jpeg plots every nite via a cron job and move them to
a centralized web server for fast display. then if I see something
interesting I can still run colplot manually to zoom in. can you believe
these hires plots are only about 10K Bytes each? Talk about compression!
-mark
> ###################****
> *Does not Work*
> ####################****
> [root@dm51db01 ~]# perl -Mthreads -le'print $threads::VERSION'****
> *1.07*****
> [root@dm51db01 ~]# colmux -v****
> colmux: 3.1.0 (Term::ReadKey: not installed)****
> ** **
> Copyright 2005-2010 Hewlett-Packard Development Company, L.P.****
> colmux may be copied only under the terms of either the Artistic License**
> **
> or the GNU General Public License, which may be found in the source kit***
> *
> ** **
> [root@dm52db01 ~]# perl -v****
> ** **
> This is perl, v5.8.8 built for x86_64-linux-thread-multi****
> ** **
> Copyright 1987-2006, Larry Wall****
> ** **
> ####################****
> *Works*
> ####################****
> [root@dm52db01 ~]# perl -Mthreads -le'print $threads::VERSION'****
> *1.79*
> [root@dm52db01 ~]# colmux -v****
> colmux: 3.2.0 (Term::ReadKey: not installed Threads: 1.79)****
> ** **
> Copyright 2005-2010 Hewlett-Packard Development Company, L.P.****
> colmux may be copied only under the terms of either the Artistic License**
> **
> or the GNU General Public License, which may be found in the source kit***
> *
> ** **
> [root@dm52db01 ~]# perl -v****
> ** **
> This is perl, v5.8.8 built for x86_64-linux-thread-multi****
> ** **
> Copyright 1987-2006, Larry Wall****
> ** **
> **
> **
>
> Regards,****
> Vishal Gupta****
> Blog <http://blog.vishalgupta.com/> |
> LinkedIn<http://www.linkedin.com/in/vishalgupta77>
> * | *Twitter <https://twitter.com/vishalgupta77>
>
> -----Original Message-----
>
> *From: *Mark Seger <[email protected]>
>
> *Subject: *Re: [Collectl-interest] colmux duplicating nodes
>
> *Date: *20 October 2012 15:53:24 BST
>
> *To: *Vishal Gupta <[email protected]>
>
> *Cc: *[email protected]
>
>
>
> interesting, I've never seen this message before ;(
> colmux always used the threads package, but the is_running() I added in
> newer versions to deal with threads more cleanly, so I guess that's your
> problem, you must be running an older threads module.
>
> I can see from colmux -v that I'm running threads V1.83, which version are
> you running? one of the tricks for great support it having colmux report
> the version of threads it's using, just like collectl reports versions for
> zlib and hires. if you've tried colplot yet it also tells you the versions
> of gnuplot it's using and whether gnuplot configured for png and/or x11
> support ;)
>
> -mark
>
> On Sat, Oct 20, 2012 at 10:37 AM, Vishal Gupta <[email protected]>wrote:
>
>> When i use collectl-utils-3.2.1-1, i am getting following error. Which
>> perl module am i missing?
>>
>> Can't locate auto/threads/is_running.al in @INC (@INC contains:
>> /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi
>> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl
>> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi
>> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl
>> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at
>> /usr/bin/colmux line 1120
>>
>>
>> Regards,****
>> Vishal Gupta****
>> Blog <http://blog.vishalgupta.com/> |
>> LinkedIn<http://www.linkedin.com/in/vishalgupta77>
>> * | *Twitter <https://twitter.com/vishalgupta77>
>>
>> -----Original Message-----
>> *From: *Mark Seger <[email protected]>
>> *Subject: *Re: [Collectl-interest] colmux duplicating nodes
>> *Date: *20 October 2012 14:25:59 BST
>> *To: *Vishal Gupta <[email protected]>
>> *Cc: *[email protected]
>>
>>
>>
>>
>> On Sat, Oct 20, 2012 at 9:12 AM, Vishal Gupta <[email protected]>wrote:
>>
>>> Mark,
>>>
>>> I am using following version.
>>>
>>> collectl-3.6.3-2
>>> collectl-utils-3.1.0-1
>>>
>>
>> I'm betting that's your problem. From my release notes for colmux 3.2:
>>
>> "- need to do double-buffering with real-time data since the pointers can
>> change if a new sample comes in before old sample printed"
>>
>>
>>> I am using the older version of collectl-utils, as i had problem with
>>> the newer version. I will install newer collectl-util again to find the
>>> exact description of the problem and let you know why i had not used the
>>> newer colmux. If i don't see the problem i faced earlier, i will try newer
>>> version to see if duplicate server entries are still listed in the output.
>>> I will also try the --age flag to see if "servers-disappearing-in-output"
>>> problem goes away with increased value of --age.
>>>
>>
>> I'd be very interested in hearing what problems you may have had with 3.2
>> as I'm just about to release 3.3 and if it's something minor could probably
>> slip in a fix.
>>
>>
>>> Thanks for the lovely tool and your prompt support. Not only your tool
>>> is fantastic, your support is even better.
>>>
>>
>> glad you're finding colmux useful. Quite honestly I'm still a little
>> surprised interest in it hasn't seemed to pick up.
>> re support: nothing I don't expect (though rarely get) from others. ;)
>> -mark
>>
>>
>>> Regards,****
>>> Vishal Gupta****
>>> Blog <http://blog.vishalgupta.com/> |
>>> LinkedIn<http://www.linkedin.com/in/vishalgupta77>
>>> * | *Twitter <https://twitter.com/vishalgupta77>
>>>
>>> -----Original Message-----
>>> *From: *Mark Seger <[email protected]>
>>> *Subject: *Re: [Collectl-interest] colmux duplicating nodes
>>> *Date: *20 October 2012 12:19:08 BST
>>> *To: *Vishal Gupta <[email protected]>
>>> *Cc: *[email protected]
>>>
>>>
>>>
>>>
>>> On Fri, Oct 19, 2012 at 4:16 PM, Vishal Gupta <[email protected]>wrote:
>>>
>>>> I am using colmux on a Oracle Exadata Machine full rack with linux
>>>> hosts (OEL 5.7), if colmux is left running for few hours it starts showing
>>>> duplicate lines for server in the output.
>>>>
>>>
>>> are you using the latest version [3.2.0]? I do remember seeing that in
>>> an earlier version and I thought I fixed it. I'm really hoping it's not
>>> still there because it can be pretty painful to track down or even
>>> reproduce. The way colmux works is it asynchronously receives/stores data
>>> from each remote host and at the same time fires a timer every monitoring
>>> interval. Colmux then displays the late value it's seen for each entry.
>>> Sounds simple enough but it turned of the incoming data was occasionally
>>> overwriting the data from the previous samples. My solution was to
>>> double-buffer the data, reading from one dataset while writing to a new
>>> one. I'm just hoping I don't need to dig back into it.
>>>
>>>
>>>> Also i noticed that some of the hosts are automatically completely
>>>> removed from the output. Is there some kind of timeout configured in colmux
>>>> or collectl which might remove the server entries from the output over
>>>> time.
>>>>
>>>
>>> unfortunately the way colmux works is if it doesn't hear from a remote
>>> server in x-seconds (which you can set via --age) it drops it from the list
>>> and doesn't try to reconnect. as for the age, you don't want to make it
>>> too long or else a server could disconnect and you'd never know it and keep
>>> displaying stale data. I suppose on a glitchy network you could end up
>>> having to wait a little longer. Maybe you could try upping it to 5 or 10
>>> and see if that helps OR if the remote machine really did drop the link.
>>>
>>> you're not the first to ask about reconnecting when a host drops...
>>>
>>> -mark
>>>
>>>
>>>> Regards,****
>>>> Vishal Gupta****
>>>> Blog <http://blog.vishalgupta.com/> |
>>>> LinkedIn<http://www.linkedin.com/in/vishalgupta77>
>>>> * | *Twitter <https://twitter.com/vishalgupta77>
>>>>
>>>>
>>>
>>> This content has been modified by UniversalMailer plugin for Mail.app.
>>> Its use is for non commercial uses ONLY, except by written permission from
>>> the author. Copyright 2011 by noware. All rights reserved.
>>>
>>
>>
>>
>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Collectl-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/collectl-interest
