thread related error upon Spyce server startup

Hi,

I'm getting the following error trying to start up the Spyce
server on a Xen-hosted Slackware VPS:

# python spyceCmd.py -d /var/run/spyce.pid -l

# Spawning another server (for check_modules_and_restart option)
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
    self.run()
  File "/usr/lib/python2.4/threading.py", line 422, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/root/spyce-2.1/spyceWWW.py", line 330, in run
    def run(): exit_wrapper[0] = os.waitpid(pid, 0)
OSError: [Errno 10] No child processes

Traceback (most recent call last):
  File "spyceCmd.py", line 301, in ?
    try: sys.exit(spyceMain(cgimode=0))
  File "spyceCmd.py", line 225, in spyceMain
    return spyceWWW.spyceHTTPserver(configFile, daemon=daemon)
  File "/root/spyce-2.1/spyceWWW.py", line 348, in spyceHTTPserver
    exit_code = exit_wrapper[0][1]
TypeError: unsubscriptable object


This does not occur on a (nearly identically set-up) OpenVZ VPS.
Any clues as to what's going on?

Could this have to do with the fact that TLS has to be disabled
on Xen?  Or the fact that the 32-bit Slackware image was being
hosted on Xen running on a 64-bit Opteron machine?

Is there a possible workaround for this and/or does the Spyce
server thread spawning code need to made more robust?


________________________________________________
Message sent using UebiMiau 2.7.9



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/