[openstack-dev] [ceilometer] zombie process after ceilometer-api
Hi, I see a zombie process left out by ceilometer-api after a client command like "ceilometer meter-list". This seems to occur only when I change the number of workers for [api] section in ceilometer.conf to 2 or more. With default value of workers = 1, there is no zombie. Has anybody encountered this problem ? OR is there already a bug to tackle this ? Thanks, Madhu Mohan __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [ceilometer] zombie process after ceilometer-api
Here is the output of "ps aux | grep ceilometer-api" after "ceilometer meter-list" ceilome+ 27192 1.0 1.1 247400 60388 ?Ss 14:10 0:00 /usr/bin/python /usr/bin/ceilometer-api --config-file=/etc/ceilometer/ceilometer.conf --logfile=/var/log/ceilometer/api.log ceilome+ 27655 15.3 0.0 0 0 ?Z14:11 0:00 [ceilometer-api] Its the second line I am concerned about. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Integration Demo
Hi All, I have been working on integrating developing a policy demo using Congress. I have done following activities in this direction - Integrated Congress as a service with keystone - Developed a trivial Python-Congressclient with support for basic commands through command line - Integrated congress and python-congressclient into devstack To verify the integration, I am using the example policy files (VM Grouping policy) as input and trying to see the policies being written to the Congress tables and the Data source tables. Could some one help me out understand what are the other missing parts to get this integration working ? What needs to be implemented from the Congress server side ? I am particularly interested in Contributing to all areas of Congress including policy definition, enforcement and also have special interests in run-time optimization, high-availability use-cases. Any guidance would be of utmost help. Thanks and Regards, Madhu Mohan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Congress] Error running scripts/run_api_server
Hi,
I recently cloned the latest Congress source code and tried to run
unit-tests on my Ubuntu PC. Using *scripts/run_api_server*, I found this
following error:
*Jun 20 11:28:11|0|__main__|INFO|Starting congress server*
*Traceback (most recent call last):*
* File /usr/lib/python2.7/dist-packages/eventlet/greenpool.py, line 80,
in _spawn_n_impl*
*func(*args, **kwargs)*
* File server.py, line 82, in ad_update_thread*
*ad_model.update_from_ad() # XXX: blocks eventlet*
* File /home/madhu/Project/policyFW/congress/congress/server/ad_sync.py,
line 72, in update_from_ad*
*l.simple_bind_s(BIND_USER, BIND_PW)*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 206, in
simple_bind_s*
*msgid = self.simple_bind(who,cred,serverctrls,clientctrls)*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 200, in
simple_bind*
*return
self._ldap_call(self._l.simple_bind,who,cred,EncodeControlTuples(serverctrls),EncodeControlTuples(clientctrls))*
* File /usr/lib/python2.7/dist-packages/ldap/ldapobject.py, line 96, in
_ldap_call*
*result = func(*args,**kwargs)*
*SERVER_DOWN: {'desc': Can't contact LDAP server}*
*(5065) wsgi starting up on http://0.0.0.0:8080/ http://0.0.0.0:8080/*
Does other guys face this error too ?
Am i missing any prerequisite to run the congress unit-test ?
make was successful and had no issues.
Please suggest a way to proceed further.
Thanks and Regards,
Madhu Mohan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
