08:05:46 <anteaya> #startmeeting third-party
08:05:47 <openstack> Meeting started Tue Apr 14 08:05:46 2015 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:05:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:05:50 <openstack> The meeting name has been set to 'third_party'
08:06:08 <anteaya> hands up if you are here for the third party meeting
08:09:07 <eantyshev> Hi, everyone!
08:09:16 <anteaya> hello eantyshev
08:09:21 <anteaya> how are you?
08:10:03 <eantyshev> Thanks, great! got a question
08:10:24 <anteaya> ask away
08:11:17 <eantyshev> my gearman server looses jobs info after zuul is restarted
08:11:28 <anteaya> do you have a stack trace?
08:12:00 <eantyshev> jobs are reported as 'not registered', no trace
08:12:50 <anteaya> ah yes 'not registered' a favourite
08:13:05 <anteaya> so this occurs after zuul is restarted
08:13:11 <eantyshev> evenually brought back
08:13:19 <anteaya> hmmmmm
08:13:43 <anteaya> so yes not registered is usually due to a communication disconnect between zuul and gearman
08:13:58 <anteaya> have you tried restarting gearman when you restart zuul?
08:14:10 <anteaya> I'm not sure that will work, I'm just wondering if you have tried that
08:16:12 <eantyshev> isn't gearman client opened from zuul itself?
08:16:37 <anteaya> opened?
08:16:56 <anteaya> it might be installed with zuul due to how puppet is configured
08:17:12 <anteaya> but restarting zuul doesn't restart gearman as far as I know
08:17:18 <anteaya> they are separate services
08:19:02 <eantyshev> have to tell you I'm using 'development' version of puppet. Gearman server has its section in zuul config
08:19:33 <anteaya> okay I'm not great at puppet
08:20:14 <anteaya> can you restart gearman from zuul?
08:20:28 <anteaya> I will admit that I myself do not run these services
08:21:01 <anteaya> it turns out that talking to folks to co-ordinate third party efforts takes more time that I had expected over the last 2 years
08:21:23 <anteaya> and my residual energy has not been sufficient for me to stand up these services myself
08:21:33 <anteaya> while I wish that I had been able to
08:21:43 <anteaya> I have to be honest with my abilities in this area
08:22:48 <anteaya> so I know that not registered means that in the zuul > gearman > jenkins communication chain someone is not talking to the others
08:23:00 <anteaya> but after that I am guessing
08:23:09 <anteaya> and trying to recall what others have done
08:25:46 <eantyshev> Okay, this isn't a big deal, I can investigate it further
08:26:28 <eantyshev> Just wondered if anyone faced it
08:27:46 <anteaya> sure
08:28:01 <anteaya> and yes, I think almost everyone has hit it at some point
08:28:14 <anteaya> see if you can find a way to restart gearman
08:28:22 <eantyshev> As far as I understand, gearman server hosts as a child of the main zuul-server process
08:28:34 <anteaya> also can you list processes, and see if gearman is there
08:28:41 <anteaya> ah
08:28:48 <anteaya> see I have a different understanding
08:29:01 <anteaya> my understanding is that gearman is its own service
08:29:15 <anteaya> but I only have hearsay for my understanding
08:29:20 <anteaya> so you may be correct
08:29:26 <eantyshev> looking at zuul/cmd/server.py: Server.start_gear_server()
08:29:42 <anteaya> is there a restart?
08:31:15 <eantyshev> service zuul stop/start should do that?
08:32:40 <anteaya> hmmmm, looking at the server.py file you may be correct
08:32:48 <anteaya> do you have a zuul merger set up?
08:33:59 <eantyshev> it's in another process, zuul-merger. Has it anything with gearman?
08:34:21 <anteaya> well the jobs need it
08:34:23 <eantyshev> does its job allright
08:34:48 <anteaya> so I am going with gearman must have to interface with it at some point
08:34:55 <anteaya> okay
08:34:57 <eantyshev> I restart them both, anyway
08:35:04 <anteaya> can't hurt
08:44:42 <anteaya> eantyshev: any further thoughts?
08:44:48 <anteaya> or are you trying it now?
08:46:11 <eantyshev> anteaya: have to investigate how to trigger gearman server jobs update
08:46:37 <anteaya> ah okay, fair enough
08:47:00 <anteaya> did you have anything else you wanted to discuss today?
08:47:49 <eantyshev> no, just that
08:47:58 <anteaya> okay great
08:48:33 <anteaya> so are you willing to come back to the meeting next week and share your findings?
08:49:10 <eantyshev> anteaya: I'll do my best
08:49:51 <anteaya> thank you
08:50:02 <anteaya> any objection to me ending this meeting?
09:00:07 <anteaya> thanks
09:00:14 <anteaya> see you next week
09:00:18 <anteaya> #endmeeting