Java processes won't start - Error initializing storage, Unable to create lock manager
Article ID: 257003
Updated On:
Products
Issue/Introduction
When attempting to start the JWP with the command:
nohup java -d64 - jar ucsrvpjp.jar -I/automic/AutomationEngine/bin/ucsrv.ini &
nohup.out showed the following error:
Exception in thread "main" java.lang.RuntimeException: Error initializing storage.
at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:71)
at org.eclipse.osgi.launch.Equinox.<init>(Equinox.java:31)
at org.eclipse.osgi.launch.EquinoxFactory.newFramework(EquinoxFactory.java:24)
at com.automic.server.startup.Main.main(Main.java:118)
Caused by: java.io.IOException: Unable to create lock manager.
at org.eclipse.osgi.storagemanager.StorageManager.open(StorageManager.java:698)
at org.eclipse.osgi.storage.Storage.getChildStorageManager(Storage.java:2011)
at org.eclipse.osgi.storage.Storage.getInfoInputStream(Storage.java:2028)
at org.eclipse.osgi.storage.Storage.<init>(Storage.java:216)
at org.eclipse.osgi.storage.Storage.createStorage(Storage.java:151)
at org.eclipse.osgi.internal.framework.EquinoxContainer.<init>(EquinoxContainer.java:69)
... 3 more
Environment
Release : 21.0.4
Cause
Two possible causes:
-
This can be caused by either being out of space
-
This error can be caused by multiple users (i.e. root) starting the Java proecesses (JWP, JCP, REST) and files in the AutomationEngine/bin/configuration folder being owned by those users and not being able to be re-written or accessible by the user attempting to start the java processes (ie. user automic).
Resolution
Check to be sure there is enough space on the drive and for the user starting the service manager or J*P process
Change ownership using the command:
chown automic:automic -R ./configuration/
from the AutomationEngine/bin folder
Then the java processes were able to start
Feedback
