<div dir="ltr"><div class="gmail_extra">Tang, Have you tried to look at the function registrations and gearman queue on the gearman server as i suggested? The instructions are in the wiki i referenced (in 'Starting the gearman workers' section). What you are seeing from the gear_client could also be from passing in a function name that does not exist. Unfortunately the simple gear_client does not check whether the passed in functions are valid so what you want to do is verify that the gearman functions have been registered by using the 'workers' command. </div><div class="gmail_extra"><br></div><div class="gmail_extra"> </div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 24, 2015 at 1:09 AM, Tang Chen <span dir="ltr"><<a href="mailto:tangchen@cn.fujitsu.com" target="_blank">tangchen@cn.fujitsu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<br>
<div>On 07/24/2015 03:36 PM, Tang Chen
wrote:<br>
</div>
<blockquote type="cite">
Hi Zaro,<br>
<br>
Thanks to reply.<br>
<br>
<div>On 07/24/2015 03:06 PM, Zaro wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>That is correctly, the Jenkins UI will not show any info
about the gearman queue. If job is pending in Jenkins that
means it's been added to the gearman queue and has been
moved to the jenkins build queue. The jenkins UI will only
show the job once it's in the jenkins queue. </div>
<div><br>
</div>
Hmm. What happens when you manually start a build by click on
the build icon in the jenkins UI? <br>
</div>
</blockquote>
</blockquote>
<br></span>
If I click the build icon in the jenkins UI, the job can run. Wired,
isn't it ?<br>
<br>
Thanks.<div><div class="h5"><br>
<br>
<blockquote type="cite">
<blockquote type="cite">
<div dir="ltr"> I'm wondering if maybe your labels are
configured correctly for your jobs and slaves. Are there any
labels on the job or the nodes (master or slaves)? I think the
jobs would be in a pending state if there are labels on nodes
and jobs but they do not match. I would check to see if there
are any labels on the jobs and if there are then I would
remove all of the labels and try again. There are step by
step directions on how to setup the gearman-plugin in the
jenkins wiki[1] which also shows you how to debug by viewing
the gearman server queue and function registrations. Try to
make sure the functions are registered correctly and that the
job is in the queue after you run the gear-client command.
<div><br>
</div>
<div>A couple of questions:</div>
<div>What version of Jenkins are you running? I think
openstack runs on 1.565.3</div>
<div>Also I don't think we've ever tested Jenkins and the
gearman server running on the same machine or VM. Maybe one
thing you can try is to run them on separate VMs? <br>
</div>
</div>
</blockquote>
<br>
I don't have any label, and only a master, no slave.<br>
<br>
My jenkins is 1.609.1.<br>
<br>
The whole problem is described here:<br>
<br>
<a href="http://paste.openstack.org/show/405051/" target="_blank">http://paste.openstack.org/show/405051/</a><br>
<br>
Please help to check and see.<br>
<br>
<br>
BTW, I post the problem to #openstack-infra IRC channel. You can
join into that meeting if you'd like to.<br>
<br>
<br>
Thanks.<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
<div>[1] <a href="https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin" target="_blank">https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin</a><br>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra"><br>
</div></div></div></div></blockquote></blockquote></div></div></div></blockquote></div><br></div></div>