Re: [staf-users] Problems restarting STAFProc

[Charles R. <ra...@us...>]

sta...@li... said:

> I shutdown the STAFProc on a Solaris box in the normal manner, and it
shut
> down "normally" (without any complaints).
> Now, when I try to restart it, I get the following error:
> STAFProc version 2.3.0 initialized
> In main():
> Caught STAFException
> Name      : STAFBaseOSErrorException
> Location  :
> Text      : STAFFSExists: 20
> Error code: 10
> I've spent a bit of time with the source code, but I can't tell what is
> happening here during the startup.  Can anyone give me a clue about what
I
> need to do to get STAFProc to run.
> If I "su" to Root, it starts up normally.  However, I definitely do not
> want to run as root on this box.  When I go back to being "qa", it
> continues to have the problem shown above.   At one point, we also got a
> message about being unable to start on a socket (but I don't have the
> details on that, and it's not happening now).

The "Error code" in the exception is the STAF return code.  A "10" means a
Base Operating System error was encountered.  The "Text" in the exception
is stating the STAF API that was called and the Base OS error that was
returned.  On my Solaris box (running 5.6/2.6) a 20 means ENOTDIR.  ENOTDIR
means that some part of a path string is not actually a directory.  The
only realistic place this could show up is when trying to start STAFProc is
when we check for the registration file.  The path it checks ultimately
comes from the "exePath" in STAFUtilGetConfigInfo() (in
stafif/unix/STAFUtil.cpp).  On first inspection, the only way this path
could get messed up is if the directory STAFProc is in is not in the PATH.
However, that should cause STAFUtilGetConfigInfo to generate an error
different from the one you are seeing.

I don't have an answer yet, but let's check/try a couple of things.  First,
make sure that your PATH contains /usr/local/staf/bin (or wherever you
installed STAF).  As a matter of fact, go ahead and reply back with your
PATH and LD_LIBRARY_PATH settings.  Second, su to root and go into /tmp and
delete any files beginning with STAF.  There are probably two of them.
This shouldn't have any effect, but let's try it anyway.  Also, are there,
by chance, any symlinks down the chain to STAFProc (with respect to your
PATH settings)?

--
Charles Rankin
I do not speak for IBM