luci reports traceback and error in logs: "TypError: No object (name: translator) has been registered for this thread" in RHEL 6
Issue
- luci reports 'TypeError: No object (name: translator) has been registered for this thread'
18:11:17,897 ERROR [luci.lib.ricci_communicator] Error receiving header from node2:11111
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/luci/lib/ricci_communicator.py", line 121, in __init__
hello = self.__receive(self.__timeout_init)
File "/usr/lib64/python2.6/site-packages/luci/lib/ricci_communicator.py", line 503, in __receive
errstr = _('Error reading from %s:%d: %s') \
File "/usr/lib/python2.6/site-packages/pylons/i18n/translation.py", line 106, in ugettext
return pylons.translator.ugettext(value)
File "/usr/lib/python2.6/site-packages/paste/registry.py", line 137, in __getattr__
return getattr(self._current_obj(), attr)
File "/usr/lib/python2.6/site-packages/paste/registry.py", line 197, in _current_obj
'thread' % self.____name__)
TypeError: No object (name: translator) has been registered for this thread
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
luciprior to release0.26.0-37.el6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
