"unable to monitor process, the parameter is incorrect"

[trimbo]

Hi,

I'm trying to configure the win32 version of Qube on Windows x64, due to:

a) We'd like to use a Python backend
b) We have compiled Python plugins for x86 that we'd like to continue to use.
c) The Windows x64 version of Qube does not include a Python module for Python 2.4

In any case, jobs immediately fail.  Even "dir C:\" fails.  Nothing is reported back to the Qube GUI and the only thing I can find in the worker log that sorta appears like an error is this:

"unable to monitor process: 3928 - The parameter is incorrect."

The really unfortunate thing is that I just had this working yesterday with a custom Python backend, though it wasn't working with "qbsub dir C:\".  However, now it's not working with the Python backend and I can't figure out if this is the error that's causing the problem, or if it's some other error that isn't reported anywhere.

Or is this because you can't run the x86 client of Qube on x64?  I browsed around the forum yesterday and it seemed like others were doing that, and was able to run some stuff this way when I tried it.

Thanks,
  Chris

[trimbo]

I think I figured it out.

The problem is that Qube doesn't fix environment variables when I uninstalled x64 and reinstalled x86.  It leaves QBDIR in an ugly state like "C:\Program Files\pfx\qube;C:\Program Files (x86)\pfx\qube", which doesn't play well with scripts and code that requires this. 

Apparently Qube's default C++-built types require this to be set to just one path, because standard qbsub started working once I fixed it.

Hope this helps if someone runs across this problem in the future.

[anthony]

Hey Trimbo,

   It looks like you solved your own installation issues... although I do have a question about the QBDIR.  The value itself should be a single directory.  It's not a PATH type value, indicating a search path.  Most of qube!'s tools use that path to find other components such as the job types, etc.

  As far as python x86 and x64 mingling, we supply the x64 plugins for python with the x64 installer.  Unfortunately, most binary applications if not all, do not support cross loading plugins.  So the 32 bit version of python does not work with the 64 bit version of Qube!

   Please let us know if you have any other questions.

    Thanks,
          Anthony

[trimbo]

   It looks like you solved your own installation issues... although I do have a question about the QBDIR.  The value itself should be a single directory.  It's not a PATH type value, indicating a search path.  Most of qube!'s tools use that path to find other components such as the job types, etc.

Correct.  The qube installer/uninstaller left it in that "search path" configuration, which I then had to fix manually to get Qube working again.  You may want to investigate the installer at some point in the future.  It may only be an issue when "C:\Program Files" changes to "C:\Program Files (x86)" between installs, which not that many people probably run into.

Thanks,
  Chris

[kewboard]

Well I am having the same problem, We just shifted from an old server to a new file server and qube was working fine on the old server but now I am getting this same error in the worker log "unable to monitor process, the parameter is incorrect".

The job wont even show up in Qube GUI. Its writing the log files but only the .hist, .qja, .xja and .sts files.  No .out or .err files were created.

I have checked the permission on the share folder and qubeproxy has full permissions . The problem is that I am not getting any errors any where except this one in the worker log.  Please help!!!!

We are using Qube5.2

[kewboard]

one correction, it is showing up in Qube Gui.