Status code = 39204
ERROR: Failed to open project
I am getting this error when trying to automate job log retreval from the command line using the dsjob app. I start getting this error for every log entry after about 200 jobs into the list of jobs we have.
Basically it goes like this:
Get list of all jobs
For each job
get list of all FATAL log entries
get detailed information for each FATAL entry
get list of all WARNING log entries
get detailed information for each WARNING entry
end
I'm using
to get list of jobs: dsjob -server server -user user -password password -ljobs project
to get list of warning/fatal: dsjob -server server -user user -password password -logsum -type FATAL project job
to get detailed info: dsjob -server server -user user -password password -logdetail projcet job_name log_entry_id
I can't find documentation about this Status code anywhere, its only mentioned once in this forum (a similar question as mine with 0 responses) and googling gives 0 results. Any help would be greatly appreciated. Let me know if you need any more info from me.
Status code = 39204
Moderators: chulett, rschirm, roy
Not sure how much help this is going to be, but grepping through my install shows this status code in the $DSHOME/gcidir/include/api_public.h header file:
I'd suggest contacting Support. One question - how are you actually kicking off all of these processes? Perhaps you are swamping your machine, running things too quickly or too close together and running out of resources?
Code: Select all
#define IE_SR_SLAVE_EXEC_FAIL 39204 /* The slave failed to start correctly */I'd suggest contacting Support. One question - how are you actually kicking off all of these processes? Perhaps you are swamping your machine, running things too quickly or too close together and running out of resources?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
chulett wrote:I'd suggest contacting Support. One question - how are you actually kicking off all of these processes? Perhaps you are swamping your machine, running things too quickly or too close together and running out of resources?
Yeah I guess that is my next step. I am kicking these off with a shell script, and I even tried putting sleeps in my shell script. I have spleeps of 2 seconds after each call to dsjob but even changing that from 2 seconds to 20 seconds yields the same results.
