Confluence won't start with java.io.IOException: No locks available
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Confluence installation would not start with the following error in catalina.out
ERROR: Error creating bundle cache.
(java.lang.Exception: Unable to lock bundle cache: java.io.IOException: No locks available)java.lang.Exception: Unable to lock bundle cache: java.io.IOException: No locks available
at org.apache.felix.framework.cache.BundleCache.<init>(BundleCache.java:176)
at org.apache.felix.framework.Felix.init(Felix.java:640)
at org.apache.felix.framework.Felix.start(Felix.java:893)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager$4.run(FelixOsgiContainerManager.java:417)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "Felix:Startup" com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to start felix
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager$4.run(FelixOsgiContainerManager.java:422)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.osgi.framework.BundleException: Error creating bundle cache.
at org.apache.felix.framework.Felix.init(Felix.java:645)
at org.apache.felix.framework.Felix.start(Felix.java:893)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager$4.run(FelixOsgiContainerManager.java:417)
... 1 more
Caused by: java.lang.Exception: Unable to lock bundle cache: java.io.IOException: No locks available
at org.apache.felix.framework.cache.BundleCache.<init>(BundleCache.java:176)
at org.apache.felix.framework.Felix.init(Felix.java:640)
... 3 more
And the following error message in atlassian-confluence.log
ERROR [localhost-startStop-1] [atlassian.plugin.loaders.ScanningPluginLoader] deployPluginFromUnit Because of the following exception:
java.lang.IllegalStateException: Unable to create a tracker when osgi is not running
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:606)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:596)
at com.atlassian.plugin.osgi.factory.RemotablePluginFactory$1.create(RemotablePluginFactory.java:60)
at com.atlassian.plugin.osgi.factory.OsgiChainedModuleDescriptorFactoryCreator.create(OsgiChainedModuleDescriptorFactoryCreator.java:68)
at com.atlassian.plugin.osgi.factory.RemotablePluginFactory.getChainedModuleDescriptorFactory(RemotablePluginFactory.java:133)
at com.atlassian.plugin.osgi.factory.RemotablePluginFactory.create(RemotablePluginFactory.java:99)
at com.atlassian.plugin.loaders.ScanningPluginLoader.deployPluginFromUnit(ScanningPluginLoader.java:155)
at com.atlassian.plugin.loaders.ScanningPluginLoader.loadAllPlugins(ScanningPluginLoader.java:89)
at com.atlassian.plugin.loaders.PermissionCheckingPluginLoader.loadAllPlugins(PermissionCheckingPluginLoader.java:24)
at com.atlassian.plugin.manager.DefaultPluginManager.earlyStartup(DefaultPluginManager.java:461)
at com.atlassian.confluence.plugin.ConfluencePluginManager.earlyStartup(ConfluencePluginManager.java:138)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:436)
at com.atlassian.confluence.setup.SetupPluginManager.init(SetupPluginManager.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
...
Diagnosis
Environment
- You are hosting either the Confluence home or installation directory on an NFS mount
Cause
This error is usually caused by the NFS lockd
not running or malfunctioning. Other NFS daemons not running/malfunctioning may cause similar errors too.
Resolution
Restart and verify functionality of all NFS related daemons on your system, most importantly lockd
. See the following page for further reference: http://osr507doc.sco.com/en/NetAdminG/nfsC.daemons.html