Job under control failed to start

ray.wurlod · Post by **ray.wurlod** » Mon Jun 04, 2007 2:19 am

Has anyone seen this happen? Like to advance a cogent explanation?

The job controller reported (-14) that the job under control failed to start within the 60 seconds allowed. The job run request was made at 4:39:08 and the failure was reported at 4:40:10, at which time the job controller aborted, the abort having been generated in DSRunJob(). The code did not get to DSWaitForJob().

However, the job under control DID start, logging its start time as 4:40:30 - some 20 seconds after it had been reported as failing to start.

Its log events showed that it was run under control of the now aborted job controller, and it finished (still under control) some 15 minutes later with no warnings or errors.

There was nothing of interest left in &PH&, and - because of the "under control" events - it is safe to say that the job was not run manually.

The controlling job is a job control routine that's been around since 2003, before job sequences were invented. The folks here say that this behaviour has occurred on a couple of other occasions, sometimes in different (production) projects on the same server.

Eight CPUs are barely ticking over (%Idle > 95%) and very little of the available memory being consumed. This most recent example occurred when only this control job was started immediately after rebooting the server. Demand for other resources was close enough to zero - just the ODBC drivers being called from the controlled job.

There is no before-job or before-stage subroutine in the controlled job. It contains two Transformer stage, one performing eight lookups, the other performing some calculations into three output links. 15 minutes is its usual execution time.

chulett · Post by **chulett** » Mon Jun 04, 2007 6:41 am

Wow... I so want to say "Have you searched the forums?" or "What did your official Support provider have to say when you asked them?" but I guess I won't. :wink:

Sorry, but I for one don't recall ever seeing this particular behaviour, but then I haven't seen anything near the variety of installs that you have. I've seen times where the call to DSRunJob seems to 'crash' internally and our job control never returns from that call. However, there's no error involved. Controlled jobs finish normally but the JC is basically comatose and thus won't start anything new. Takes a PID kill and a status file reset to resolve.

Which flavor of Windows, by the way?

And I know, not all that cogent, but I didn't want you to languish here without something in the way of a reply.

ray.wurlod · Post by **ray.wurlod** » Mon Jun 04, 2007 9:46 pm

Windows 2003 Server, sp1. 7.5GB memory (!), four dual-core CPUs (not sure of speed of these). Spare capacity of all kinds, though only 12GB free on disk where Projects installed. The annoying thing was, having re-booted, that NOTHING else was happening at the time.