Job failing when scheduled through Director

chulett · Post by **chulett** » Tue Jun 22, 2010 9:42 pm

Singleton schedules use "at" on UNIX, it's only recurring schedules (like 'every') that use "cron".

swades · Post by **swades** » Wed Jun 23, 2010 12:44 pm

chulett wrote:Singleton schedules use "at" on UNIX, it's only recurring schedules (like 'every') that use "cron".

Thanks Craig.

Now I am wondering what is the difference, schedule through "at" vs through "cron". Schedule through "cron" failing with permission issue.

Thanks.

ray.wurlod · Post by **ray.wurlod** » Wed Jun 23, 2010 5:19 pm

Maybe the user ID is registered in cron.allow but not in at.allow. Ask your UNIX administrator to check.

chulett · Post by **chulett** » Wed Jun 23, 2010 8:23 pm

Or the other way 'round.

That would usually be the answer to the question if the attempt to schedule the job had failed. Since we're not talking about the 'Add to Schedule' step but rather the actual scheduled run, something else is going on, some kind of difference in the environments between the two schedulers.

Heck if I know what that might be however. In your shoes I would involve both your SysAdmins and your official support provider to help nail down where the responsibility for this lies.

dganeshm · Post by **dganeshm** » Thu Oct 21, 2010 9:07 am

Please check your LD_LIBRARY_PATH and make sure the library file being referenced is part of you LD_LIBRARY_PATH