PK36189: WASSERVICE CREATED SERVICE ON LINUX SUSE 9 DOES NOT START WHEN THE SERVER IS REBOOTED IF SET TO LEVEL 3 OR 5

Fixes are available

APAR status

Closed as program error.

Error description

When wasservice is used to create a service on Linux SUSE
version 9, the service will not start with a restart of the
operating system if the service is set to level 3 or 5.
wasservice.sh places it scripting into these directories
/etc/init.d/rc3.d
/etc/init.d/rc5.d
This will cause WebSphere to start before the network is up
and on a shutdown cause WebSphere to be stopped after the
network is down.

Local fix

The following is information that may be useful if attempting to
work around this...

Contents of /etc/init.d/rc3.d and /etc/init.d/rc5.d as the
result of
wasservice.sh
.
S00nodeAgent_was.init.......
K15nodeAgent_was.init..........
.
AFTER a manual correction it looks like that appears to work
.
S15nodeAgent_was.init.......
K00nodeAgent_was.init..........
.
NOTE: the Sxx and Kxx define the sequential order of a S=start
and
      K=kill script. Will say S00 runs first, then S01 aso......
      The network support is started as S07......

Problem summary

****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server        *
*                 version 6.1 Service on SuSE linux 9          *
*                 (possibly others).                           *
****************************************************************
* PROBLEM DESCRIPTION: Application Server service is unable    *
*                      to start through linux service on       *
*                      SuSE 9.                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Entries placed in init files on SuSE 9 attempt to start
Application Server before the network interface is up,
resulting in failure. Also will stop Application Server after
the network is down.

Problem conclusion

Fixed the problem with WebSphere Application Server service.

Fix is targeted for fixpack 6.1.0.7.
Please refer to the recommended updates page for delivery
information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Alter init file

So - what we have is:



# The next lines are for chkconfig on RedHat and SuSE systems.

# chkconfig: 2345 98 02

# description: Starts and stops WebSphere Application Server \

#              instances. This service was created via the \

#              wasservice command.



And what we need is:



# The next lines are for chkconfig on RedHat systems.

# chkconfig: 2345 98 02

# description: Starts and stops WebSphere Application Server \

#              instances. This service was created via the \

#              wasservice command.



# The next lines are for chkconfig on SuSE systems.

# Provides: WebSphere init

# Required-Start: $network $syslog

# Required-Stop:

# Default-Start: 2 3 4 5

# Default-Stop: 0 6

# Short-Description: Starts and stops WebSphere Application
Server
instances

Comments

APAR Information

APAR number
PK36189
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2006-12-14
Closed date
2007-01-19
Last modified date
2007-01-19

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Modules/Macros

```
SERVICE
```

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61I PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK36189: WASSERVICE CREATED SERVICE ON LINUX SUSE 9 DOES NOT START WHEN THE SERVER IS REBOOTED IF SET TO LEVEL 3 OR 5

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61I PSY

Document Information

Share your feedback

Need support?