From: Gary Jaeger <gary@(email surpressed)>
Subject: nuke
   Date: Fri, 25 Feb 2011 19:12:05 -0500

So we're finally integrating nuke into the rush install. We've been seat of the pants until now. But in my simple tests I can't get the submit right. 

I've changed this part of the submit to reflect our nuke install:

elsif ( $G::ismac )
{
   ### MAC
   $ENV{PATH} = "/Applications/Nuke6.2v1/Nuke6.2v1.app:$ENV{PATH}";
   $ENV{LM_LICENSE_FILE} = "/usr/local/foundry/FLEXlm/foundry.lic";

but when I submit I get this in the log:

Fail 0001   1               gfx10        10156 gfx10.56   02/25,15:56:05 00:00:21 retry#3 of 3
Executing: /Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0  -x /Volumes/core0000/core_tests/rush/nuke/depth.nk  1,24
Can't exec "/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0": No such file or directory at /Volumes/coreAPPS/rush/rushscripts/.common.pl line 252.
--- /Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0: Command not found. (Probably '/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0' is not in your PATH)

so does that mean I need to edit my .common.pl? or something else?

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

Are you trying to render with nuke 6.2 or 5.0? You could have the NUKECMD variable set wrong.


On Feb 25, 2011, at 4:12 PM, Gary Jaeger wrote:

[posted to rush.general]

So we're finally integrating nuke into the rush install. We've been seat =
of the pants until now. But in my simple tests I can't get the submit =
right.=20

I've changed this part of the submit to reflect our nuke install:

elsif ( $G::ismac )
{
  ### MAC
  $ENV{PATH} =3D "/Applications/Nuke6.2v1/Nuke6.2v1.app:$ENV{PATH}";
  $ENV{LM_LICENSE_FILE} =3D "/usr/local/foundry/FLEXlm/foundry.lic";

but when I submit I get this in the log:

Fail 0001   1               gfx10        10156 gfx10.56   02/25,15:56:05 =
00:00:21 retry#3 of 3
Executing: /Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0  -x =
/Volumes/core0000/core_tests/rush/nuke/depth.nk  1,24
Can't exec "/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0": No such file =
or directory at /Volumes/coreAPPS/rush/rushscripts/.common.pl line 252.
--- /Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0: Command not found. =
(Probably '/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0' is not in your =
PATH)

so does that mean I need to edit my .common.pl? or something else?

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com=09


----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures

dbrowne@(email surpressed)
Office: (415) 777-0666 x105

6.2

where might that variable be set? (bear in mind we're a bunch of artists who pretend to be IT when it's needed. Which generally means we screw things up a few times before getting it straight)

On Feb 25, 2011, at 4:26 PM, Daniel Browne wrote:

> Are you trying to render with nuke 6.2 or 5.0? You could have the NUKECMD v=
> ariable set wrong.

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

btw I have edited my .bash_profile with

alias nuke="/Applications/Nuke6.2v1/Nuke6.2v1.app/Nuke6.2v1"
alias nukex="/Applications/Nuke6.2v1/NukeX6.2v1.app/NukeX6.2v1"

thought maybe that was it, but no love

On Feb 25, 2011, at 4:29 PM, Gary Jaeger wrote:

> where might that variable be set? (bear in mind we're a bunch of artists =
> who pretend to be IT when it's needed. Which generally means we screw =
> things up a few times before getting it straight)

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

OK, so I just tried submitting to a machine that has never had any flavor of nuke on it till now, and got the same fail. So it must be something in the submit or the .common, right Greg?

On Feb 25, 2011, at 5:07 PM, Gary Jaeger wrote:

> [posted to rush.general]
> 
> btw I have edited my .bash_profile with
> 
> alias nuke="/Applications/Nuke6.2v1/Nuke6.2v1.app/Nuke6.2v1"
> alias nukex="/Applications/Nuke6.2v1/NukeX6.2v1.app/NukeX6.2v1"
> 
> thought maybe that was it, but no love
> 
> On Feb 25, 2011, at 4:29 PM, Gary Jaeger wrote:
> 
>> where might that variable be set? (bear in mind we're a bunch of artists =
>> who pretend to be IT when it's needed. Which generally means we screw =
>> things up a few times before getting it straight)
> 
> . . . . . . . . . . . .
> Gary Jaeger // Core Studio
> 86 Graham Street, Suite 120
> San Francisco, CA 94129
> 415 543 8140
> http://corestudio.com	
> 

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

You need to edit your submit_nuke.pl and change the version and environment information Greg has there to correspond with what you are using on the desktop. When a job runs under Rush it technically does not have a shell, so all of the environment information it would get normally from your .bashrc or .profile has to be supplied to it explicitly there. In particular:

}
elsif ( $G::ismac )
{
    ### MAC
    $ENV{PATH}    = "/Applications/Nuke5.1v5/Nuke5.1v5.app/Contents/MacOS:$ENV{PATH}";
    $ENV{NUKECMD} = "Nuke5.1v5";
}


On Feb 25, 2011, at 4:29 PM, Gary Jaeger wrote:

[posted to rush.general]

6.2

where might that variable be set? (bear in mind we're a bunch of artists =
who pretend to be IT when it's needed. Which generally means we screw =
things up a few times before getting it straight)

On Feb 25, 2011, at 4:26 PM, Daniel Browne wrote:

> Are you trying to render with nuke 6.2 or 5.0? You could have the =
NUKECMD v=3D
> ariable set wrong.

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com=09


----------
Dan "Doc" Browne
System Administrator
Evil Eye Pictures

dbrowne@(email surpressed)
Office: (415) 777-0666 x105

Daniel Browne wrote:
> elsif ( $G::ismac )
> {
>     ### MAC
>     $ENV{PATH}    = "/Applications/Nuke5.1v5/Nuke5.1v5.app/Contents/MacOS:$ENV{PATH}";
>     $ENV{NUKECMD} = "Nuke5.1v5";
> }

	This is true in the newer scripts.

	But some older submit-nuke scripts didn't have the $ENV{NUKECMD} setting
	at the top, and were left to their own devices to set the nuke command.

	Nuke used to just be called 'nuke'. But then they changed that somewhere
	along the line so that the executable name had the version number in it.

	I mentioned to one of their software guys (not Bill Spitzak) they should
	at least have the regular command 'nuke' command in there as well,
	so that users can have just 'nuke' in their scripts, and just adjust
	their PATH to point to the correct version. This is what all other products
	do and it works fine.. but they seemed intent on having the version number
	in the executable name, which means that not only the PATH but the executable
	name must change as well. :(

-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)

Gary Jaeger wrote:
>    ### MAC
>    $ENV{PATH} = "/Applications/Nuke6.2v1/Nuke6.2v1.app:$ENV{PATH}";
>    $ENV{LM_LICENSE_FILE} = "/usr/local/foundry/FLEXlm/foundry.lic";

	That looks OK.

> but when I submit I get this in the log:
> Executing: /Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0  [..]

	Sounds like you might have a hot rodded script that has
	the command name modified to run that full path.

	Search the submit-nuke.pl script for 'Nuke5.0' to find
	where that's being set, and modify accordingly.

	I'm guessing someone perhaps specified the full path to Nuke5
	deep in the script (not in the settings at the top) to work
	around some problem they were having with the path.


-- 
Greg Ercolano, erco@(email surpressed)
Seriss Corporation
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)ext.23
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)