problem with openAPI installing TS6.5 on solaris9

This is my first time installed teamsite on Solaris from scratch, so I assume its something trivial... but maybe someone can help me along.

I am installing teamsite on a Solaris9 machine to do some devel work. Installed TeamSite 6.5. Everything seemed to work. Installed the servicepack3, and my teamsite server stopped working. I can no longer http to the machine and get a web page, so for whatever reason my web server isn't running.

Interwoven TeamSite starting ...
ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwserver.log

So I check iwserver.log

iw.server: ---------- STARTING: Sun Aug 26 16:18:13 EDT 2007
iwetcboot: Running iwstart /iw-store in /Interwoven/TeamSite
iwstart: WFS device driver path is /dev/iwovwfs
WARNING: iwserver.sol is already running. Not restarted.
iwmount: /iwmnt/default has previously been mounted. Umounting it...
iwmount: /.iwmnt/default has previously been mounted. Umounting it...
iwmount: Mounting /iwmnt/default...
iwmount: Mounting /.iwmnt/default...
iwmount: Mounted /iwmnt/default and /.iwmnt/default.
Interwoven OpenAPI starting ...
ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwui/openapi.log

So then I check openapi.log

iwopenapiboot: ---------- STARTING: Sun Aug 26 16:18:14 EDT 2007
Usage: OpenAPIServer [-h] [-p port] openapi_cfg_path

Starts an RMI registry and Interwoven OpenAPI server

-h This help message
-p The TCP port for the server's RMI registry (default 1099)

What does this all mean? Somehow I need to reinstall openAPI, or what could be causing this?

Thanks!

Find more posts tagged with

Comments

Adam Stoller

Have you tried rebooting?
If not - try that first.
If it's still not working ...
It looks like something isn't picking up an argument somewhere in the script - you might need to (as root or via sudo) run /etc/init.d/iw.server stop, and then /etc/init.d/iw.server start - but in verbose mode - something like:

/bin/ksh -x /etc/init.d/iw.server start

This should display all the commands in the script as they are being executed. If this doesn't pinpoint the source of the problem it should help narrow it down - presumably to another script, which you can then try to execute the same way until the problem does become apparent.
If you still cannot figure it out (or if the above is too much for you) - I suggest opening a case with Support.

kg_brian

Yes a full restart did not work, it hung on openAPI. So I am trying to start just the openAPI part to see where it is broke.

Well I made it 3 steps, but I am not seeing the problem in step3. Any ideas on where to go from here?


+ iwopenapiboot start
+ 1>> /Interwoven/TeamSite/local/logs/iwserver.log 2>& 1
+ RESULT=21
+ [ 21 -ne 0 ]
+ echo ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwserver.lo


