[openstack-dev] [Cinder] The way to get traces of compiling fails when cinder service restarts

Chinmaya Bharadwaj acbharadwaj at gmail.com
Thu Apr 28 06:27:14 UTC 2016


hi,

Try running it  on the  foreground, instead as a background service.

Something like :

/usr/local/bin/cinder-volume --config-file /etc/cinder/cinder.conf




#Chinmaya

On 28 April 2016 at 11:50, 박준하 <pjh03 at kinx.net> wrote:

> Hi all,
>
>
>
> I’m a beginner of Openstack.
>
> I tried to modified some sources in Cinder directories for studying and
> restart services such as cinder-api, cinder-volume, cinder-scheduler.
>
> But, I could not discover any compile error on ‘/var/log/*’
>
> I want to watch compile errors with python Traceback.
>
> Is there the best way to debugging on service level?
>
>
>
> Thanks
>
>
>
> Jun-ha Park
>
> Dept. Cloud Technology group. KINX corp. , Korea
>
> __________________________________________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160428/c7884bcf/attachment.html>


More information about the OpenStack-dev mailing list