topic Re: Java daemon exiting after rc3.d boot finishes in Operating System - HP-UX

Java daemon exiting after rc3.d boot finishes

sharathkv25 — Fri, 27 Apr 2007 20:11:24 GMT

Hi,

I have a very strange problem here.

I am starting a java daemon from /sbin/rc3.d boot level. Now this deamon is up till all the rc3.d scripts finish executing.

Once the transition from rc3.d finishes, the Java daemon is killed.

Maybe some one can help me here?

Now as you can see below,I am printing the status of "ps -efx | grep TPICS.jar" in /etc/rc.log

The output of "ps -efx | grep TPICS.jar" is this:

otroot 3046 1 8 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar

Here is the /etc/rc.log

--------------------START OF /etc/rc.log----------------

Starting the ICS daemon ...

Starting Oracle Web Server for TimePictra
Output from "/sbin/rc3.d/S504oracle_web start":
----------------------------
Oracle Web Server for TimePictra started: Current Site is not configured for replication.
warning: commands will be executed using /usr/bin/sh

Starting TimePictra SNNP Agents
Output from "/sbin/rc3.d/S505TPsnmp_sub start":
----------------------------
TimePictra SNMP Sub Agent starting: TimePictra SNMP Agents Started Status of ICS daemon is->
otroot 3046 1 8 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar

Starting HP-UX Tomcat-based Servlet Engine
Output from "/sbin/rc3.d/S823hpws_tomcat start":
----------------------------
Status of ICS daemon->
otroot 3046 1 13 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar
"/sbin/rc3.d/S823hpws_tomcat start" SKIPPED

Starting OpenView
Output from "/sbin/rc3.d/S940ov500 start":
----------------------------
Network management daemons started: ovstart: Must specify managers by name if running on OVW Clien
t
Status of ICS daemon->
otroot 3046 1 14 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar

Start CDE login server
Output from "/sbin/rc3.d/S990dtlogin.rc start":
----------------------------
Status of ICS daemon->
otroot 3046 1 24 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar

Starting PRNGD (Pseudo Random Number Generator Daemon)
Output from "/sbin/rc3.d/S99prngd.rc start":
----------------------------
PRNGD (Pseudo Random Number Generator Daemon) started
Status of ICS daemon->
otroot 3046 1 16 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar

**************************************************
HP-UX run-level transition completed
Fri Apr 27 17:54:32 PDT 2007
**************************************************

------------------END OF /etc/rc.log--------------------

Below, I am checking the status of the Java daemon from the login console:

$ ps -efx | grep TPICS.jar
otroot 3046 1 16 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar
$ ps -efx | grep TPICS.jar
otroot 3046 1 24 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar
$ ps -efx | grep TPICS.jar
otroot 3046 1 16 17:54:14 console 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar
$ ps -efx | grep TPICS.jar
otroot 3046 1 10 17:54:14 ? 0:00 /opt/java1.3/bin/../bin/PA_RISC2.0/native_threads/
java -jar /opt/osmf/DB/ics/TPICS.jar
$ ps -efx | grep TPICS.jar
$ ps -efx | grep TPICS.jar
$ ps -efx | grep TPICS.jar
$

As you saw above the java daemon was started and alive till Run Level 3 got complete.

Once Run Level 3 got complete, the Daemon is killed??

I have no errors printed, no java exceptions, nothing!!

If I start the java daemon manually, it's running fine wihout any problems.

This is only happening during boot time.

Any ideas why???

Thanks

Re: Java daemon exiting after rc3.d boot finishes

Astoetijani Priatna — Mon, 30 Apr 2007 01:06:20 GMT

Try to pick the higher sequence.. Change S505 to the higher number, like S900 above...

Re: Java daemon exiting after rc3.d boot finishes

Senthil Kumar.A — Mon, 30 Apr 2007 01:14:04 GMT

Hi,

Can you give the output of the following command.

ll /sbin/rc3.d

Senthil

Re: Java daemon exiting after rc3.d boot finishes

sharathkv25 — Mon, 30 Apr 2007 10:56:41 GMT

>>Senthil

$ ll /sbin/rc3.d/
total 0
lrwxr-xr-x 1 root root 23 Oct 10 2006 S100nfs.server -> /sbin/init.d/nfs.server
lrwxr-xr-x 1 root sys 19 Oct 10 2006 S200tps.rc -> /sbin/init.d/tps.rc
lrwxr-xr-x 1 root sys 17 Apr 27 16:32 S503osmf -> /sbin/init.d/osmf
lrwxr-xr-x 1 root sys 23 Apr 27 16:32 S504oracle_web -> /sbin/init.d/oracle_web
lrwxr-xr-x 1 root sys 23 Nov 11 21:38 S505TPsnmp_sub -> /sbin/init.d/TPsnmp_sub
lrwxr-xr-x 1 bin bin 24 Oct 10 2006 S823hpws_tomcat -> /sbin/init.d/hpws_tomcat
lrwxr-xr-x 1 root sys 18 Oct 10 2006 S940ov500 -> /sbin/init.d/ov500
lrwxr-xr-x 1 root sys 23 Oct 10 2006 S990dtlogin.rc -> /sbin/init.d/dtlogin.rc
lrwxr-xr-x 1 root sys 21 Oct 10 2006 S99prngd.rc -> /sbin/init.d/prngd.rc

>>Astoetijani

Is it ok to change to a higher number?.

Currently only the java daemon is exiting, everything else is ok. I don't want to break something else trying to fix this java daemon.

What does S503/S900 mean?

Thanks

Re: Java daemon exiting after rc3.d boot finishes

Steven E. Protter — Mon, 30 Apr 2007 12:13:17 GMT

Shalom,

What does S503/S900 mean?

Setting the soft link to a higher number makes the daemon start later.

That might not help in this case as the daemon may need to start before other applications.

Also look for a K soft link in run level three that may be shutting down the daemon.

SEP

Re: Java daemon exiting after rc3.d boot finishes

Astoetijani Priatna — Mon, 30 Apr 2007 21:57:28 GMT

S505TPsnmp_sub start.

S: startup
505 is the startup sequence number.
TPsnmp_sub is script name.

So I am wondering whether your script is depend on other thing, which start after TPsnmp_sub...

You have to make sure it's dependencies script running before TPsnmp_sub

Also, if there is any other stuff depend on TPsnmp_sub, you have to put the sequence after TPsnmp_sub...