That's very strange, I'm not seeing that but usually, by the time the
restarted task is applied the service is already stopped because of the
stop directive in deploy.yml


On Fri, Jun 14, 2013 at 11:20 AM, Jason Bau <notifications@github.com>wrote:

> In playbooks/roles/edxapp/handlers/main.yml:
>
> > @@ -206,3 +235,21 @@
> >    tags:
> >    - cms
> >    - deploy
> > +
> > +- name: stop edxapp
>
> I'm not sure if you see this also, but if I do this on our app servers,
> the edxapp process does bounce up and down, but none of the children
> gunicorn processes come back up.
> … <#13f43462830a66b7_>
> On Jun 14, 2013, at 6:39 AM, Feanil Patel <notifications@github.com>
> wrote: In playbooks/roles/edxapp/handlers/main.yml: > @@ -206,3 +235,21 @@
> > tags: > - cms > - deploy > + > +- name: stop edxapp So what was the issue
> with restart edxapp? What about it didn't work? — Reply to this email
> directly or view it on GitHub.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx/configuration/pull/106/files#r4703423>
> .
>