Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

NoSuchFileException: null/override error when starting Liferay or executing the Upgrade Tool

Written By

Ricardo Couso

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Right after starting Liferay or executing the Upgrade Tool, there a NoSuchFileException: null/override error in the log. 
    2024-04-01 15:44:08.392 ERROR [main][DBUpgrader:110] null
    java.lang.RuntimeException: java.nio.file.NoSuchFileException: null/override
    at com.liferay.portal.util.InitUtil.initWithSpring(InitUtil.java:280)
    at com.liferay.portal.util.InitUtil.initWithSpring(InitUtil.java:196)
    at com.liferay.portal.tools.DBUpgrader.main(DBUpgrader.java:112)
    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:498)
    at com.liferay.portal.tools.db.upgrade.client.DBUpgraderLauncher.main(DBUpgraderLauncher.java:45)
    Caused by: java.nio.file.NoSuchFileException: null/override
    at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
    at sun.nio.fs.UnixFileSystemProvider.newDirectoryStream(UnixFileSystemProvider.java:427)
    at java.nio.file.Files.newDirectoryStream(Files.java:457)
    at com.liferay.portal.bootstrap.ModuleFrameworkImpl._setUpInitialBundles(ModuleFrameworkImpl.java:1743)
    at com.liferay.portal.bootstrap.ModuleFrameworkImpl.startFramework(ModuleFrameworkImpl.java:402)
    at com.liferay.portal.module.framework.ModuleFrameworkUtilAdapter.startFramework(ModuleFrameworkUtilAdapter.java:91)
    at com.liferay.portal.util.InitUtil.initWithSpring(InitUtil.java:227)
    ... 7 more

Environment

  • Quarterly Release 2023.Q3, 2023.Q4, 2023.Q1
  • Liferay DXP 7.3

Resolution

  • This error can occur when upgrading or starting Liferay on a new update but the /osgi folder is still the one associated to the previous update.
  • Make sure when starting a bundle corresponding to a newer update to not point to the older /osgi folders. 
    • Review existing symlinks and associated portal properties like module.framework.base.dir or module.framework.marketplace.dir.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?