Re: [Ganglia-general] [PYTHON] Can't find the metric_init function in the python module [varnish].

[Ayman Al-Shorman]

Anyone? I'm still couldn't make it working :(

Sent from my iPhone

> On Apr 18, 2016, at 17:50, Ayman Al-Shorman  wrote:
> 
> Hi Vladimir,
> 
> Any suggestions ?
> 
> 
> 
> From: ayman_shor...@hotmail.com
> To: vli...@veus.hr; ganglia-general@lists.sourceforge.net
> Date: Sun, 17 Apr 2016 17:27:46 +0300
> Subject: Re: [Ganglia-general] [PYTHON] Can't find the metric_init function 
> in the python module [varnish].
> 
> OS: centos 6.6   Ganglia: 3.7.2
> 
> 
> Ayman
> 
> Subject: Re: [Ganglia-general] [PYTHON] Can't find the metric_init function 
> in the python module [varnish].
> To: ayman_shor...@hotmail.com; ganglia-general@lists.sourceforge.net
> From: vli...@veus.hr
> Date: Sun, 17 Apr 2016 10:16:05 -0400
> 
> What OS and Ganglia version is this running on ?
> 
> Vladimir
> 
> 04/17/2016 u 08:37 AM, Ayman Al-Shorman je napisao/la:
> Hi Vladimir,
> 
> yes i can see the output of the plugin.
> 
> 
> varnish_MAIN.fetch_1xx = 0.00
> varnish_MAIN.fetch_204 = 0.00
> varnish_MAIN.fetch_304 = 0.00
> varnish_MAIN.bans = 1.00
> varnish_MAIN.bans_added = 0.00
> varnish_MAIN.bans_dups = 0.00
> varnish_MAIN.bans_tested = 0.00
> varnish_MAIN.bans_deleted = 0.00
> varnish_MAIN.n_gunzip = 0.00
> varnish_MAIN.n_gzip = 0.00
> varnish_MAIN.n_waitinglist = 0.00
> varnish_MAIN.vmods = 2.00
> varnish_SMA.s0.c_bytes = 241777981447.00
> varnish_SMA.s0.c_freed = 240704265477.00
> varnish_SMA.s0.g_bytes = 1073715970.00
> varnish_SMA.s0.g_space = 25854.00
> Sleeping 15 seconds
> 
> 
> Thanks
> 
> Ayman
> 
> To: ganglia-general@lists.sourceforge.net
> From: vli...@veus.hr
> Date: Sun, 17 Apr 2016 08:14:08 -0400
> Subject: Re: [Ganglia-general] [PYTHON] Can't find the metric_init function 
> in the python module [varnish].
> 
> Can you try to run the varnishstat.py by hand to see if outputs the metrics 
> values.
> 
> Vladimir
> 
> 04/16/2016 u 02:33 PM, Ayman Al-Shorman je napisao/la:
> Hi,
> 
> I'm trying to plot varnish stats by the varnish python module but when i run 
> gmond -d 5 i get :
> 
> [PYTHON] Can't find the metric_init function in the python module [varnish].
> 
> Unable to find any metric information for 'varnish_(.+)'. Possible that a 
> module has not been loaded.
> 
> Everything is in place and all libraries are linked properly to modpython.so  
> any suggestion ?
> 
> Thanks
> 
> Ayman
> 
> 
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> 
> 
> ___
> Ganglia-general mailing list
> Ganglia-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
> 
> 
> --
>  Find and fix application performance issues faster with Applications Manager 
> Applications Manager provides deep performance insights into multiple tiers 
> of your business applications. It resolves application problems quickly and 
> reduces your MTTR. Get your free trial! 
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___ Ganglia-general mailing list 
> Ganglia-general@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
> 
>   This email is safe. www.avast.com
> 
> --
>  Find and fix application performance issues faster with Applications Manager 
> Applications Manager provides deep performance insights into multiple tiers 
> of your business applications. It resolves application problems quickly and 
> reduces your MTTR. Get your free trial! 
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___ Ganglia-general mailing list 
> Ganglia-general@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
> --
> Find and fix application performance issues faster with Applications Manager
> Applications Manager provides deep performance insights into multiple tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> ___
> Ganglia-general mailing list
> Ganglia-general@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
--
Find and fix application 

Re: [Ganglia-general] Ubuntu: No matching metrics detected or RRDs not reachable

[Elliot Hallmark]

I solved this.  Using tcpdump I saw a lot of this:

13:19:25.271573 IP6 localhost.38025 > localhost.8649: UDP, length 48
13:19:25.271591 IP6 localhost > localhost: ICMP6, destination unreachable,
unreachable port, localhost udp port 8649, length 104

So I changed `localhost` in `gmond.conf` to the ipv4 address of the
computer (192.168.1.x).  The node shows up now!

On Wed, Apr 20, 2016 at 1:00 PM, Elliot Hallmark <
ell...@clearviewsudbury.org> wrote:

> I am trying to set up Ganglia on a cluster of one Ubuntu 14.10 machine and
> 3 windows 7 machines.  The Ubuntu machine will also be the web server.
>
> I followed this tutorial:
> https://www.digitalocean.com/community/tutorials/introduction-to-ganglia-on-ubuntu-14-04
>
> When I get to the web-interface section, the site comes up and looks
> normal except for the detail that it says there are no hosts connected and
> "No matching metrics detected or RRDs not reachable".
>
> Does anyone have any advice for getting this working just on the ubuntu
> machine?
>
> Thanks,
>   Elliot
>
> ===
>
> root@steve:~# gmetad --version
> gmetad 3.6.0
> root@steve:~# gmond --version
> gmond 3.6.0
>
> root@steve:~# grep -v '^#' /etc/ganglia/gmetad.conf
>
> data_source "my cluster" localhost
>
> case_sensitive_hostnames 0
>
> root@steve:~# cat /etc/ganglia/gmond.conf
> /* This configuration is as close to 2.5.x default behavior as possible
>The values closely match ./gmond/metric.h definitions in 2.5.x */
> globals {
>   daemonize = yes
>   setuid = yes
>   user = user1
>   debug_level = 0
>   max_udp_msg_len = 1472
>   mute = no
>   deaf = no
>   host_dmax = 0 /*secs */
>   cleanup_threshold = 300 /*secs */
>   gexec = no
>   send_metadata_interval = 0
> }
>
> /* If a cluster attribute is specified, then all gmond hosts are wrapped
> inside
>  * of a  tag.  If you do not specify a cluster tag, then all
>  will
>  * NOT be wrapped inside of a  tag. */
> cluster {
>   name = "my cluster"
>   owner = "CSS"
>   latlong = "unspecified"
>   url = "unspecified"
> }
>
> /* The host section describes attributes of the host, like the location */
> host {
>   location = "unspecified"
> }
>
> /* Feel free to specify as many udp_send_channels as you like.  Gmond
>used to only support having a single channel */
> udp_send_channel {
>   #mcast_join = 239.2.11.71
>   host = localhost
>   port = 8649
>   ttl = 1
> }
>
> /* You can specify as many udp_recv_channels as you like as well. */
> udp_recv_channel {
>   #mcast_join = 239.2.11.71
>   port = 8649
>   #bind = 239.2.11.71
> }
>
> /* You can specify as many tcp_accept_channels as you like to share
>an xml description of the state of the cluster */
> tcp_accept_channel {
>   port = 8649
> }
>
> /* Each metrics module that is referenced by gmond must be specified and
>loaded. If the module has been statically linked with gmond, it does
> not
>require a load path. However all dynamically loadable modules must
> include
>a load path. */
> modules {
>   module {
> name = "core_metrics"
>   }
>   module {
> name = "cpu_module"
> path = "/usr/lib/ganglia/modcpu.so"
>   }
>   module {
> name = "disk_module"
> path = "/usr/lib/ganglia/moddisk.so"
>   }
>   module {
> name = "load_module"
> path = "/usr/lib/ganglia/modload.so"
>   }
>   module {
> name = "mem_module"
> path = "/usr/lib/ganglia/modmem.so"
>   }
>   module {
> name = "net_module"
> path = "/usr/lib/ganglia/modnet.so"
>   }
>   module {
> name = "proc_module"
> path = "/usr/lib/ganglia/modproc.so"
>   }
>   module {
> name = "sys_module"
> path = "/usr/lib/ganglia/modsys.so"
>   }
> }
>
> include ('/etc/ganglia/conf.d/*.conf')
>
>
> /* The old internal 2.5.x metric array has been replaced by the following
>collection_group directives.  What follows is the default behavior for
>collecting and sending metrics that is as close to 2.5.x behavior as
>possible. */
>
> /* This collection group will cause a heartbeat (or beacon) to be sent
> every
>20 seconds.  In the heartbeat is the GMOND_STARTED data which expresses
>the age of the running gmond. */
> collection_group {
>   collect_once = yes
>   time_threshold = 20
>   metric {
> name = "heartbeat"
>   }
> }
>
> /* This collection group will send general info about this host every 1200
> secs.
>This information doesn't change between reboots and is only collected
> once. */
> collection_group {
>   collect_once = yes
>   time_threshold = 1200
>   metric {
> name = "cpu_num"
> title = "CPU Count"
>   }
>   metric {
> name = "cpu_speed"
> title = "CPU Speed"
>   }
>   metric {
> name = "mem_total"
> title = "Memory Total"
>   }
>   /* Should this be here? Swap can be added/removed between reboots. */
>   metric {
> name = "swap_total"
> title = "Swap Space Total"
>   }
>   metric {
> name = "boottime"
> title = "Last Boot Time"
>   }
>   metric {
> name = "machine_type"
> title