Greetings;
The real test is to eg.;
cd /etc/rc3.d
./K20apache status
this should give you something like
Usage: /etc/init.d/apache
{start|stop|reload|reload-modules|force-reload|restart}
if it doesn't then your links in the rc.? directories are incorrect.
Good Luck!
Dennis
James Melin
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
pin.mn.us> cc:
Sent by: Linux on Subject: Re: Things not starting at
IPL
390 Port
<[EMAIL PROTECTED]
T.EDU>
04/01/2003 09:14 AM
Please respond to
Linux on 390 Port
There is a member in /etc/init.d called apache. Issuing the command
./apache start is what I used to start the httpd server. Again, I see an
HMC message indicating that the HTTPD has started: Starting httpd [ LDAP
PERL PHP4 SSL ]. This is the same message I see when I start things
manually.
As to the jboss link, I have a symbolic in /opt called jboss that is
symbolically linked to the jboss install directory.
This allows me to test a new install of jboss in a diff tree just by
changing the link:
rockhopper:/etc/init.d # ls -al /opt/ | grep jboss
lrwxrwxrwx 1 root root 24 Mar 11 13:37 jboss ->
jboss-3.0.4_tomcat-4.0.6
drwxrwxrwx 8 root root 4096 Nov 2 19:53
jboss-3.0.4_tomcat-4.0.6
The script in the /etc/init.d directory sets the env. var JBOSS_HOME as
this snippet indicates
#define where jboss is - this is the directory containing directories log,
bin, conf etc
JBOSS_HOME=${JBOSS_HOME:-"/opt/jboss"}
#make java is on your path
JAVAPTH=${JAVAPTH:-"$JAVA_HOME/bin"}
#define the classpath for the shutdown class
JBOSSCP=${JBOSSCP:-"$JBOSS_HOME/bin/shutdown.jar"}
#define the script to use to start jboss
JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh"}
Again running ./jboss start from /etc/init.d works, just like apache does.
As to jboss,
|---------+---------------------------->
| | Dennis Wicks |
| | <[EMAIL PROTECTED]> |
| | Sent by: Linux on|
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | IST.EDU> |
| | |
| | |
| | 04/01/2003 09:00 |
| | AM |
| | Please respond to|
| | Linux on 390 Port|
| | |
|---------+---------------------------->
>
------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Things not starting at IPL
|
>
------------------------------------------------------------------------------------------------------------------------------|
Greetings;
I am pretty sure that the links for apache are incorrect.
../apache is usually a directory and ../jboss probably is also.
The correct links are more likely of the form
K20apache -> ../init.d/apache
Good Luck!
Dennis
James Melin
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
pin.mn.us> cc:
Sent by: Linux on Subject: Things not
starting at IPL
390 Port
<[EMAIL PROTECTED]
T.EDU>
04/01/2003 08:38 AM
Please respond to
Linux on 390 Port
I have a situation where various things are not starting properly at boot.
I see the message for the httpd server on the HMC console: Starting httpd
[ LDAP PERL PHP4 SSL ] but when I telnet in, the task is not running and I
don't see anything in the log that truly indicates why it's not there.
Also, JBOSS is not starting at IPL, even though the items in
etc/init.d/rc3/d are ok. (or appear to be). Lastly, one component of
DB2connect EE isn't starting either. That is the db2sysc process, in the
8.1 version of DB2 connect. I have had to logon as db2inst1 and issue a
db2start command to get that to work. Nothing for it was created in
/etc/init.d or any of the rc.x sub dirs. Any insight?
Here are the RC3.d entries for apache/jboss. I believe the links are
correct. The actual scripts themselves do function to start/stop the tasks.
Apache
lrwxrwxrwx 1 root root 9 Feb 27 13:57 K02apache ->
../apache
lrwxrwxrwx 1 root root 9 Mar 9 14:46 S23apache ->
../apache
Jboss:
lrwxrwxrwx 1 root root 8 Mar 11 13:56 K01jboss ->
../jboss
lrwxrwxrwx 1 root root 8 Mar 11 13:56 S21jboss ->
../jboss
