From a241a7f510d8e2416241962f36b04d5515eab691 Mon Sep 17 00:00:00 2001 From: rajinir Date: Thu, 14 Jan 2016 11:31:01 -0600 Subject: [PATCH] Updated gearman default port information The jobs generated by jenkins job builder were not registered with the Gearman server. Updated the instructions with the right port and trouble shooting information Change-Id: Ib846e9bf3c36f40747b2ce2f04eae5ae1f42c392 --- doc/source/third_party_ci.rst | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/doc/source/third_party_ci.rst b/doc/source/third_party_ci.rst index a1a099c..e12155d 100644 --- a/doc/source/third_party_ci.rst +++ b/doc/source/third_party_ci.rst @@ -414,9 +414,35 @@ Enable Gearman, which is the Jenkins plugin zuul uses to queue jobs: http://:8080/ Manage Jenkins --> Configure System + For "Gearman Server Port" use port number 4730 Under "Gearman Plugin Config" Check the box "Enable Gearman" Click "Test Connection" It should return success if zuul is running. +The zuul process is running a gearman server on port 4730. To check the status +of gearman: on your zuul node telnet to 127.0.0.1 port 4730, and issue the +command ``status`` to get status information about the jobs registered in +gearman. + +:: + + echo 'status' | nc 127.0.0.1 4730 -w 1 + +The output of the ``status`` command contains tab separated columns with the +following information. + +1. Name: The name of the job. +2. Number in queue: The total number of jobs in the queue including the +currently running ones (next column). +3. Number of jobs running: The total number of jobs currently running. +4. Number of capable workers: A maximum possible count of workers that can run +this job. This number being zero is one reason zuul reports "NOT Registered". + +:: + + build:noop-check-communication 1 0 1 + build:dsvm-tempest-full 2 1 1 + + Enable ZMQ Event Publisher, which is how nodepool is notified of Jenkin slaves status events: