Problem with permission

diogo.cwb · Post by **diogo.cwb** » Wed Jul 08, 2009 7:29 am

Hi all,

When i run my job on production enviroment. I get the below error. But i want to know how i know what directory the job is trying to use ?

Unable to determine current working directory! This is very likely due to a problem with file permissions on the directory or directories above this point. The error was Permission denied
Traceback: Could not obtain stack trace; check that 'dbx' and 'sed' are installed and on your PATH

Regards

ArndW · Post by **ArndW** » Wed Jul 08, 2009 8:30 am

Does resetting the job produce an entry in the log file with "From previous run..."

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Wed Jul 08, 2009 8:47 am

Add an external source stage with 'env' as its source program.

diogo.cwb · Post by **diogo.cwb** » Wed Jul 08, 2009 12:21 pm

Sorry but i didn't understand this answers...

chulett · Post by **chulett** » Wed Jul 08, 2009 12:50 pm

OK. Try doing an Exact search for your error message(s) as this has been discussed here before. For example, a search for "check that 'dbx' and 'sed' are installed and on your PATH" has 18 matches to other posts, see if any of them help.

diogo.cwb · Post by **diogo.cwb** » Wed Jul 08, 2009 2:04 pm

But my problem such as i understand it wasn't in traceback...but is in "Unable to determine current working directory! This very likely due to a problem with file permissions on the directory or directories above this point. The error was Permission denied "

and i try to search something about that and i doesn't find.

diogo.cwb · Post by **diogo.cwb** » Wed Jul 08, 2009 2:05 pm

Internal Error: (0):util/pathutils.C: 349:

chulett · Post by **chulett** » Wed Jul 08, 2009 2:58 pm

You are probably searching for "too much", too many words at a time - try another search for 'Unable to determine current working directory'.

diogo.cwb · Post by **diogo.cwb** » Thu Jul 09, 2009 5:03 am

ok thanks for the help...

ray.wurlod · Post by **ray.wurlod** » Thu Jul 09, 2009 4:25 pm

This is a really strange error. When connected (to AIX) via telnet, I have seen this message using the du . command.

Code: Select all

# Let's start somewhere
$ cd /home/dsadm/projects/eswm/dev/data/reject

$ du .
du: can't find current directory
$ du /home/dsadm/projects/eswm/dev/data/reject
du: can't find current directory

# And yet, we own the directory and have full permission to it.
$ ls -ld .
drwxrwxr-x   2 dsadm    dstage          256 Nov 25 2008  .
$ id
uid=236(dsadm) gid=216(dstage) groups=1(staff)

# But, when the attach point is somewhere else, all is OK.
$ cd /tmp
$ du /home/dsadm/projects/eswm/dev/data/reject
0       /home/dsadm/projects/eswm/dev/data/reject

$

UNIX seems to lose track of the attach point even though you're the owner and you're attached there. But it's happy if you're attached someplace else.
Clearly this is UNIX behaviour and not DataStage behaviour, but DataStage apparently can be affected by it.

jhmckeever · Post by **jhmckeever** » Tue Nov 17, 2009 6:54 pm

Sorry to open an old wound, but has anyone experiencing this problem found a reliable way to reproduce (or better, fix) this issue? We're 8.1.0 on AIX6.1.

We have the symptom described by the OP visible in our Director log, but cannot reproduce the command-line du behaviour demonstrated by Ray.

Ray - Is there any particular directory we should attempt demonstrating this du problem from?

Thanks,
John.

ray.wurlod · Post by **ray.wurlod** » Tue Nov 17, 2009 10:45 pm

Basically it's the directory where the thing throwing the error is. Or is meant to be.