Why does ceilometer-agent-central throw "ERROR ceilometer.openstack.common.loopingcall [-] in fixed duration looping call"? [closed]

asked 2013-08-30 17:58:02 -0600

mulz gravatar image

updated 2013-09-26 13:13:43 -0600

nickchase gravatar image

I am installing Ceilometer to query Swift object usage.

My Swift configuration is the following:

2 proxy nodes, 3 storage nodes and 1 management server.

On the management server I have installed the following Ceilometer components: ceilometer-agent-central, ceilometer-collector and ceilometer-api

I have religiously followed the instructions in http://docs.openstack.org/developer/ceilometer/install/manual.html#installing-manually

After installing everything and creating the reselleradmin etc. as per the link, when I launch ceilometer-collector and ceilometer-agent-central, I get the following:

# ceilometer-collector &
[3] 32078
# 2013-08-30 18:41:50.307 32078 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
2013-08-30 18:41:50.308 32078 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
Fri Aug 30 18:41:50.394 [initandlisten] connection accepted from 127.0.0.1:33765 #4 (1 connection now open)
# 2013-08-30 18:43:00.703 32115 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
2013-08-30 18:43:00.705 32115 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
Fri Aug 30 18:43:00.795 [initandlisten] connection accepted from 127.0.0.1:33767 #5 (1 connection now open)


# ceilometer-agent-central &
[3] 2225
# 2013-08-30 18:55:47.338 2225 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
2013-08-30 18:55:47.339 2225 WARNING ceilometer.publisher.rpc [-] Publishing policy is unknown (wait) force to default
2013-08-30 18:55:47.765 2225 ERROR ceilometer.openstack.common.loopingcall [-] in fixed duration looping call
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall Traceback (most recent call last):
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/ceilometer/openstack/common/loopingcall.py", line 78, in _inner
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall     self.f(*self.args, **self.kw)
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/ceilometer/central/manager.py", line 75, in interval_task
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall     auth_url=cfg.CONF.service_credentials.os_auth_url)
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 139, in __init__
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall     self.authenticate()
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/keystoneclient/httpclient.py", line 458, in authenticate
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall     resp, body = self.get_raw_token_from_identity_service(**kwargs)
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 160, in get_raw_token_from_identity_service
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall     token=token)
2013-08-30 18:55:47.765 2225 TRACE ceilometer.openstack.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/keystoneclient/v2_0/client.py", line 189, in _base_authN
2013-08-30 18 ...
(more)
edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by mrhillsman
close date 2018-12-02 21:32:45.335523

Comments

Can you paste the output of /etc/ceilometer/policy.json file?

Jobin gravatar imageJobin ( 2013-08-30 21:36:33 -0600 )edit

Do you have keystone installed ? It is Unauthorized error

guangyu gravatar imageguangyu ( 2013-08-30 22:22:36 -0600 )edit
1

Yes... Look the output below from the shell: # keystone --version 0.3.2 # keystone user-list WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored). +----------------------------------+------------+---------+------------------------+ | id | name | enabled | email | +----------------------------------+------------+---------+------------------------+ | 0142de4513104407956a92988bda4288 | admin | True | | | f7fb054a0f1648d9bab9799c082dd148 | ceilometer | True | ceilometer@example.com | | 1d9acdc6157c48b08d98199a5571a0c0 | cinder | True | | | 378c975aa43948968555f9f9e6f92c61 | glance | True | | | facdf22ccf444de08daa14ab7511955e | nova | True | | +----------------------------------+------------+---------+------------------------+

mulz gravatar imagemulz ( 2013-08-30 23:12:27 -0600 )edit

{ "context_is_admin": [["role:admin"]] }

mulz gravatar imagemulz ( 2013-08-30 23:13:21 -0600 )edit

were u guys able to fix this?

koolhead17 gravatar imagekoolhead17 ( 2014-02-03 12:45:47 -0600 )edit