Kim, I had similar problems until I renamed the Sxx* link for the websphere start to be the last to start. The default started it too early. This fixed my start issues. Tom Driscoll Utah Retirement Systems
Kim Goldenberg <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
11/05/2007 01:12 PM
Please respond to
Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
To
LINUX-390@VM.MARIST.EDU
cc
Subject
SLES9 Services
Hello all -
I am attempting to set up WebSphere App Server for HATS so that it
starts up correctly. If I take the startup scripts that WAS creates,
they end up in a jumble that never gets off the ground after a Linux
reboot. They seem to have started, but they never really initialize. If
I do it manually, I start the HTTP server with their version of
apachectl, then I start the DepMgr, the NodeAgent and finally the
AppServer, and all is well.
I am attempting to use the Required-Start: items in the script
headers to make them start in the (?seemingly?) required order. I had to
change the Provides: statement to make each one different (The DepMgr,
NodeAgent, and AppServer all said "Websphere init" for that) and added
the information to apachectl to give the same information.
apachectl Required-Start: $network $syslog
DepMgr Required-Start: $network $syslog apachectl
NodeAgent Required-Start: $network $syslog apachectl DepMgr
AppServer Required-Start: $network $syslog apachectl Depmgr NodeAgent
The scripts are called the same as the Provides: string. No matter what,
they end up in a clump as either S01... or S02... and network is
$05network, etc. I am using Yast Runlevel Editor Expert mode to
enable/disable them.
What am I doing wrong?
Kim
--
Kim Goldenberg
Systems Programmer I
State of NJ - OIT
609-777-3722
[EMAIL PROTECTED]
[EMAIL PROTECTED]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
kgoldenberg.vcf
Description: Binary data
