Last modified: 2013-05-29 18:52:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49244, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47244 - ganglia-monitor does not start (override_hostname not understood)
ganglia-monitor does not start (override_hostname not understood)
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Ryan Lane
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-15 14:02 UTC by Antoine "hashar" Musso (WMF)
Modified: 2013-05-29 18:52 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2013-04-15 14:02:13 UTC
On a fresh instance, ganglia-monitor refresh to start:

puppet gives:


err: /Stage[main]/Ganglia/Service[gmond]/ensure: change from stopped to running failed: Could not start Service[gmond]: Execution of '/etc/init.d/ganglia-monitor start' returned 1:  at /etc/puppet/manifests/ganglia.pp:238


Manual start gives:

root@deployment-cache-upload-test6:/var/log# /etc/init.d/ganglia-monitor start
Starting Ganglia Monitor Daemon: no such option 'override_hostname'
Parse error for '/etc/ganglia/gmond.conf'
root@deployment-cache-upload-test6


ganglia-monitor version is 3.1.7-2ubuntu1.1 :


# apt-cache policy ganglia-monitor
ganglia-monitor:
  Installed: 3.1.7-2ubuntu1.1
  Candidate: 3.5.0-wm1
  Version table:
     3.5.0-wm1 0
       1001 http://apt.wikimedia.org/wikimedia/ precise-wikimedia/main amd64 Packages
     3.3.5-2~wmf2 0
       1001 http://apt.wikimedia.org/wikimedia/ precise-wikimedia/universe amd64 Packages
 *** 3.1.7-2ubuntu1.1 0
        500 http://pmtpa.clouds.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
        100 /var/lib/dpkg/status
     3.1.7-2ubuntu1 0
        500 http://pmtpa.clouds.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
Comment 1 Andrew Bogott 2013-05-29 16:21:52 UTC
I think this is resolved thanks to a new VM image.  Hashar, do you agree?
Comment 2 Antoine "hashar" Musso (WMF) 2013-05-29 18:20:11 UTC
I think that was related to the fresh instances having an old ganglia version (3.1.7 from ubuntu) that did not support the override_hostname parameter (introduced in ganglia 3.2.0).

The new instances still have 3.1.7-2ubuntu2 though.  Maybe they are prepopulated with the latest ganglia version.

I tried creating a new instance ( bug47244.pmtpa.wmflabs ) but that does not let me log in yet :-D  I guess it needs some puppet run which most probably update ganglia.


We might want to just close this bug.
Comment 3 Antoine "hashar" Musso (WMF) 2013-05-29 18:52:09 UTC
$ apt-cache policy ganglia-monitor
ganglia-monitor:
  Installed: 3.5.0-wm1
  Candidate: 3.5.0-wm1
  Version table:
 *** 3.5.0-wm1 0
       1001 http://apt.wikimedia.org/wikimedia/ precise-wikimedia/main amd64 Packages
        100 /var/lib/dpkg/status
     3.3.5-2~wmf2 0
       1001 http://apt.wikimedia.org/wikimedia/ precise-wikimedia/universe amd64 Packages
     3.1.7-2ubuntu1.1 0
        500 http://pmtpa.clouds.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages
     3.1.7-2ubuntu1 0
        500 http://pmtpa.clouds.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages


Weird thing there are two gmond process:

 6257 /usr/sbin/gmond --pid-file /var/run/gmond.pid
 8245 /usr/sbin/gmond


# netstat -lnp|grep gmond
tcp        0      0 0.0.0.0:8649            0.0.0.0:*               LISTEN      6257/gmond      
udp        0      0 239.2.11.71:8649        0.0.0.0:*                           6257/gmond      

Stopping the service, there is still 6257 /usr/sbin/gmond --pid-file /var/run/gmond.pid


I have killed both process and restarted.


Anyway, the restart process does not cause any troubles.
Comment 4 Antoine "hashar" Musso (WMF) 2013-05-29 18:52:50 UTC
The original is fixed whenever puppet has ran which upgrade the default version.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links