yahoo-eng-team team mailing list archive

[Joseph Lorenzini <joseph.lorenzini@xxxxxxxxx>]

Public bug reported:

When the keystone package is intalled, it creates the /var/log/keystone
directory, which is initially empty. When the keystone service starts up
for the first time, it needs to write to /var/log/keystone/keystone.log.
The init service creates the file as root and does not change the
ownership of the file from the root user to the keystone user. As a
result, the daemon crashes because it cannot write to the file.

The init script should execute a chmod on the log file each time it
starts up so that this problem is avoid.

** Affects: keystone
     Importance: Undecided
         Status: New

** Description changed:

- When the keystone package it creates the /var/log/keystone directory,
- which is initially empty. When the keystone service starts up for the
- first time, it needs to write to /var/log/keystone/keystone.log. The
- init service creates the file as root and does not change the ownership
- of the file from the root user to the keystone user. As a result, the
- daemon crashes because it cannot write to the file.
+ When the keystone package is intalled, it creates the /var/log/keystone
+ directory, which is initially empty. When the keystone service starts up
+ for the first time, it needs to write to /var/log/keystone/keystone.log.
+ The init service creates the file as root and does not change the
+ ownership of the file from the root user to the keystone user. As a
+ result, the daemon crashes because it cannot write to the file.
  
  The init script should execute a chmod on the log file each time it
  starts up so that this problem is avoid.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1319049

Title:
  keystone log is owned by root after initial install

Status in OpenStack Identity (Keystone):
  New

Bug description:
  When the keystone package is intalled, it creates the
  /var/log/keystone directory, which is initially empty. When the
  keystone service starts up for the first time, it needs to write to
  /var/log/keystone/keystone.log. The init service creates the file as
  root and does not change the ownership of the file from the root user
  to the keystone user. As a result, the daemon crashes because it
  cannot write to the file.

  The init script should execute a chmod on the log file each time it
  starts up so that this problem is avoid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1319049/+subscriptions