From: Gary Jaeger <gary@(email surpressed)>
Subject: nuke path
   Date: Tue, 24 Jun 2008 15:15:53 -0400

Gary Jaeger wrote:

can anybody help me with the nuke path for v5 on OSX? It looks like i need to replace this:

{
    ### MAC
#   $ENV{PATH} = "/Applications/D2Software/nuke4/bin:$ENV{PATH}";
}

in the submit-nuke.pl script

	I don't know the path for nuke5 offhand, but I would uncomment
	the above line by removing the leading '#' from the $ENV{PATH} line,
	and I assume the D2Software may have changed to "Framestore"
	and "nuke4" to "nuke5".

	If you're unsure, show us an "ls -la" listing of your /Applications
	directory, and if you're able to tell where nuke is installed,
	send me (via private email) the output of:

		ls -laR /Applications/XXX

	..replacing XXX with the name of the dir nuke5 is installed in,
	and I can follow up here with the exact change to make.


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

     ********************  N O T I C E  *************************
     ***   I'll be on vacation June 18th through June 28th.   ***
     ***   During this time I will be watching email, but it  ***
     ***   may take up to a day for me to reply.              ***
     ************************************************************

Greg Ercolano wrote:

    [..] I assume the D2Software may have changed to "Framestore"

	Oops, I mean "The Foundary" ;)

    If you're unsure, show us an "ls -la" listing of your /Applications
    directory, and if you're able to tell where nuke is installed,
    send me (via private email) the output of:

        ls -laR /Applications/XXX

    ..replacing XXX with the name of the dir nuke5 is installed in,

    A quick look at the docs, it looks like the command to send me is:

	ls -laR /Applications/Nuke5.0*

    My guess is the $ENV{PATH} line should look something like:

	$ENV{PATH} = "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS:$ENV{PATH}";

    ..and you might need to change this line as well in submit-nuke.pl:

