← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1764272] [NEW] no records logged which show that httpd.service is dead

 

Public bug reported:

There are no records logged which show that httpd.service is dead. The
error is logged in /var/log/messages, this can make it difficult for the
administrator to trace the error because /var/log/messages contains the
general purpose error logs for overall system.

As keystone service runs inside httpd, the non-availability of httpd can
make the entire openstack environment stop working.

To avoid this issue, there can be two possible solutions:
Log the error message in component level log. Here the error message should be logged in keystone.log so that monitoring remains within keystone component. In this case, changes should be done in keystone client end.
High level monitoring mechanism such as email containing the error message can also be sent to admin so that monitoring can be made more convenient.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1764272

Title:
  no records logged which show that httpd.service is dead

Status in OpenStack Identity (keystone):
  New

Bug description:
  There are no records logged which show that httpd.service is dead. The
  error is logged in /var/log/messages, this can make it difficult for
  the administrator to trace the error because /var/log/messages
  contains the general purpose error logs for overall system.

  As keystone service runs inside httpd, the non-availability of httpd
  can make the entire openstack environment stop working.

  To avoid this issue, there can be two possible solutions:
  Log the error message in component level log. Here the error message should be logged in keystone.log so that monitoring remains within keystone component. In this case, changes should be done in keystone client end.
  High level monitoring mechanism such as email containing the error message can also be sent to admin so that monitoring can be made more convenient.

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


Follow ups