Troubleshooting
Problem
After applying a fix or fix pack with the Update Installer, servers (Dmgr, NodeAgent, and AppServers) may fail to start. The SystemOut.log will not even be generated to indicate why. The startServer.log shows: ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in z/OS® ) and other log files under /home/dwhare/WebSphere61/profiles/Dmgr01/logs/dmgr should contain failure information.
Symptom
ADMU3011E: Server launched but failed initialization. startServer.log, SystemOut.log(or job log in z/OS® ) and other log files under /home/dwhare/WebSphere61/profiles/Dmgr01/logs/dmgr should contain failure information.
!ENTRY org.eclipse.osgi 2006-08-24 09:04:14.597
!MESSAGE Error reading configuration: /home/dwhare/WebSphere61/profiles/Dmgr01/configuration/org.eclipse.osgi/.manager/.fileTableLock (Permission denied)
!STACK 0
java.io.FileNotFoundException: /home/dwhare/WebSphere61/profiles/Dmgr01/configuration/org.eclipse.osgi/.manager/.fileTableLock (Permission denied)
at java.io.FileOutputStream.openAppend(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:203)
at org.eclipse.core.runtime.internal.adaptor.Locker_JavaNio.lock(Locker_JavaNio.java:34)
at org.eclipse.core.runtime.adaptor.FileManager.lock(FileManager.java:361)
at org.eclipse.core.runtime.adaptor.FileManager.open(FileManager.java:658)
at ...
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21244631