Description of problem: condor_status shows 44 slots, qpid-tool shows # collectors * 44 slots, and cumin shows a variable number. Upon refreshing the Grid:Statistics tab, the Pool Status was observe to go from 15 of 21 idle, to 19 of 24 idle, then 19 of 21 idle, settling on 19 of 19 idle. Version-Release number of selected component (if applicable): cumin-0.1.3037-1.el5 How reproducible: 100%
This can probably be explained by a pool misconfiguration. There were apparently 2 pools with the same name, and slots advertisement order may have been messing with Cumin's internal state. If this isn't just an issue of the pool name being duplicated, this brings up the question of handling slots that advertise themselves to multiple pools.
*** Bug 481754 has been marked as a duplicate of this bug. ***
The final solution we adopted was to stop trying to consolidate duplicate slots and instead rely on getting qmf data from just one collector, for now.
On cumin-0.1.3160-1.el5 on my laptom running qpidd, configured Condor, sesame and postgresql, I am getting this error when trying to show Grid tab: ------------------------------------------------------------------------- APPLICATION ERROR ----- python trace ----- Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/wooly/server.py", line 116, in service response = page.render(session) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 246, in render string = self.do_render(session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 255, in do_render self.__main_tmpl.render(writer, session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 841, in render result = frag(self.__object, session, *args) File "/usr/lib/python2.4/site-packages/wooly/widgets.py", line 53, in render_mode return mode.render(session) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 246, in render string = self.do_render(session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 255, in do_render self.__main_tmpl.render(writer, session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 841, in render result = frag(self.__object, session, *args) File "/usr/lib/python2.4/site-packages/wooly/widgets.py", line 53, in render_mode return mode.render(session) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 246, in render string = self.do_render(session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 255, in do_render self.__main_tmpl.render(writer, session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 841, in render result = frag(self.__object, session, *args) File "/usr/lib/python2.4/site-packages/wooly/widgets.py", line 53, in render_mode return mode.render(session) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 246, in render string = self.do_render(session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 255, in do_render self.__main_tmpl.render(writer, session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 846, in render result = frag.render(session) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 246, in render string = self.do_render(session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 255, in do_render self.__main_tmpl.render(writer, session, *args) File "/usr/lib/python2.4/site-packages/wooly/__init__.py", line 841, in render result = frag(self.__object, session, *args) File "/usr/lib/python2.4/site-packages/cumin/pool.py", line 528, in render_status return record and "<div><span>%i</span> of <span>%i</span> slots idle</div>" % \ TypeError: int argument required -------------------------------------------------------------------------
Excuse me, that was configuration error on my side. Though it could say in a nicer way that condor has CONDOR_HOST set to non-local hostname (in my case it was hostname of my laptop when in office - it wasn't even up).
Verified by examining source code cumin/python/cumin/slot.py
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-0434.html