IBM Support

Security Key Lifecycle Manager Fix pack fails when stopping WebSphere stopsServer.log exit code: 246

Troubleshooting


Problem

Installing SKLM Fix pack4 fails to properly stop WebSphere with:
     "Error executing /opt/IBM/WebSphere/AppServer/bin/stopServer.sh: status=246"
Additionally, when manually trying to stopServer.sh with the service command, the stop operation also fails. 
[root@sklm bin]# service SecurityKeyLifecycleManager_was.init stop
Stopping WebSphere Application Server - server1 ...
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/KLMProfile/logs/server1/stopServer.log
ADMU0128I: Starting tool with the KLMProfile profile
ADMU3100I: Reading configuration for server: server1
com.ibm.rmi.ras.Utility.newWriter: could not write to orbtrc.03032022.0844.53.txt : java.io.FileNotFoundException: /orbtrc.03032022.0844.53.txt (Permission denied)
com.ibm.rmi.ras.Utility.newWriter: could not write to orbmsg.03032022.0844.53.txt : java.io.FileNotFoundException: /orbmsg.03032022.0844.53.txt (Permission denied)
ADMU0509I: The server "server1" cannot be reached. It appears to be stopped.

ADMU0211I: Error details may be seen in the file:
           /opt/IBM/WebSphere/AppServer/profiles/KLMProfile/logs/server1/stopServer.log
exit code: 246

Symptom

The installation of an SKLM Fix pack due to the WebSphere Application Server failing to stop with an exit code of 246.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSWPVP","label":"IBM Security Key Lifecycle Manager"},"ARM Category":[{"code":"a8m0z000000cvdzAAA","label":"SKLM-\u003EINSTALL-\u003EFIXPACK"}],"ARM Case Number":"TS008608086","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
10 March 2022

UID

ibm16560993