keystone sometime fails to come up during provisioning due to log file permission
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
Fix Released
|
High
|
Senthilnathan Murugappan | ||
R2.0 |
New
|
High
|
Senthilnathan Murugappan |
Bug Description
3.0 3.0-2507~
In this sanity run, keystone failed to come up : http://
On restart of keystone, it came up fine.
keystone.log :
=============
Traceback (most recent call last):
File "/usr/bin/
config.
File "/usr/lib/
log.
File "/usr/lib/
_setup_
File "/usr/lib/
filelog = logging.
File "/usr/lib64/
logging.
File "/usr/lib64/
StreamHandl
File "/usr/lib64/
stream = open(self.
IOError: [Errno 13] Permission denied: '/var/log/
[root@a6s44 ~]# ls -l /var/log/ |grep keystone
drwxr-x--- 2 keystone keystone 4096 Dec 21 20:57 keystone
[root@a6s44 ~]# ls -l /var/log/keystone/
total 8
-rw-r--r-- 1 keystone keystone 6030 Dec 19 17:07 keystone.log
[root@a6s44 ~]#
[root@a6s44 ~]# service keystone restart
keystone: ERROR (not running)
keystone: started
[root@a6s44 ~]# service keystone status
keystone RUNNING pid 22333, uptime 0:00:03
[root@a6s44 ~]#
Changed in juniperopenstack: | |
assignee: | Ignatious Johnson Christopher (ijohnson-x) → Senthilnathan Murugappan (msenthil) |
Changed in juniperopenstack: | |
status: | Fix Committed → Fix Released |
Reviewed: https:/ /review. opencontrail. org/5872 github. org/Juniper/ contrail- packaging/ commit/ fcafd0238cd1efa 90250d217b44468 e058f02fa9
Committed: http://
Submitter: Zuul
Branch: master
commit fcafd0238cd1efa 90250d217b44468 e058f02fa9
Author: Senthilnathan Murugappan <email address hidden>
Date: Mon Dec 22 16:37:43 2014 -0800
Fixing permission denied issue for openstack comp. log files
Issue: <comp>/ <comp>. log
When openstack components were started we observe permission denied issue
for /var/log/
Reason: <comp>/ <comp>. log
On certain supervisor ini file for openstack components we have configured
the stdout and stderr to be redirected to the same /var/log/
file used by the process. Due to which the logfiles were created with root uid
where as the components were started using their own uid hence they didnt have
permission to write to the logfile
Change-Id: I6f6260fa68e9a6 9463293b1246281 477cd2170fe
Closes-Bug: #1404789