BEFORE:    my $command = "nuke $opt{NukeFlags} ".
 AFTER:    my $command = ($G::ismac ? "nuke5.0" : "nuke") . " $opt{NukeFlags} ".

    ..because it looks like they may have renamed the actual executable
    to follow the version number (which I don't think they should have done).

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

     ********************  N O T I C E  *************************
     ***   I'll be on vacation June 18th through June 28th.   ***
     ***   During this time I will be watching email, but it  ***
     ***   may take up to a day for me to reply.              ***
     ************************************************************

Sent via private email:
% ls -laR /Applications/Nuke5.0v2/*
[..]
/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS:
total 112120
drwxr-xr-x   26 1725  wheel       884 Jun  2 16:33 .
drwxr-xr-x    8 1725  wheel       272 May 28 11:15 ..
drwxr-xr-x    6 1725  wheel       204 May 28 11:15 Documentation
drwxr-xr-x   11 1725  wheel       374 May 28 11:14 FrameCycler
drwxr-xr-x    3 1725  wheel       102 May 28 11:14 Frameworks
-rwxr-xr-x    1 1725  wheel  31297444 May 28 11:15 Nuke5.0

[..]

    Hi Gary,

    Thanks for the 'ls -la' listing.

    That looks consistent with my last post, so definitely make both
    changes, specifically:

   $ENV{PATH} = "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS:$ENV{PATH}";

    ..and because the nuke executable is called 'Nuke5.0',
    you'll need to make this change as well:

 BEFORE:    my $command = "nuke $opt{NukeFlags} ".
  AFTER:    my $command = ($G::ismac ? "Nuke5.0" : "nuke") . " $opt{NukeFlags} ".

    If you have any trouble, please follow up.

thanks greg. there seems to be this bit also (from the nuke list):

On the issue of command line rendering and the Nuke alias.

I have found that if you are on Leopard and using the default terminal, which is a BASH rather than the old TCSH which Tiger used, you will need to edit your .bash_profile and add the line :

alias nuke="/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0"

to get the alias working again. Damn extra '=' had me loosing my mind for a bit !

On Jun 24, 2008, at 6:20 PM, greg ercolano wrote:

[posted to rush.general]

Sent via private email:
% ls -laR /Applications/Nuke5.0v2/*
[..]
/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS:
total 112120
drwxr-xr-x   26 1725  wheel       884 Jun  2 16:33 .
drwxr-xr-x    8 1725  wheel       272 May 28 11:15 ..
drwxr-xr-x    6 1725  wheel       204 May 28 11:15 Documentation
drwxr-xr-x   11 1725  wheel       374 May 28 11:14 FrameCycler
drwxr-xr-x    3 1725  wheel       102 May 28 11:14 Frameworks
-rwxr-xr-x    1 1725  wheel  31297444 May 28 11:15 Nuke5.0
[..]

   Hi Gary,

   Thanks for the 'ls -la' listing.

   That looks consistent with my last post, so definitely make both
   changes, specifically:

$ENV{PATH} = "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/ MacOS:$ENV{PATH}";

   ..and because the nuke executable is called 'Nuke5.0',
   you'll need to make this change as well:

BEFORE:    my $command = "nuke $opt{NukeFlags} ".

AFTER: my $command = ($G::ismac ? "Nuke5.0" : "nuke") . " $opt{NukeFlags} ".

   If you have any trouble, please follow up.

Gary Jaeger wrote:

thanks greg. there seems to be this bit also (from the nuke list):

On the issue of command line rendering and the Nuke alias.

I have found that if you are on Leopard and using the default terminal, which is a BASH rather than the old TCSH which Tiger used, you will need to edit your .bash_profile and add the line :

alias nuke="/Applications/Nuke5.0v2/Nuke5.0v2.app/Nuke5.0"

to get the alias working again. Damn extra '=' had me loosing my mind for a bit !

not sure if that impacts rush but I guess it might? I'll try again in the morning

    Yes, I noticed mention of that 'alias' in the Nuke5 docs,
    but this will not affect the submit-nuke.pl script, because
    it's written in perl, not bash or tcsh.

    The bash/csh concept of 'aliases' are usable for login shell scripts,
    but have no effect on scripts or programs written in other languages
    like Python or Perl or even C/C++.

    Besides, this change that I mentioned:

BEFORE:    my $command = "nuke $opt{NukeFlags} ".
 AFTER:    my $command = ($G::ismac ? "Nuke5.0" : "nuke") . " $opt{NukeFlags} ".

    ..should handle all that.

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

     ********************  N O T I C E  *************************
     ***   I'll be on vacation June 18th through June 28th.   ***
     ***   During this time I will be watching email, but it  ***
     ***   may take up to a day for me to reply.              ***
     ************************************************************

hmm. So it still fails. I get:

###
### gfx10.5: 0004
###
--------------- Rush 102.42a9 --------------
--      Host: gfx10
--       Pid: 56504
--     Title: nuke_test1
--     Jobid: gfx10.5
--     Frame: 0004
--     Tries: 0
--     Owner: gfx10 (501/20)
-- RunningAs: ? (501/20)
--  Priority: 1
--      Nice: 10
--    Tmpdir: /var/tmp/.RUSH_TMP.9

--   Started: Wed Jun 25 08:59:51 2008
--------------------------------------------

   NUKESCRIPT: /Volumes/JOBSB/0813_Conor_PCR08/nuke/0813_spin2.nk
   SCRIPTARGS:
    NUKEFLAGS: -V -i
  BATCHFRAMES: 1 (4-4)
      RETRIES: 3 (Fail after 3 retries)

--- nuke5.0: Command not found. (Probably 'nuke5.0' is not in your PATH)

--- RETRY #2 of 3
[gfx10.5] 0004: retry#2 of 3

--- nuke5.0: Command not found. (Probably 'nuke5.0' is not in your PATH)

--- RETRY #3 of 3
[gfx10.5] 0004: retry#3 of 3

--- nuke5.0: Command not found. (Probably 'nuke5.0' is not in your PATH)
--- NUKE FAILED

On Jun 24, 2008, at 9:48 PM, Greg Ercolano wrote:

   ..should handle all that.

Gary Jaeger wrote:
> hmm. So it still fails. I get:
> 
> [..]
>     NUKEFLAGS: -V -i
>   BATCHFRAMES: 1 (4-4)
>       RETRIES: 3 (Fail after 3 retries)
>          PATH: /usr/local/rush/bin:/usr/local/rush/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/rush/bin 

    Make sure there's no leading '#' on that $ENV{PATH} line.

    The PATH: above shows your change to the $ENV{PATH} line have not taken
    effect, which means the line is still commented out.

    Double check your /Volumes/coreAPPS/rush/rushscripts/submit-nuke.pl script,
    and make sure the MAC section reads:

{
    ### MAC
    $ENV{PATH} = "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS:$ENV{PATH}";
}

    Note there's no leading '#' in front of the $ENV{PATH}

> Executing: nuke5.0 -V -i -x /Volumes/JOBSB/0813_Conor_PCR08/nuke/0813_spin2.nk  4,4
> Can't exec "nuke5.0": No such file or directory at /Volumes/coreAPPS/rush/rushscripts/.common.pl line 252.
> --- nuke5.0: Command not found. (Probably 'nuke5.0' is not in your PATH)


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

     ********************  N O T I C E  *************************
     ***   I'll be on vacation June 18th through June 28th.   ***
     ***   During this time I will be watching email, but it  ***
     ***   may take up to a day for me to reply.              ***
     ************************************************************

//////////////////

###
### gfx10.14: 0001
###
--------------- Rush 102.42a9 --------------
--      Host: gfx10
--       Pid: 57060
--     Title: nuke_test1
--     Jobid: gfx10.14
--     Frame: 0001
--     Tries: 0
--     Owner: gfx10 (501/20)
-- RunningAs: ? (501/20)
--  Priority: 1
--      Nice: 10
--    Tmpdir: /var/tmp/.RUSH_TMP.27

--   Started: Wed Jun 25 09:54:36 2008
--------------------------------------------

   NUKESCRIPT: /Volumes/core0000/core_projects/testing/nuke/test1.nk
   SCRIPTARGS:
    NUKEFLAGS: -V -i
  BATCHFRAMES: 11 (1-10)
      RETRIES: 3 (Fail after 3 retries)

Nuke 5.0v2, built May 28 2008, revision 6380.
Copyright (C) 2008 The Foundry Visionmongers Ltd.  All Rights Reserved.
License failure: License server machine is down or not responding.

 make sure you're referring to the right host (see LM_LICENSE_FILE).
Feature:       nuke_i
Hostname:      lserver
License path:  /Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS -

   /FLEXlm/foundry.lic

For further information, refer to the FLEXnet Licensing End User Guide,
available at "www.macrovision.com".
--- NUKE LICENSE ERROR: EXITCODE=100

//////////////////

nuke -V -x -i /Volumes/core0000/core_projects/testing/nuke/test1.nk

On Jun 25, 2008, at 9:31 AM, Greg Ercolano wrote:

{
   ### MAC

$ENV{PATH} = "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/ MacOS:$ENV{PATH}";

}

I believe the problem here was one of permissions on the license file
or directory, where the user the Rush render was running as didn't have
read permission to the license file, so nuke couldn't load it.

The way to debug this sort of thing is to login to the machine in question
as the user the rush render is running as, which you can see from the
"Host:" and "RunningAs:" lines in the rush log.

To determine the problem, you would login as that user on that machine,
and then try to 'more' the license file to see if you have permission
to read it, eg:

	more "/Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS/*.lic"
	more "/usr/local/foundry/FLEXlm/foundry.lic"
	more "/Library/Application Support/TheFoundry/FLEXlm/*.lic"

Note that quotes are needed if the pathnames contain spaces.

The above are unix commands, though similar commands should work in DOS
as well, only you'd need to avoid the '*' wildcards, as the DOS shell
doesn't handle wildcard expansions the same way as unix shells. (In DOS,
wild cards are handled by the command, not the shell, and only certain
DOS commands, like "DIR", can handle wildcards)


> [..] now I get:
> 
> [..]
> Nuke 5.0v2, built May 28 2008, revision 6380.
> Copyright (C) 2008 The Foundry Visionmongers Ltd.  All Rights Reserved.
> License failure: License server machine is down or not responding.
>   See the system adminstrator about starting the license server system, or
>   make sure you're referring to the right host (see LM_LICENSE_FILE).
> Feature:       nuke_i
> Hostname:      lserver
> License path:  /Applications/Nuke5.0v2/Nuke5.0v2.app/Contents/MacOS/*.lic: [..]
>     /Library/Application Support/TheFoundry/FLEXlm/*.lic:/usr/local/foundry/FLEXlm/foundry.lic
> FLEXnet Licensing error:-96,7.  System Error: 2 "No such file or directory"
> For further information, refer to the FLEXnet Licensing End User Guide,
> available at "www.macrovision.com".
> --- NUKE LICENSE ERROR: EXITCODE=100