Marking this as "invalid". I have seen keystone successfully use the
logging.conf setup to channel to remote syslog. the "use systlog" option
is something we should probably look at eliminating as it doesn't seem
to do what people expect.
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1245510
Title:
syslog setting does not work in keystone
Status in OpenStack Identity (Keystone):
Invalid
Bug description:
1. Enable syslog in keystone.conf
/etc/keystone/keystone.conf:
use_syslog = True
2. Modify the logging setting in keystone/logging.conf
/etc/keystone/logging.conf:
[handler_production]
class=handlers.SysLogHandler
level=ERROR
formatter=normal
args=(('[2001:2013:xx...xx]', handlers.SYSLOG_UDP_PORT),
handlers.SysLogHandler.LOG_USER)
#args=(('localhost', handlers.SYSLOG_UDP_PORT),
handlers.SysLogHandler.LOG_USER)
--> still the logging is written in the localhost syslog
Ref.
https://lists.launchpad.net/openstack/msg20020.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1245510/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
