Server does not start after upgrade from 5.1.1 to 5.1.2 (binary version '5.1.1....' does not match the installed version '5.1.2....')

[pzygielo]

Describe the bug
Server does not start after upgrade from 5.1.1 to 5.1.2

To Reproduce
Steps to reproduce the behavior:

1. stop current (5.1.1) opendj
2. backup (saved me this time)
3. unzip 5.1.2 (cksum: 403568937 76728473 opendj-5.1.2.zip) over current installation
4. execute upgrade
5. start upgraded opendj

Expected behavior
5.1.2 to start and operate normally

Screenshots

# ./upgrade 

>>>> OpenDJ Upgrade Utility

 * OpenDJ will be upgraded from version
 5.1.1.eefd084c464aaa6492814a833d804a93e2001782 to
 5.1.2.0802aa4081e1c175c40bde1af59439a20fcc5670
 * See '.../opendj/logs/upgrade.log' for a detailed log of this
 operation

>>>> Preparing to upgrade

  The upgrade is ready to proceed. Do you wish to continue? (yes/no) [yes]: 


>>>> Performing upgrade

  Replacing schema file '02-config.ldif'..............................   100%     
  Archiving concatenated schema.......................................   100%     

>>>> OpenDJ was successfully upgraded from version
5.1.1.eefd084c464aaa6492814a833d804a93e2001782 to
5.1.2.0802aa4081e1c175c40bde1af59439a20fcc5670

 * See '.../opendj/logs/upgrade.log' for a detailed log of this

in my case upgrade.log is actually empty.

then - on starting here's server.out:

[17/Jul/2026:19:33:17 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerShutdown, alert ID org.opends.messages.core-141): The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServer and the reason provided for the shutdown was An error occurred while trying to start the Directory Server: InitializationException: The OpenDJ binary version '5.1.1.eefd084c464aaa6492814a833d804a93e2001782' does not match the installed version '5.1.2.0802aa4081e1c175c40bde1af59439a20fcc5670'. Please run upgrade before continuing (DirectoryServer.java:1331 DirectoryServer.java:5054)

running upgrade again:

# ./upgrade 
 * OpenDJ has already been upgraded to version
 5.1.2.0802aa4081e1c175c40bde1af59439a20fcc5670

Desktop (please complete the following information):

• OS: Ubuntu 24.04

---

Vote to raise the priority 🖐️

[vharseko]

Try clean lib directory before unzip

[pzygielo]

Try clean lib directory before unzip

That helpded, and I'm getting

[18/Jul/2026:07:53:28 +0000] category=CORE severity=NOTICE msgID=139 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID org.opends.messages.core-135): The Directory Server has started successfully

🎉

Thank you!

[pzygielo]

Closing as the PR with fix is merged already.

[pzygielo]

• I'm confused - it seems Fix duplicate opendj-server-legacy classes in distribution lib/ #661 was included in 5.1.2. Should something similar be considered for upgrade process separately?
• Reopening to let the Team decide for the state of this issue.

[vharseko]

lib/org.openidentityplatform.opendj.opendj-server-legacy.jar — an unwanted duplicate after upgrade without delete old libraries

[pzygielo]

lib/org.openidentityplatform.opendj.opendj-server-legacy.jar — an unwanted duplicate after upgrade without delete old libraries

But in https://doc.openidentityplatform.org/opendj/install-guide/chap-upgrade I can't see any mention for special step to delete anything.

IMO - this is not completed.

[vharseko]

@pzygielo you're right, this wasn't complete — thanks for reopening.

#661 removed the duplicate org.openidentityplatform.opendj.opendj-server-legacy.jar from fresh distributions, but it didn't cover the upgrade path. Unzipping 5.1.2 over an older install leaves the old copy behind (it's no longer in the archive, so nothing overwrites or removes it), and since the launcher builds the classpath from lib/*, that stale 5.1.1 jar makes the runtime report the old binary version and refuse to start. Cleaning lib/ before unzip works because it removes that leftover.

PR #751 addresses both sides:

• Automatic fix (ships in 5.2.0): an upgrade task now deletes the leftover lib/org.openidentityplatform.opendj.opendj-server-legacy.jar, so no manual step will be needed when upgrading to 5.2.0+.
• Docs: a note has been added to the upgrade guide describing the manual lib/ cleanup, since the already-released 5.1.2 doesn't have the automatic task yet.

Since 5.1.2 is already out, the manual cleanup (or unzip after clearing lib/) remains the workaround for upgrading to 5.1.2 specifically; upgrades to 5.2.0+ will handle it on their own.