cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

We are happy to announce the new Windchill Customization board! Learn more.

Winchill method server and server manager won't start after reboot

dnordin
15-Moonstone

Winchill method server and server manager won't start after reboot

All,

After successfully installing Pro/Intralink 9.1 M060 on a RHEL 4 server, everything was working fine, and I was able to startup and shutdown oracle and all the WC & related services. I created a couple of scripts; one that would start/stop all services and another that would run the first script on system bootup (see below). I have made NO changes to any of the WC setup at this point, so all the conf and properties files are OOTB. The problem occurred after I rebooted the server. I was able to watch all the services start, however, the method server and server manager showed up in the process list, but quickly disappeared. No method server or server manager log files are created. At first I thought that the issue may be related to the xterm windows not being able to open because during bootup there isn't an interactive shell running, but I have removed the WC bootup scripts from the system, rebooted, and the services still won't start. Again with no logs created. Oracle, Tomcat, Apache and WindchillDS all start and stop without issue w/ no obvious issues in any of the log files.

I have a call open to PTC, but don't have a resolution as of yet.

Any suggestions?

Regards,

Daniel Nordin
BAE Systems
Electronic Solutions
ET&S MCAE Support Group


#!/bin/sh
mode=$1
case $mode in
'start')
/bin/su - wcadmin -c "/disk0/ptc/Windchill_9.1/bae_scripts/wc.init $mode"
;;
'stop')
/bin/su - wcadmin -c "/disk0/ptc/Windchill_9.1/bae_scripts/wc.init $mode"
;;
*)
echo "Usage $0 { start | stop }"
esac
exit 0
2 REPLIES 2

hi,

if you do not even get output in the methodserver log file (which if you
got it would tell the problem) then check the value of
wt.manager.cmd.MethodServer and run the command from a windchill shell -
this will reveal the problem.

regarding the xterm in the start command - most of the folks obviously
come from windows machines and can't live without windows popping up 😉
for a unix box you will *definitely* want to remove the xterm and just
run java ....

hth, martin

On 11/19/2010 03:30 PM, Nordin, Daniel A (US SSA) wrote:
>
> All,
>

>
> After successfully installing Pro/Intralink 9.1 M060 on a RHEL 4
> server, everything was working fine, and I was able to startup and
> shutdown oracle and all the WC & related services.  I created a couple
> of scripts; one that would start/stop all services and another that
> would run the first script on system bootup (see below).  I have made
> NO changes to any of the WC setup at this point, so all the conf and
> properties files are OOTB.  The problem occurred after I rebooted the
> server.  I was able to watch all the services start, however, the
> method server and server manager showed up in the process list, but
> quickly disappeared.  No method server or server manager log files are
> created.  At first I thought that the issue may be related to the
> xterm windows not being able to open because during bootup there isn’t
> an interactive shell running, but I have removed the WC bootup scripts
> from the system, rebooted, and the services still won’t start.  Again
> with no logs created.  Oracle, Tomcat, Apache and WindchillDS all
> start and stop without issue w/ no obvious issues in any of the log files.
>

>
> I have a call open to PTC, but don’t have a resolution as of yet.
>

>
> Any suggestions?
>

>
> Regards,
>

>
> Daniel Nordin
> BAE Systems
> Electronic Solutions
> ET&S MCAE Support Group
>
>
> #!/bin/sh
>
> mode=$1
>
> case $mode in
>
>     'start')
>
>         /bin/su - wcadmin -c
> "/disk0/ptc/Windchill_9.1/bae_scripts/wc.init $mode"
>
>         ;;
>
>     'stop')
>
>         /bin/su - wcadmin -c
> "/disk0/ptc/Windchill_9.1/bae_scripts/wc.init $mode"
>
>         ;;
>
>     *)
>
>         echo "Usage $0 { start | stop }"
>
> esac
>
> exit 0
>
>
> ----------
rwelch
6-Contributor
(To:dnordin)

Dan,

I would bet that the xterms are problem, since there is no
X server running at system startup. Change the following
two properties in wt.properties;

From:
wt.manager.cmd.MethodServer=xterm -title {1} -sb -sl 500 -e $(wt.manager.cmd.MethodServer.java.command)
to:
wt.manager.cmd.MethodServer=$(wt.manager.cmd.MethodServer.java.command)

and

From:
wt.manager.cmd.ServerManager=xterm -title ServerManager -sb -sl 500 -e $(wt.manager.cmd.ServerManager.java.command)
to:
wt.manager.cmd.ServerManager=$(wt.manager.cmd.ServerManager.java.command)

Ron
Top Tags