|
Problem(Abstract) |
Error was thrown due to file permission in jmsserver logs
root. This is an indication that the server is attempting to start as root
and WebSphere® Application Server is installed under different id.
Example: owner: WebSphere group: WebSphere
[5/20/05 12:20:38:674 EDT] d24e3f WsServerLaunc E ADMU3002E: Exception
attempting to process server jmsserver
[5/20/05 12:20:38:675 EDT] d24e3f WsServerLaunc E ADMU3007E: Exception
com.ibm.ws.process.exception.InvalidFileException: PROC0007E: Some files
required by the process or the process definition were inaccessible.
Please check the standard in, out, and error file redirects and
directories. Process could not be created.
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:141)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
at
com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.ja
va:66)
[5/20/05 12:20:38:676 EDT] d24e3f AdminTool E ADMU0111E: Program exiting
with error: com.ibm.ws.process.exception.InvalidFileException:
PROC0007E: Some files required by the process or the process definition
were inaccessible. Please check the standard in, out, and error file
redirects and directories. Process could not be created.
at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:141)
at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
Information Center Definition:
ADMU3002E: Exception attempting to process server {0}
Explanation: A more detailed exception has occurred while attempting to
start or stop the named server. This message is always paired with a
second message that displays the detailed exception.
User Response: Record and save the exception information in the follow-on
message for further problem determination.
ADMU3007E: Exception {0}
Explanation: Some general exception condition has been discovered.
User Response: Combine this information with additional exception messages
in order to perform additional problem determination.
PROC0007E: Some files required by the process or the process definition
were inaccessible. Please check the standard in, out, and error file
redirects and directories. Process could not be created.
Explanation: Some files the process needs for execution were not
accessible by the process. This is commonly log files (redirects of
standard out and error, or directories they reside in) that are not set
readable and writable to the user id that will be running the process that
will access them.
User Response: Check the standard out and error redirection files and
their directories to make sure they're readable and writable by the userid
that will be running the process.
ADMU0111E: Program exiting with error: {0}
Explanation: An exception occurred during program execution.
User Response: Record the exception information from this message and
perform problem determination using that exception data |
|
|
|
Cause |
File permission issue on /logs/jmsserver directory. |
|
|
Resolving the
problem |
Resolutions:
Things to check for validating the configuration:
1. Validate that jmsserver – server.xml file is showing with correct logs
path.
Example:
fileName="$(LOG_ROOT)/jmsserver/SystemErr.log"
fileName="$(LOG_ROOT)/jmsserver/SystemOut.log"
<execution xmi:id="ProcessExecution_1096393828578"
processPriority="1000" runAsUser="mqm" runAsGroup="mqm"
runInProcessGroup="0"/>
<ioRedirect xmi:id="OutputRedirect_1096393828578"
stdoutFilename="${LOG_ROOT}/jmsserver/native_stdout.log"
stderrFilename="${LOG_ROOT}/jmsserver/native_stderr.log"/>
2. Is WebSphere running as root or non-root? If the WebSphere is running
as non-root then you need to validate the following steps to correct the
problem.
If running the jmsserver, the group must be mqm in order for the
jmsserver to start WebSphere JMS Provider.
For the steps that follow, assume that "wasjms" is the user id to run
all the servers, and that "mqm" is the group. If not running server,
a different group may be used.
1) Create user id wasjms with primary group mqm
2) If running jmsserver, add user wasjms to group mqbrkrs too.
3) Reboot machine
4) From admin console: System
Management --> Node
Agents --> Node
agent (for the node) -->
Process Definition -->
Process
Execution
Umask: 002
User: wasjms
Group: mqm
5) This step must be applied to all servers. Substitute
"server1"
with
the name of each application server in the node:
Servers -->
Application Servers -->
server1 --> Process
Definition
--> Process Execution
Umask: 002
User: wasjms
Group: mqm
6) JMS Servers -->
jmsserver (for the node)
--> Process
Definition --> Process
Execution
Umask: 002
User: wasjms
Group: mqm
7) Save and synchronize
8) Stop all servers, including jmsserver
9) Stop node
10) If running the jmsserver, as root, run:
deletemq.sh <cellname> <nodename>
jmsserver
11) If running the jmsserver, as wasjms, run:
createmq.sh <wshome> <cellname>
<nodename> jmsserver
where <wshome> is where WebSphere is installed,
e.g.,
/opt/WebSphere/AppServer
12) As root, change file permission's as follows, assuming
/opt/WebSphere/AppServer is the WebSphere installation
directory:
chgrp mqm /opt/WebSphere
chgrp mqm /opt/WebSphere/AppServer
chgrp -R mqm /opt/WebSphere/AppServer/config
chgrp -R mqm /opt/WebSphere/AppServer/logs
chgrp -R mqm /opt/WebSphere/AppServer/wstemp
chgrp -R mqm
/opt/WebSphere/AppServer/installedApps
chgrp -R mqm /opt/WebSphere/AppServer/temp
chgrp -R mqm /opt/WebSphere/AppServer/tranlog
chgrp -R mqm /opt/WebSphere/AppServer/cloudscape50
chgrp -R mqm /opt/WebSphere/AppServer/cloudscape51
chgrp -R mqm
/opt/WebSphere/AppServer/bin/DefaultDB
chmod g+w /opt/WebSphere
chmod g+w /opt/WebSphere/AppServer
chmod -R g+w /opt/WebSphere/AppServer/config
chmod -R g+w /opt/WebSphere/AppServer/logs
chmod -R g+w /opt/WebSphere/AppServer/wstemp
chmod -R g+w
/opt/WebSphere/AppServer/installedApps
chmod -R g+w /opt/WebSphere/AppServer/temp
chmod -R g+w /opt/WebSphere/AppServer/tranlog
chmod -R g+w /opt/WebSphere/AppServer/cloudscape50
chmod -R g+w /opt/WebSphere/AppServer/cloudscape51
chmod -R g+w
/opt/WebSphere/AppServer/bin/DefaultDB
13) Login as wasjms
14) Start node and servers
15) If running jmsserver with WebSphere JMS Provider, run "dspmq" to
ensure that the MQ queue is running. The name of the queue is
WAS_<nodename>_jmsserver
Java_Message_Service__JMS_/swg21110884.html |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
Historical Number |
52561
278
000 |
|
|
|
|