Open Stack

Samer, you could always use `dockerctl check all|<container-name>` command.

On Wed, Mar 30, 2016 at 2:47 PM, Adam Heczko <aheczko at mirantis.com> wrote:

> Samer my 2c are:
> after Fuel node reboot just run 'docker ps -a' to get information if all
> containers have been already running.
>
> On Wed, Mar 30, 2016 at 1:07 PM, Samer Machara <
> samer.machara at telecom-sudparis.eu> wrote:
>
>> Thanks,
>>    Problem solved by magic.  It looks like,  the nailgun service take
>> some time to start up in my computer.
>>
>> ------------------------------
>> *From: *"Samer Machara" <samer.machara at telecom-sudparis.eu>
>> *To: *"OpenStack Development Mailing List" <
>> openstack-dev at lists.openstack.org>
>> *Sent: *Wednesday, March 30, 2016 12:39:35 PM
>> *Subject: *Re: [Fuel] [Openstack] Problem after reboot fuel-master VM
>>
>>
>> Hi Vladimir,
>>   I'm using fuel 7.0, Which log I need to see?
>>
>> ------------------------------
>> *From: *"*Vladimir Kuklin* vkuklin at mirantis.com
>> <openstack-dev%40lists.openstack.org?Subject=Re%3A%20%5Bopenstack-dev%5D%20%5BFuel%5D%20%5BOpenstack%5D%20Problem%20after%20reboot%0A%20fuel-master%20VM&In-Reply-To=%3CCAHAWLf2-xQ0G-m-ApocgOAVDG1GTEb5F-f7NXoiwN%3DpbCQ3JWA%40mail.gmail.com%3E>
>> *To: *"OpenStack Development Mailing List" <
>> openstack-dev at lists.openstack.org>
>> *Sent: **Wed Mar 30 10:06:22 UTC 2016*
>> *Subject: *[Fuel] [Openstack] Problem after reboot fuel-master VM
>>
>> Hi, Samer
>>
>> It seems that Nailgun has not started. Could you please provide us with the
>> version of Fuel you are using? You can find logs for nailgun in:
>>
>> for <9.0/pre-Mitaka versions
>> /var/log/<docker-logs>/nailgun/
>>
>> for current Mitaka:
>>
>> /var/log/nailgun/
>>
>> ------------------------------
>> *From: *"Samer Machara" <samer.machara at telecom-sudparis.eu>
>> *To: *"OpenStack Development Mailing List" <
>> openstack-dev at lists.openstack.org>
>> *Sent: *Wednesday, March 30, 2016 11:38:44 AM
>> *Subject: *[Fuel] [Openstack] Problem after reboot fuel-master VM
>>
>> Hello,
>>   I have rebooted the "fuel-master" VM and after that, I cannot access
>> the Fuel UI. What I am missing. Please check the image to see the error.
>>
>> Another question,  How can I rediscover a node that was removed from
>> the pool of available nodes, and also add new nodes to the pool. I clone a
>> fuel-slave node but, it is not recognized by fuel
>>
>> Thanks in advance.
>>
>>
>>
>>
>> __________________________________________________________________________
>> 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
>>
>>
>
>
> --
> Adam Heczko
> Security Engineer @ Mirantis Inc.
>
> __________________________________________________________________________
> 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
>
>


-- 
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
35bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/d7246223/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 15.png
Type: image/png
Size: 55855 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/d7246223/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 32.png
Type: image/png
Size: 21477 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/d7246223/attachment-0001.png>