Description of problem:
luci and ricci - probing of storage on remote system can result in luci zope
process tying up 90% of memory - the process is also not killed when the luci
service is stopped.
This may be (partially?) due to network delays, but I'm seeing situations where
an attempt to probe the storage of a remote node (i.e., a node other than the
node running luci - although all the nodes are local to the same subnet) can
take several (10+) minutes. At this point, this process ties up 90%+ of the
/usr/bin/python /usr/lib/luci/zope/lib/python/Zope2/Startup/run.py -C
Stopping the luci service does not kill this process.
Version-Release number of selected component (if applicable):
luci-0.8-21.el5 and ricci-0.8-21.el5
~75% of the time
Steps to Reproduce:
1. Access storage of a remote system via luci
Storage information is not reported by luci - zope process listed above ties up
90% of memory.
The storage should be reported - if it's a network timing issue, we should have
Unable to recreate this problem with:
Marking the bz as verified.