Difference between revisions of "Ganglia"

From ArchWiki
Jump to: navigation, search
m (rm gap)
Line 5: Line 5:
  
 
The [http://sourceforge.net/apps/trac/ganglia Ganglia Wiki] contains all the information you need to get started with Ganglia.
 
The [http://sourceforge.net/apps/trac/ganglia Ganglia Wiki] contains all the information you need to get started with Ganglia.
 +
 +
== Ganglia Web ==
 +
 +
First you need [https://aur.archlinux.org/packages/ganglia-web ganglia-web] from AUR:
 +
 +
yaourt -S ganglia-web
 +
 +
Then you need a [[:Category:Web_Server|web server]] with a working [[PHP]] setup, the following sections include some example setups.
 +
As the [https://aur.archlinux.org/packages/ganglia-web ganglia-web] install script tells you, make sure that your <code>/etc/php/php.ini</code> <code>open_basedir</code> setting includes <code>/usr/share/webapps</code> and <code>/var/lib/ganglia</code>.
 +
 +
 +
=== [[nginx]] with php-fpm ===
 +
 +
Installation of required packages:
 +
 +
pacman -S nginx php-fpm
 +
 +
This is a minimal configuration <code>/etc/nginx/nginx.conf</code>:
 +
 +
events {
 +
  worker_connections  1024;
 +
}
 +
 +
http {
 +
  include mime.types;
 +
  default_type application/octet-stream;
 +
 +
  upstream php {
 +
    server unix:/run/php-fpm/php-fpm.sock;
 +
  }
 +
 +
  server {
 +
    listen 80 default_server;
 +
 +
    root /usr/share/webapps;
 +
    index index.php;
 +
 +
    location ~ \.php$ {
 +
      fastcgi_pass php;
 +
      include fastcgi.conf;
 +
    }
 +
  }
 +
}
 +
 +
Then start all required services:
 +
 +
systemctl start gmetad.service
 +
systemctl start gmond.service
 +
systemctl start php-fpm.service
 +
systemctl start nginx.service
 +
 +
Go to [http://localhost/ganglia/index.php your localhost ganglia page] and monitor the metrics.
 +
  
 
== Troubleshooting ==
 
== Troubleshooting ==

Revision as of 13:21, 2 October 2013

Ganglia is a scalable distributed system monitor tool for high-performance computing systems such as clusters and grids. It allows the user to remotely view live or historical statistics (such as CPU load averages or network utilization) for all machines that are being monitored.

Ganglia is available as the ganglia package on the AUR, along with the web frontend ganglia-web.

The Ganglia Wiki contains all the information you need to get started with Ganglia.

Ganglia Web

First you need ganglia-web from AUR:

yaourt -S ganglia-web

Then you need a web server with a working PHP setup, the following sections include some example setups. As the ganglia-web install script tells you, make sure that your /etc/php/php.ini open_basedir setting includes /usr/share/webapps and /var/lib/ganglia.


nginx with php-fpm

Installation of required packages:

pacman -S nginx php-fpm

This is a minimal configuration /etc/nginx/nginx.conf:

events {
  worker_connections  1024;
}

http {
  include mime.types;
  default_type application/octet-stream;

  upstream php {
    server unix:/run/php-fpm/php-fpm.sock;
  }

  server {
    listen 80 default_server;

    root /usr/share/webapps;
    index index.php;

    location ~ \.php$ {
      fastcgi_pass php;
      include fastcgi.conf;
    }
  }
}

Then start all required services:

systemctl start gmetad.service
systemctl start gmond.service
systemctl start php-fpm.service
systemctl start nginx.service

Go to your localhost ganglia page and monitor the metrics.


Troubleshooting

Issues with IP-address binding or undesirable hostnames

If bind_hostname = yes in the udp_send_channel section of gmond.conf, the gmond daemon will determine which IP to bind to (and report in the XML data) by determining the IP address of the default hostname. You should be able to replicate this behaviour with one of these commands:

$ hostname -i
$ host $(hostname)

The hostname to report is determined by asking the system to look up a hostname for the chosen IP address, in order to ensure the hostname is that by which other machines on the network identify the monitored machine:

$ host <ip-address>

The hostname listed at the top of the list is the one that will be reported by gmond, and will appear in the web UI. You can influence the returned hostname by modifying your /etc/hosts or /etc/nsswitch.conf files. In particular, watch out for placing myhostname before dns on the hosts line in /etc/nsswitch.conf. This will cause gmond to attempt to bind to a UDP port on 127.0.0.1, and it will fail to load.

If you're not able to achieve the desired behaviour, the hostname can be overridden in the gmond.conf file by adding the following lines to the globals section:

globals {
  ...
  override_hostname = myhostname.mydomain
  override_ip = 127.0.0.2
}

References