SIGINT in Director

dougcl · Post by **dougcl** » Tue Jul 20, 2010 12:46 pm

Hi folks, starting today, if I try to run jobs from Director, I get a job abortion with SIGINT. Jobs run fine when started in DS Designer. Ideas?

Thanks,
Doug

anbu · Post by **anbu** » Tue Jul 20, 2010 12:57 pm

Search the forum with the keyword "SIGINT"

dougcl · Post by **dougcl** » Tue Jul 20, 2010 1:12 pm

anbu wrote:Search the forum with the keyword "SIGINT"

Maybe someone has a better answer?

Thanks,
Doug

kris007 · Post by **kris007** » Tue Jul 20, 2010 1:24 pm

Is this a Job Sequence or just a parallel job? Are you getting any warnings before you get the SIGINT error. Can you post any warnings from director log? Couple of reasons why SIGINT error occurs is when someone tries to stop the job or if the number of warnings exceed the limit mentioned in the Job Run options.

dougcl · Post by **dougcl** » Tue Jul 20, 2010 1:32 pm

kris007 wrote:Is this a Job Sequence or just a parallel job? Are you getting any warnings before you get the SIGINT error. Can you post any warnings from director log? Couple of reasons why SIGINT error occurs is when someone tries to stop the job or if the number of warnings exceed the limit mentioned in the Job Run options.

Great thanks. This is just a parallel job. There are a bunch of "standard" warnings that I get running it either way. There is a pair of warnings on each input column:

Code: Select all

The modify operator has a binding for the non-existent output field

and

Code: Select all

The modify operator keeps field

This is due to the fact that I am identifying only a few columns in my SELECT statement, but the link has the full db table def associated to it. Getting around these warnings would be nice. Not sure if it's separate issue (hopefully it is). In any case, if these warnings are related, I think it would mean that the warning limit is different in Director and Designer. Really?

Thanks,
Doug

chulett · Post by **chulett** » Tue Jul 20, 2010 2:32 pm

The default warning limit is indeed different between Designer and Director (0 v. 50) but there's nothing stopping you from ensuring both run with the same values.

ray.wurlod · Post by **ray.wurlod** » Tue Jul 20, 2010 3:41 pm

Disable RCP to see whether that resolves the issue. If it does, try to discover why the additional, unspecified columns might have raised an interrupt signal.

dougcl · Post by **dougcl** » Tue Jul 20, 2010 5:39 pm

ray.wurlod wrote:Disable RCP to see whether that resolves the issue. If it does, try to discover why the additional, unspecified columns might have raised an interrupt signal.

Hi,
RCP is not enabled. I'm not sure that these warnings have anything to do with it. Again, the jobs run just fine when launched from Designer, warnings and all.

Thanks,
Doug

ray.wurlod · Post by **ray.wurlod** » Tue Jul 20, 2010 8:07 pm

Is JobMonApp running or disabled? Are you collecting performance statistics when running from Director?

chulett · Post by **chulett** » Tue Jul 20, 2010 9:22 pm

Again, unless you override the values, the default warning limit in the Director is 50 while from the Designer it is zero - unlimited. Which could explain part of your issue with the Director but still shouldn't result in a SIGINT as far as I know.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 21, 2010 12:51 am

dougcl wrote:... starting today ...

What's changed since the day beore today?

"Nothing" is clearly not the correct answer.

dougcl · Post by **dougcl** » Wed Jul 21, 2010 5:04 pm

ray.wurlod wrote:Is JobMonApp running or disabled? Are you collecting performance statistics when running from Director?

Not sure about the former. I'm not sure how to check this. For the latter, I do not have the jobs set to record performance data on the job properties execution tab.

Regarding the problem starting yesterday, it is more accurate to say that I haven't tried to run from director in a week or so. Last time I tried it, it was fine, but many things were added to the jobs since then.

It seems really odd to me that something runs perfectly well in designer, but fails in director. I would think this can only happen in very specific ways. It's unfortunate as well that whatever it is, it's unhandled.

Thanks,
Doug

kris007 · Post by **kris007** » Wed Jul 21, 2010 7:05 pm

dougcl wrote: Last time I tried it, it was fine, but many things were added to the jobs since then. Doug

There lies your answer. You will have to figure out what component that was added might have caused this issue. I asked earlier but I'll ask again. Are there any warnings in your director log that is causing the job to fail? Usually the default value in director is 50 warnings. Do you see 50 warnings in your director log when you run the job both from the Director and Designer?

dougcl · Post by **dougcl** » Thu Jul 22, 2010 11:07 am

Hi folks, increasing the warning limit in Director fixed the problem. Thanks to kris007 and chulett for that answer.

Thanks,
Doug

DSXchange

SIGINT in Director

SIGINT in Director

Re: SIGINT in Director