Open Stack

Umar Yousaf <umarusaf902 at gmail.com> wrote on 02/08/2016 03:04:31 AM:

> From: Umar Yousaf <umarusaf902 at gmail.com>
> To: openstack-dev at lists.openstack.org
> Date: 02/08/2016 03:05 AM
> Subject: [openstack-dev] [all] Getting error after doing unstack.sh on
> stable/liberty
> 
> I just did unstack.sh due to some reason and then afterwards when I 
> run stack.sh I am getting following error
>  i) Error: Service g-api is not running
> ii) Error: Service g-reg is not running
> iii) Error: Service h-api is not running
> 
> After a lot of struggle I found a resolution that when I reboot my 
> machine,I can successfully stack.sh just like before.Its really 
> tedious to do reboot.So anyone has a better solution to this problem.I
> know in previous additions of devstack there were not any problems 
> like that but I dont know why it is happening...
> 
> Here is the log where error comes
> 2016-02-08 01:40:47.966 | + 
failures='/opt/stack/status/stack/g-api.failure
> 2016-02-08 01:40:47.967 | /opt/stack/status/stack/g-reg.failure
> 2016-02-08 01:40:47.967 | /opt/stack/status/stack/h-api.failure'
> 2016-02-08 01:40:47.967 | + for service in '$failures'
> 2016-02-08 01:40:47.967 | ++ basename 
/opt/stack/status/stack/g-api.failure
> 2016-02-08 01:40:47.969 | + service=g-api.failure
> 2016-02-08 01:40:47.969 | + service=g-api
> 2016-02-08 01:40:47.969 | + echo 'Error: Service g-api is not running'
> 2016-02-08 01:40:47.969 | Error: Service g-api is not running
> 2016-02-08 01:40:47.969 | + for service in '$failures'
> 2016-02-08 01:40:47.969 | ++ basename 
/opt/stack/status/stack/g-reg.failure
> 2016-02-08 01:40:47.970 | + service=g-reg.failure
> 2016-02-08 01:40:47.970 | + service=g-reg
> 2016-02-08 01:40:47.970 | + echo 'Error: Service g-reg is not running'
> 2016-02-08 01:40:47.970 | Error: Service g-reg is not running
> 2016-02-08 01:40:47.970 | + for service in '$failures'
> 2016-02-08 01:40:47.970 | ++ basename 
/opt/stack/status/stack/h-api.failure
> 2016-02-08 01:40:47.971 | + service=h-api.failure
> 2016-02-08 01:40:47.971 | + service=h-api
> 2016-02-08 01:40:47.971 | + echo 'Error: Service h-api is not running'
> 2016-02-08 01:40:47.971 | Error: Service h-api is not running
> 2016-02-08 01:40:47.971 | + '[' -n 
'/opt/stack/status/stack/g-api.failure
> 2016-02-08 01:40:47.971 | /opt/stack/status/stack/g-reg.failure
> 2016-02-08 01:40:47.971 | /opt/stack/status/stack/h-api.failure' ']'
> 2016-02-08 01:40:47.972 | + die 1537 'More details about the above 
> errors can be found with screen, with ./rejoin-stack.sh'
> 2016-02-08 01:40:47.972 | + local exitcode=0
> 2016-02-08 01:40:47.972 | [Call Trace]
> 2016-02-08 01:40:47.972 | ./stack.sh:1314:service_check
> 2016-02-08 01:40:47.972 | 
/home/airbourne/devstack/functions-common:1537:die
> 2016-02-08 01:40:47.974 | [ERROR] /home/airbourne/devstack/functions-
> common:1537 More details about the above errors can be found with 
> screen, with ./rejoin-stack.sh
> 2016-02-08 01:40:49.057 | Error on exit
> 
> regards,
> 
Umar__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

I sometimes experience that the "unstack" doesn't clean up all the 
services. I then have to see with "px aux | grep python" which one
of the services is still running, despite of the "unstack.sh" call,
and have to kill that processes manually with "kill -9 <pid>".
After that, a new "stack.sh" does usually work for me.

Regards, Markus Zoeller (markus_z)