Services keystone and glance fail to start due to incorrect log file ownership

[Piotr Gacoń]

It seems that each time I install certain openstack service(so far only keystone and glance) there seems to be this persistent issue with starting the service caused by the SERVICENAME.log being owned by root group instead of the service specific group.

CentOS 6.5 on virtualbox
arch x64
Openstack-Icehouse

> First instance with keystone service
> http://docs.openstack.org/icehouse/install-guide/install/yum/content/keystone-install.html

# service openstack-keystone start / failed on the first launch, wrongly root ownership assigned

> solution
# chown keystone:keystone /var/log/keystone/keystone.log
# service openstack-keystone stop
# service openstack-keystone start / works

> info
# keystone --version
0.9.0

> Second instance with the glance service
> http://docs.openstack.org/icehouse/install-guide/install/yum/content/glance-install.html

# service openstack-glance-api start / Failed on the first launch, wrongly root ownership assigned
# service openstack-glance-registry start / This service had the correct group ownership assigned, so it started OK

> solution
# chown glance:glance /var/log/glance/api.log
# service openstack-glance-api stop
# service openstack-glance-api start / works

> info
# glance --version
0.12.0

Please let me know if I've been omitting something or else I think would be helpful to mention in the docs about
changing log ownership after installing openstack services to avoid troubles.

Thanks!

-----------------------------------
Built: 2014-07-17T08:09:50 00:00
git SHA: 3144c8b2fabd57012d88fc9fd39d00c9cc64fb00
URL: http://docs.openstack.org/icehouse/install-guide/install/yum/content/glance-install.html
source File: file:/home/jenkins/workspace/openstack-manuals-tox-doc-publishdocs/doc/install-guide/section_glance-install.xml
xml:id: glance-install

[Gauvain Pocentek (gpocentek)]

The doc indicates that the *-manage commands should be run as the service system user to avoid this kind of problems. Make sure that you didn't run these commands as root.

[Piotr Gacoń (pgacon)]

Gauvain, you right I ran all these commands as root, thanks for the lesson!