ganglia / chef-ganglia Goto Github PK

Version 0.2.3 was released back in 2014 and there has been quite a bit of development on this cookbook since that time. Any chance of a 0.2.4 release?

The biggest thing I need is the package support on Centos and Redhat, we don't want to have to build from source every time we install gmond on a host.

All gmond templates don’t have a path to all modules and assume that they’re statically linked. When you try to load a dynamically compiled module (as it is the case by default on Ubuntu nodes) you’ll just get an error that the module was not found.

There should be an attribute (module_path or similar) that can be empty be default. Setting the attribute would prefix all modules with that path.

Ubuntu 14.04 there are packages like ganglia-modules-linux or ganglia-monitor-python.
Will be great to have ability install this packages with gmond daemon if i need it.

I'm using the unicast mode and the actual generated configuration of udp_send_channel becomes:

udp_send_channel { 
   host = ["x.x.x.x"]
   port = 8649 
   ttl = 1 
}

While the expected result is:

udp_send_channel { 
   host = x.x.x.x
   port = 8649 
   ttl = 1 
}

It seems that value of chef search result (in array) is used, so it's easy to fix.

#50

There's quite a few open pull requests. Could someone merge them or close them?

The ganglia org has begun maintaining a fork of this cookbook. This cookbook repo should be deprecated in favor of its new home:

https://github.com/ganglia/chef-ganglia

Hi,

on centos (and probably redhat) we could fetch all the packages from epel:

Name        : ganglia
Arch        : x86_64
Version     : 3.1.7
Release     : 6.el6
Size        : 150 k
Repo        : epel
Summary     : Ganglia Distributed Monitoring System
URL         : http://ganglia.sourceforge.net/
License     : BSD
Description : Ganglia is a scalable, real-time monitoring and execution environment
            : with all execution requests and statistics expressed in an open
            : well-defined XML format.

Is there any reason why we build it from source instead?

Hello,
I really need use cookbook in chef-solo, but some parts of recipes have search. I know how fix it, but i don't know how fix chefspec test for it.

Due to this issue(https://bugs.launchpad.net/ubuntu/+source/ganglia/+bug/854866), this cookbook didn't work in Ubuntu-11.10.

If i try to run gmond by default recipe on server with collect gmond i has error on init script:

/usr/sbin/gmond already running.

could 0.2.1 be stamped (or tagged?) and be uploaded to the community site, there was a patch that fixes an issue with ganglia and a unknown configuration variable in ubuntu 12.04.

can you switch from using node['platform'].include?('redhat', 'fedora', 'centos') to node['platform_family'] == 'rhel' so that Oracle Linux gets supported?

All symlinks have to be placed in /etc/apache/sites-enabled/*.conf in order to be read by the default Ubuntu Apache configuration. The current symlink doesn’t conform to Ubuntu file system naming standards and is just /etc/apache/sites-enabled/ganglia. It should be /etc/apache/sites-enabled/001-ganglia.conf instead.

It would help if the attributes were broken down by global, server and client.

I'm having a hard time getting this cookbook to work without trial and error.

Also which recipe needs to be run on which type of host could use a bit more clarification. If I have a server that is running gmetad and the webUI, do that host need the default gmond as well?

It seems ganglia-logtailer is not available on ubuntu?

Hello, there is allot of bugfixes and work that has been done on this cookbook since the 0.2.3 release. Basically the version that is on https://supermarket.chef.io/cookbooks/ganglia is broken for rpm based systems and the fixes are already incorporated into the current release. Any chance this can be bumped up to a current version in supermarket?

in package ganglia-monitor (3.6.0) on ubuntu 14.04 initscript return exit code 1 when restart because upstart run process fastly than initscript. Generally it error of initscript which return exit code 1 when application already run.

This issue is about distribution of ganglia through the use of Berkshelf. Somewhere in the chain of custody between github and a machine running Berkshelf your cookbook is being mangled. This issue probably needs to be routed through another project but I have been unable to figure out who precisely. Please bare with me. I figure this project has a vested interest in proper distribution to Chef users. I am hopeful someone on this project can help redirect me to the proper place to log an issue, or someone will know enough to help convey the problem to the right people.

The issue:
when using ganglia-0.2.1 with Berkshelf the cookbook becomes damaged and cannot be uploaded to a Chef server because it fails validation.

Environment:
berkshelf: 3.1.4
chef server: 11.1.0

Analysis:
Uploading ganglia-0.2.1 with the command berks upload fails because of a validation error. The error reports as follows:

E, [2014-07-23T16:28:27.255594 #10823] ERROR -- : Cookbook file attributes/PaxHeader/ganglia.rb has a ruby syntax error:
E, [2014-07-23T16:28:27.256008 #10823] ERROR -- : /home/vagrant/.berkshelf/cookbooks/ganglia-0.2.1/attributes/PaxHeader/ganglia.rb:1: syntax error, unexpected tIDENTIFIER, expecting $end
E, [2014-07-23T16:28:27.256121 #10823] ERROR -- : 18 gid=1876110778
E, [2014-07-23T16:28:27.256721 #10823] ERROR -- :       ^
E, [2014-07-23T16:28:27.263077 #10823] ERROR -- : Ridley::Errors::CookbookSyntaxError: Invalid ruby files in cookbook: ganglia (0.2.1).
E, [2014-07-23T16:28:27.266391 #10823] ERROR -- : /var/lib/gems/1.9.1/gems/ridley-4.0.0/lib/ridley/chef/cookbook.rb:198:in `validate'

Viewing the contents of the ganglia cookbook on disk it is clear that there has been some error in the tar package handling. This may have occurred at github, at the Opscode supermarket intermediary, or in the Berkshelf code. Within the cookbook every directory is mirrored with a PaxHeader directory, which is a bookkeeping artifact from tar packaging. The PaxHeader directories should not show up in the output from tar. Here is a list of the files as they appear in the downloaded cookbook: https://gist.github.com/4ba91ca3463844aa16d4.git

In that output you can see that, for example, the attributes directory is mirrored by an attributes/PaxHeader directory. attributes contains the file ganglia.rb which has the actual ruby code to set cookbook attributes. attributes/PaxHeader contains the file ganglia.rb which includes metadata tar uses to track the file. Since attributes/PacHeader/ganglia.rb represents itself as a ruby file (by its file extension .rb) the Chef server attempts to validate the ruby contained within. Since the file is metadata, and not actual ruby code, the validation fails and uploading ganglia to the Chef server fails.

So the question is, where do things break down?

My project downloads 62 cookbooks in addition to ganglia. Ganglia is the only cookbook which manifests this particular problem. I am happy to attempt to find a forum in Opscode, or on GitHub to replay this issue, but I am uncertain whether and how the cookbooks provided through supermarket.getchef.com (where Berkshelf pulls Opscode blessed cookbooks) come from. Perhaps they have a cached copy of the project tar that was provided manually from this project?

For my part I am able to script deletion of PaxHeader directories and can move along smoothly. But I sense this may be a problem for other ganglia users who employ Berkshelf. I bring it up here because I suspect folks on this project will be the best advocates for this being straightened out. If I can be of assistance I am happy to do so, but will require input as to where the proper venue is for lodging this issue.

Thanks!