PK93557: UNABLE TO START SERVER AS A ROOT WHEN HAVING A NON-ROOT USER AS THE RUN AS USER FOR SERVER PROCESS USING A NON

Fixes are available

APAR status

Closed as program error.

Error description

If a customer is using a non-IBM JVM to start a server from
the command line as root and specified a non-root user as the
Run As User for the server process, server start up may fail.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V7.0 who use a non-IBM JVM and the   *
*                  RUN AS USER attribute for a server process. *
****************************************************************
* PROBLEM DESCRIPTION: If you are using a non-IBM JVM to       *
*                      start a server from the command line    *
*                      as root and specify a non-root user as  *
*                      the Run As User for the server process, *
*                      server start up may fail                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This problem may be seen when all of the following conditions
apply:

1) You are using a non-IBM JVM (this is true on the Solaris
operating system, for example).

2) The server is started by a different user(such as a Root
userid) than the runAsUser from the command line.  For example,
a server from the command line logged in as a root userid and
the server is configured to run as a specific non-root user
(that is, a runAsUser attribute is set for the server process.).

In this situation during a deployment manager start up, the
following error was displayed at the command-line:

ADMU3200I: Server launched. Waiting for initialization status.
   ADMU3011E: Server launched but failed initialization.
startServer.log,              SystemOut.log(or job log in zOS)
and other log files under
/opt/software/WebSphere7/AppServer/profiles/Dmgr1/logs/dmgr
should contain failure information.

The SystemOut.log contained the following error indicating that
the server could not read a configuration file because
permission was denied:

[7/26/09 8:47:56:052 EDT] 0000000b FfdcProvider  I
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
Incident emitted on
/opt/software/WebSphere7/AppServer/profiles/Dmgr1/logs/ffdc/dmgr
_xxxxxxxxxxx.txt
com.ibm.ws.management.repository.FileDocument.createTempFile 404
[7/26/09 8:47:56:098 EDT] 0000000b FileDocument  E   ADMR0104E:
The system is unable to read document
cells/myCell/nodes/myNode/node-metadata.properties:
java.io.IOException: Permission denied
 at java.io.UnixFileSystem.createFileExclusively(Native
Method)
 at java.io.File.checkAndCreate(File.java:1704)
 at java.io.File.createTempFile(File.java:1793)
 at
com.ibm.ws.management.repository.FileDocument.createTempFile(Fil
eDocument.java:564)
 at
com.ibm.ws.management.repository.FileDocument.read(FileDocument.
java:500)
 at
com.ibm.ws.management.repository.FileRepository.extractInternal(
FileRepository.java:1130)
 at
com.ibm.ws.management.repository.FileRepository.extract(FileRepo
sitory.java:1102)
 at
com.ibm.ws.management.repository.FileRepository.extract(FileRepo
sitory.java:1053)
 at
com.ibm.ws.management.repository.FileRepository.extract(FileRepo
sitory.java:1042)
 at
com.ibm.ws.management.repository.client.LocalConfigRepositoryCli
ent.extract(LocalConfigRepositoryClient.java:141)
 etc.

Problem conclusion

The code was modified so that the launcher does not create
temporary directories when it accesses the configuration
repository.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK93557
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-10
Closed date
2009-09-17
Last modified date
2009-09-17

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

Fix information

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

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PK93557: UNABLE TO START SERVER AS A ROOT WHEN HAVING A NON-ROOT USER AS THE RUN AS USER FOR SERVER PROCESS USING A NON_IBM JVM

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:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?