Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working
Hi, Thanks for your response Chris, Ceilometer-api Pls let me know if /etc/ceilometer/ceilometer.conf file is correct: [DEFAULT] # # Options defined in ceilometer.middleware # # Exchanges name to listen for notifications (multi valued) http_control_exchanges=nova http_control_exchanges=glance http_control_exchanges=neutron http_control_exchanges=cinder # # Options defined in ceilometer.pipeline # # Configuration file for pipeline definition (string value) pipeline_cfg_file=pipeline.yaml # # Options defined in ceilometer.sample # # Source for samples emited on this instance (string value) #sample_source=openstack # # Options defined in ceilometer.api.app # # The strategy to use for auth: noauth or keystone. (string # value) auth_strategy=keystone # Deploy the deprecated v1 API. (boolean value) #enable_v1_api=true # # Options defined in ceilometer.compute.notifications # # Exchange name for Nova notifications (string value) nova_control_exchange=nova # # Options defined in ceilometer.compute.pollsters.util # # list of metadata prefixes reserved for metering use (list # value) reserved_metadata_namespace=metering. # limit on length of reserved metadata values (integer value) #reserved_metadata_length=256 # # Options defined in ceilometer.compute.virt.inspector # # Inspector to use for inspecting the hypervisor layer (string # value) #hypervisor_inspector=libvirt # # Options defined in ceilometer.compute.virt.libvirt.inspector # # Libvirt domain type (valid options are: kvm, lxc, qemu, uml, # xen) (string value) #libvirt_type=kvm # Override the default libvirt URI (which is dependent on # libvirt_type) (string value) #libvirt_uri= # # Options defined in ceilometer.image.notifications # # Exchange name for Glance notifications (string value) glance_control_exchange=glance # # Options defined in ceilometer.network.notifications # # Exchange name for Neutron notifications (string value) neutron_control_exchange=neutron # # Options defined in ceilometer.objectstore.swift # # Swift reseller prefix. Must be on par with reseller_prefix # in proxy-server.conf. (string value) #reseller_prefix=AUTH_ # # Options defined in ceilometer.openstack.common.db.sqlalchemy.session # # the filename to use with sqlite (string value) #sqlite_db=ceilometer.sqlite # If true, use synchronous mode for sqlite (boolean value) #sqlite_synchronous=true # # Options defined in ceilometer.openstack.common.eventlet_backdoor # # Enable eventlet backdoor. Acceptable values are 0, , # and :, where 0 results in listening on a random # tcp port number; results in listening on the # specified port number (and not enabling backdoor if that # port is in use); and : results in listening on # the smallest unused port number within the specified range # of port numbers. The chosen port is displayed in the # service's log file. (string value) #backdoor_port= # # Options defined in ceilometer.openstack.common.lockutils # # Whether to disable inter-process locks (boolean value) #disable_process_locking=false # Directory to use for lock files. (string value) #lock_path= # # Options defined in ceilometer.openstack.common.log # # Print debugging output (set logging level to DEBUG instead # of default WARNING level). (boolean value) #debug=false # Print more verbose output (set logging level to INFO instead # of default WARNING level). (boolean value) #verbose=false # Log output to standard error (boolean value) #use_stderr=true # format string to use for log messages with context (string # value) #logging_context_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user)s %(tenant)s] %(instance)s%(message)s # format string to use for log messages without context # (string value) #logging_default_format_string=%(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s # data to append to log format when level is DEBUG (string # value) #logging_debug_format_suffix=%(funcName)s %(pathname)s:%(lineno)d # prefix each line of exception output with this format # (string value) #logging_exception_prefix=%(asctime)s.%(msecs)03d %(process)d TRACE %(name)s %(instance)s # list of logger=LEVEL pairs (list value) #default_log_levels=amqplib=WARN,sqlalchemy=WARN,boto=WARN,suds=INFO,keystone=INFO,eventlet.wsgi.server=WARN # publish error events (boolean value) #publish_errors=false # make deprecations fatal (boolean value) #fatal_deprecations=false # If an instance is passed with the log message, format it # like this (string value) #instance_format="[instance: %(uuid)s] " # If an instance UUID is passed with the log message, format # it like this (string value) #instance_uuid_format="[instance: %(uuid)s] " # If this option is specified, the logging configuration file # specified is used and overrides any other logging options # specified. Please see the Python logging module # documentation for details on logging configuration files. # (string v
Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working
On Mon, 20 Oct 2014, david jhon wrote: 2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service CommunicationError: Error communicating with http://193.168.4.121:8777 [Errno 111]$ 2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service How do I fix it? It looks like it may be that either your ceilometer-api service is not running or is not bound to the correct network interface. Since you've got a ceilometer-api.log is may be that the service is unreachable because of some configuration setting (firewall, alarm and api service on different networks, that sort of thing). -- Chris Dent tw:@anticdent freenode:cdent https://tank.peermore.com/tanks/cdent ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working
Hi,
Just opened /var/log/ceilometer/ceilometer-alarm-evaluator.log file and
found following errors:
2014-10-20 16:32:15.263 23166 TRACE ceilometer.alarm.service
2014-10-20 16:33:07.854 30437 ERROR ceilometer.alarm.service [-] alarm
evaluation cycle failed
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service Traceback
(most recent call last):
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometer/alarm/service.py", line 96, in$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service alarms =
self._assigned_alarms()
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometer/alarm/service.py", line 139, i$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service 'value':
True}])
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometerclient/v2/alarms.py", line 61, $
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service return
self._list(options.build_url(self._path(), q))
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometerclient/common/base.py", line 57$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service resp, body
= self.api.json_request('GET', url)
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometerclient/common/http.py", line 18$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service resp,
body_iter = self._http_request(url, method, **kwargs)
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service File
"/usr/lib/python2.7/dist-packages/ceilometerclient/common/http.py", line 15$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service raise
exc.CommunicationError(message=message)
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service
CommunicationError: Error communicating with http://193.168.4.121:8777
[Errno 111]$
2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service
How do I fix it?
On Mon, Oct 20, 2014 at 4:02 PM, david jhon wrote:
> Hi all,
>
> I am working with Ceilometer, Havana-All-in-one on Ubuntu 12.04.
> Initially, ceilometer configuration installed four ceilometer services:
>
> ceilometer-agent-central
> ceilometer-agent-compute
> ceilometer-api
> ceilometer-collector
>
> but later I came to know that there should be two other services running
> as well: ceilometer-alarm evaluator, ceilometer-alarm-notifier, I installed
> these services as given on the link:
> http://www.brucemartins.com/2014/03/openstack-havana-ceilometer-alarm.html
>
> I created alarm at a resource by using this command: ceilometer -k
> alarm-threshold-create --name tester_cpu_high --description 'overheating?'
> --meter-name cpu_util --threshold 3.0 --comparison-operator gt --statistic
> avg --period 10 --query resource_id=e0bbdad3-ebdb-4acd-8fb5-cd2e10bb10f4
>
> but whenever I check the status of alarm, it shows me 'insufficient data'
> status.
>
> I tested it by running different applications on my instance but they made
> no change in alarm_status.
>
> Here is the log from /var/log/ceilometer/ceilometer-agent-compute.log:
>
> 2014-10-20 15:37:13.957 23126 WARNING ceilometer.transformer.conversions
> [-] dropping sample with no predecessor: 2014-10-20 15:37:14.023 23126 WARNING ceilometer.transformer.conversions
> [-] dropping sample with no predecessor:
> /var/log/ceilometer/ceilometer-api.log :
>
> 2014-10-20 15:37:10.652 23136 INFO keystoneclient.middleware.auth_token
> [-] Starting keystone auth_token middleware
> 2014-10-20 15:37:10.653 23136 INFO keystoneclient.middleware.auth_token
> [-] Using /tmp/keystone-signing-bGIm6r as cache directory for signing c$
> 2014-10-20 15:37:13.039 23136 INFO keystoneclient.middleware.auth_token
> [-] Starting keystone auth_token middleware
> 2014-10-20 15:37:13.039 23136 INFO keystoneclient.middleware.auth_token
> [-] Using /tmp/keystone-signing-y7L_NW as cache directory for signing c
>
> Please tell me which step is missing or what exact procedure should be
> followed in order to monitor a meter for a resource.
>
> Moreover, what steps should be taken in order to add new meter. How would
> I debug ceilometer source code in /usr/lib/python2.7/ceilometer/* if I
> follow the following link:
> http://docs.openstack.org/developer/ceilometer/contributing/plugins.html
>
> Thank you!
>
>
> Regards,
> Jhon David
>
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
