Update: Adjusted the /usr/libexec/hobbit issues by putting a sym link
into the directory (directory existed, but client directory didn't).
This did not fix the error.
Bill Hart
Burke Corporation
-----Original Message-----
From: Bill Hart [mailto:user-1131e5ac48a4@xymon.invalid]
Sent: Monday, November 13, 2006 10:39 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] RHEL 3 Error
Ralph,
I did check through the directory tree and it's got full ownership
permissions through the client tree as you would expect.
I just ran the bbcmd to see what the environment looked like, and I see
it has /usr/libexec/hobbit/client for the bbhome and hobbit home.
I bet I don't have those directories, though I know where they came
from.
I tried compiling the 4.2.0 client from the source, but was unable to
get it to compile as it had floating point errors. I found the rpm on
razor's edge and installed that. That did an odd install that put
things in a number of places, so that's probably where that comes from,
so now I need to figure out how to get the paths straightened out in the
bbcmd environment.
Thanks for the pointer, I don't know why I hadn't checked all that more
closely.
Does anyone know why I can't get the 4.2.0 source to compile on RHEL 3 ?
Bill Hart
Burke Corporation
-----Original Message-----
From: Ralph Mitchell [mailto:user-00a5e44c48c0@xymon.invalid]
Sent: Monday, November 13, 2006 9:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] RHEL 3 Error
Seems to me that's the kind of message to expect if someone either
removes a directory the process is running in, or possibly chmod's (or
maybe chown's) some part of the tree so that it can't be accessed by
the running process.
I'm not a RHEL expert, but that's where I'd start on any Unix-like
system. Even if you don't have any 'files' tests defined, Hobbit
still has to be able to reach its own config files, log files, etc.
Ralph Mitchell
On 11/13/06, Bill Hart <user-1131e5ac48a4@xymon.invalid> wrote:
I posted about this last week, as well as searching the archives.
Is anyone else seeing this :
shell-init: could not get current directory: getcwd: cannot access
parent directories: No such file or directory
I'm seeing it on one of our RHEL 3 servers, the other two don't
display
this error, and I have no idea what directories they are looking for.
I
don't have any 'files' tests defined. The archives had one reference
to
this, but it was a Debian system and the solution was unclear to me.
Bill Hart
Burke Corporation