# /bin/ksh -x /etc/init.d/iw.server start
+ PATH=/usr/sbin:/sbin:/usr/bin
+ + basename /etc/init.d/iw.server
MYNAME=iw.server
+ SCCSID=@(#)iw.server.sh       105.1 97/05/23
+ VERSION=6.5.0 Build 41235 SYM Interwoven 20040928
+ USAGE=Usage: iw.server [-h|-v] { start | stop | stop_all }
        Start up or shutdown iwserver with logging.
        -h      this message
        -v      version string
+ + iwgethome
IW_HOME=/Interwoven/TeamSite
+ RESULT=0
+ [ 0 -ne 0 ]
+ export IW_HOME
+ PATH=/usr/bin:/Interwoven/TeamSite/private/bin:/Interwoven/TeamSite/bin:/usr/sbin:/sbin:/usr/bin
+ export PATH
+ IWARGSET=0
+ ARG=
+ [ 1 -ne 0 ]
+ [ %start = %-v ]
+ [ %start = %-h ]
+ [ 0 -eq 0 ]
+ IWARGSET=1
+ ARG=start
+ shift
+ [ 0 -ne 0 ]
+ iwgetlog -h
+ 1> /dev/null 2>& 1
+ RESULT=0
+ [ 0 -ne 0 ]
+ + iwgetlog
IWLOGFILE=/Interwoven/TeamSite/local/logs/iwserver.log
+ + dirname /Interwoven/TeamSite/local/logs/iwserver.log
IWLOGDIR=/Interwoven/TeamSite/local/logs
+ [ ! -d /Interwoven/TeamSite/local/logs ]
+ iwetcboot -h
+ 1> /dev/null 2>& 1
+ RESULT=0
+ [ 0 -ne 0 ]
+ echo Interwoven TeamSite starting ...
Interwoven TeamSite starting ...
+ date
+ echo iw.server: ---------- STARTING: Sun Aug 26 23:06:22 EDT 2007
+ 1>> /Interwoven/TeamSite/local/logs/iwserver.log 2>& 1
+ iwetcboot start
+ 1>> /Interwoven/TeamSite/local/logs/iwserver.log 2>& 1
+ RESULT=0
+ [ 0 -ne 0 ]
+ iwevent start
+ 1>> /Interwoven/TeamSite/local/logs/iwserver.log 2>& 1
+ RESULT=0
+ [ 0 -ne 0 ]
+ iwopenapiboot start
+ 1>> /Interwoven/TeamSite/local/logs/iwserver.log 2>& 1
+ RESULT=21
+ [ 21 -ne 0 ]
+ echo ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwserver.log
ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwserver.log
+ exit 21


# /bin/ksh -x ./iwopenapiboot start
+ PATH=/usr/sbin:/usr/bin:/usr/sbin:/sbin:/usr/bin
+ + basename ./iwopenapiboot
MYNAME=iwopenapiboot
+ VERSION=6.5.0 Build 41235 SYM Interwoven 20040928
+ USAGE=Usage: iwopenapiboot [-h|-v] { start | stop | restart }
        Start up or shut down Interwoven OpenAPI with logging.
        -h      this message
        -v      version string
+ + iwgethome
IW_HOME=/Interwoven/TeamSite
+ RESULT=0
+ [ 0 -ne 0 ]
+ PATH=/usr/bin:/Interwoven/TeamSite/bin:/usr/sbin:/usr/bin:/usr/sbin:/sbin:/usr/bin
+ export PATH
+ JAVA_HOME=/Interwoven/TeamSite/tools/java
+ OPENAPI_DIR=/Interwoven/TeamSite/iwopenapi
+ CLASSPATH=
+ export IW_HOME JAVA_HOME CLASSPATH
+ IWARGSET=0
+ ARG=
+ [ 1 -ne 0 ]
+ [ %start = %-v ]
+ [ %start = %-h ]
+ [ 0 -eq 0 ]
+ IWARGSET=1
+ ARG=start
+ shift
+ [ 0 -ne 0 ]
+ iwgetlog -h
+ 1> /dev/null 2>& 1
+ RESULT=0
+ export RESULT
+ [ 0 -ne 0 ]
+ + iwgetlocation iwlogs
IWLOGFILE=/Interwoven/TeamSite/local/logs/iwui/openapi.log
+ + dirname /Interwoven/TeamSite/local/logs/iwui/openapi.log
IWLOGDIR=/Interwoven/TeamSite/local/logs/iwui
+ [ ! -d /Interwoven/TeamSite/local/logs/iwui ]
+ [ ! -x /Interwoven/TeamSite/local/logs/iwui/openapi.log ]
+ touch /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ date
+ echo iwopenapiboot: ---------- STARTING: Sun Aug 26 23:17:25 EDT 2007
+ 1>> /Interwoven/TeamSite/local/logs/iwui/openapi.log 2>& 1
+ iwui_user=iwui
+ + id iwui
+ sed -n -e s/^uid=\([0-9]*\).*/\1/p
iwui_uid=102
+ 1>> /Interwoven/TeamSite/local/logs/iwui/openapi.log 2>& 1
+ [ x102 = x ]
+ chown iwui:nobody /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ chmod 664 /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ status 1
+ RESULT=21
+ export RESULT
+ [ 21 -eq 0 ]
+ echo Interwoven OpenAPI starting ...
Interwoven OpenAPI starting ...
+ /bin/su iwui -c nohup /Interwoven/TeamSite/iwopenapi/iwopenapi 1>>/Interwoven/TeamSite/local/logs/iwui/openapi.log 2>&1 &
+ RESULT=0
+ export RESULT
+ [ 0 -ne 0 ]
+ status 30
+ RESULT=21
+ export RESULT
+ [ 21 -ne 0 ]
+ echo ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwui/openapi.log
ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ exit 21
#

Adam Stoller

This appears to be where the source of the problem occurs:

...
+ chown iwui:nobody /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ chmod 664 /Interwoven/TeamSite/local/logs/iwui/openapi.log
+ status 1
+ RESULT=21
+ export RESULT
+ [ 21 -eq 0 ]
+ echo Interwoven OpenAPI starting ...
Interwoven OpenAPI starting ...
+ /bin/su iwui -c nohup /Interwoven/TeamSite/iwopenapi/iwopenapi 1>>/Interwoven/TeamSite/local/logs/iwui/openapi.log 2>&1 &
+ RESULT=0
+ export RESULT
+ [ 0 -ne 0 ]
+ status 30
+ RESULT=21
+ export RESULT
+ [ 21 -ne 0 ]
+ echo ERROR: Failed to start. Check /Interwoven/TeamSite/local/logs/iwui/openapi.log
...

Things to check:

You could also try running each of the commands shown in that output directly via root / sudo in your shell - as they might display a bit more information than what is being captured in the script output.

kg_brian

existence of "nobody" in /etc/group

Things to check:
existence of user "iwui" in /etc/passwd (I believe that was already verified in the script)

Both these appear to be there.

existence of "chown" and "chmod" on PATH (they should be there)


# which chown
/usr/bin/chown
# which chmod
/usr/bin/chmod

This appears to be there.. but if I run the command from eariler I do get this:



# /bin/ksh -x chown iwui:nobody /Interwoven/TeamSite/local/logs/iwui/openapi.log
/bin/ksh: chown: cannot execute

I think that is just a problem with trying to use ksh -x, not with chown.. because when I go look at the log, it has a chmod of 644, and a chown of iwui:nobody, so it seems to be getting set fine by the script.

existence of iwhome/iwopenapi/iwopenapi (doesn't seem to exist in my 6.7.1 Windows environment - not sure about a 6.5 Solaris environment)

Yah it is there, but I am 90% sure this is where it is hanging. If I just try to run openAPI I get this



# /bin/ksh -x iwopenapi
+ PATH=/usr/sbin:/sbin:/usr/bin
+ + iwgethome
IW_HOME=/Interwoven/TeamSite
+ + basename iwopenapi
MYNAME=iwopenapi
+ OPENAPI_DIR=/Interwoven/TeamSite/iwopenapi
+ JAVA_HOME=/Interwoven/TeamSite/tools/java
+ LAX_FILE=/Interwoven/TeamSite/iwopenapi/IWServiceServer.lax
+ LD_LIBRARY_PATH=/Interwoven/TeamSite/lib:
+ SHLIB_PATH=/Interwoven/TeamSite/lib:
+ export LD_LIBRARY_PATH SHLIB_PATH
+ [  = -v ]
+ + laxprop_to_javaopt -D !/^lax\.*/
JAVA_PROPERTIES=-Djava.library.path=/iwopenapi
-Djava.rmi.server.codebase=file:////iwopenapi/openapi_client.jar
-Djava.security.policy=/iwopenapi/openapi.policy
+ + laxprop_to_javaopt -Xss /^lax.nl.java.option.java.stack.size.max=/
JAVA_NATIVE_STACK_OPT=-Xss4000000
+ CLASSPATH=/Interwoven/TeamSite/iwopenapi/openapi_server.jar:/Interwoven/TeamSite/iwopenapi/openapi_client.jar:/Interwoven/TeamSite/iwopenapi/collections.jar:/Interwoven/TeamSite/iwopenapi/xercesImpl.jar:/Interwoven/TeamSite/iwopenapi/xalan.jar
+ MAIN_CLASS=com.interwoven.api.OpenAPIServer
+ + laxprop_to_javaopt  /^lax.command.line.args=/
OPENAPI_CMD_ARGS=-p  /iwopenapi/openapi.cfg
+ DEBUG_PROG=/Interwoven/TeamSite/private/bin/iwnamedexec iwopenapi
+ export DEBUG_PROG
+ cd /
+ [ -n  ]
+ exec /Interwoven/TeamSite/tools/java/bin/java -server -Xss4000000 -Djava.library.path=/iwopenapi -Djava.rmi.server.codebase=file:////iwopenapi/openapi_client.jar -Djava.security.policy=/iwopenapi/openapi.policy -classpath /Interwoven/TeamSite/iwopenapi/openapi_server.jar:/Interwoven/TeamSite/iwopenapi/openapi_client.jar:/Interwoven/TeamSite/iwopenapi/collections.jar:/Interwoven/TeamSite/iwopenapi/xercesImpl.jar:/Interwoven/TeamSite/iwopenapi/xalan.jar com.interwoven.api.OpenAPIServer -p  /iwopenapi/openapi.cfg
Usage: OpenAPIServer [-h] [-p port] openapi_cfg_path

        Starts an RMI registry and Interwoven OpenAPI server

        -h      This help message
        -p      The TCP port for the server's RMI registry (default 1099)
#

I think it wants me to call openapiserver with openapi openApiConfigPath... but the command our script is calling is


+ /bin/su iwui -c nohup /Interwoven/TeamSite/iwopenapi/iwopenapi 1>>/Interwoven/TeamSite/local/logs/iwui/openapi.log 2>&1 &

I see openAPI being called and the output redirected to a log file, but I do not see the command being called correctly. There are a couple too many numbers and &'s for me to understand this line, humm.

ownership / group-ownership / access bits on iwhome/local/logs/iwui/openapi.log

things like that ...You could also try running each of the commands shown in that output directly via root / sudo in your shell - as they might display a bit more information than what is being captured in the script output.



# ls -l
total 16
-rw-rw-r--   1 iwui     nobody      3534 Aug 27 08:33 openapi.log
-rw-r--r--   1 iwui     other       3118 Aug 26 23:06 servletd.log

Seems fine...

nipper

One thing I have seen with 6.1,


+ /bin/su iwui -c nohup /Interwoven/TeamSite/iwopenapi/iwopenapi 1>>/Interwoven/TeamSite/local/logs/iwui/openapi.log 2>&1 &
+ RESULT=0

What shell has been assigned to iwui ?

I have seen issue when an su to iwui happens and the commands were set for /bin/sh and it was assigned bash, I got similar errors

kg_brian

One thing I have seen with 6.1,
+ /bin/su iwui -c nohup /Interwoven/TeamSite/iwopenapi/iwopenapi 1>>/Interwoven/TeamSite/local/logs/iwui/openapi.log 2>&1 &
+ RESULT=0
What shell has been assigned to iwui ?

I have seen issue when an su to iwui happens and the commands were set for /bin/sh and it was assigned bash, I got similar errors

In etc/passwd iwui had /bin/sh assigned. I tried changing it with passwd -e command to /bin/zh and /bin/ksh, and I got the same result

Adam Stoller

In etc/passwd iwui had /bin/sh assigned. I tried changing it with passwd -e command to /bin/zh and /bin/ksh, and I got the same result

I do hope you've opened a case with Support, and post their response....

kg_brian

As an update -

So it looks like the problem was that during install, the installer did not make a openapi.cfg file.

We made an openapi.cfg file from the example, and can call it with


nohup /Interwoven/TeamSite/tools/java/bin/java -server -Xss4000000 -Djava.library.path=/Interwoven/TeamSite/iwopenapi -Djava.rmi.server.codebase=file:////Interwoven/TeamSite/iwopenapi/openapi_client.jar -Djava.security.policy=/Interwoven/TeamSite/iwopenapi/openapi.policy -classpath /Interwoven/TeamSite/iwopenapi/openapi_server.jar:/Interwoven/TeamSite/iwopenapi/openapi_client.jar:/Interwoven/TeamSite/iwopenapi/collections.jar:/Interwoven/TeamSite/iwopenapi/xercesImpl.jar:/Interwoven/TeamSite/iwopenapi/xalan.jar com.interwoven.api.OpenAPIServer -p 1099 /Interwoven/TeamSite/iwopenapi/openapi.cfg &

Does anyone know why this would be? Why wouldn't the openapi.cfg be automatically created?