From the log...
[ENGINE] job workout removed from internal queue.
[ENGINE] CAN run job "wake
up.60bf0ac6-a355-460b-a864-992a5fc7c90b"
[ENGINE] JOB ACQUIRED wake
up.60bf0ac6-a355-460b-a864-992a5fc7c90b
[RUNNING THE JOB]
[JOB PROCESSOR FAILED TO START]
Exception: System.ComponentModel.Win32Exception
Message: The system cannot find the file specified
Source: System
at
System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo
startIn
fo)
at System.Diagnostics.Process.Start()
at MyGrid.JobProcessors.Shell.Run(Job job)
[ENGINE] job wake up removed from internal queue.
I'm not sure what file it is looking for, where it is
looking for it, and why it can't find it. What is the
standard location for where the binary files should be?
I'm running Windows2000 Pro and IIS. I can connect to
the cluster through the web interface and all seems
well except the jobs fail to process. I'm using the 0.2
alpha build.
Looks great. We're very excited about this.
-Mark E.
Logged In: YES
user_id=1028741
I think i can shed some light on whats happening here.
I expect you're using the default feed.xml file that came with
the 0.2 distribution.
Unfortunately this file is not suitable for windows, since the
command it actually tries to run is "ls" (linux dir command).
What the shell processor does is look for the executable file in
the engine\processors directory. Since ls.exe is not there, it
throws the exception you get.
try this to confirm if I'm correct:
Copy the net.exe command from your windows\system32
directory to the engine\processors.
edit the feed.xml file on the cluster and change
<Content>ls</Content> to <Content>net.exe</Content>
<Content>-rtl</Content> to <Content>view</Content>
(these are case sensitive)
When you start up, the grid should try to run the jobs which
will now be a "net view" command. you should be able to see
the results come up in the engines console window.
There is a document in the works that includes this
information. Mail me, if you want to see a prelim version of it.