By: Ferenc Schulcz user 29 Jul 2021 at 4:51 a.m. CDT

3 Responses
Ferenc Schulcz gravatar
I'm trying to use the gluufederation/opendj:4.3.0_b1 docker image with my gluu installation. The container restarts every ~10 seconds. This part of the logs seems to be the most useful: "The OpenDJ binary version '4.4.10.7d150b89b2bbc84ad5aa3431634de337a9d2e32c' does not match the installed version '4.0.0.a647132f766ca29542a072c835a4a31a3436d12f'. Please run upgrade before continuing". Docker logs repeat the following: INFO - pygluu.containerlib.wait - 2021-07-27 06:18:50,630 - Config is ready INFO - pygluu.containerlib.wait - 2021-07-27 06:18:50,662 - Secret is ready INFO - entrypoint - 2021-07-27 06:18:52,332 - Syncing OpenDJ certs. INFO - entrypoint - 2021-07-27 06:18:52,436 - Checking certificate's Subject Alt Name (SAN) INFO - entrypoint - 2021-07-27 06:18:52,472 - Loading Serf key from secrets ==> Starting Serf agent... ==> Starting Serf agent RPC... ==> Serf agent running! Node name: 'ldap' Bind addr: '0.0.0.0:7946' Advertise addr: '192.168.128.6:7946' RPC addr: '127.0.0.1:7373' Encrypted: true Snapshot: false Profile: lan Message Compression Enabled: true ==> Log data will now stream in as it occurs: INFO - ldap_peer - 2021-07-27 06:18:53,567 - Loading initial Serf peers from /etc/gluu/conf/serf-peers-static.json WARNING - ldap_peer - 2021-07-27 06:18:53,567 - Unable to load initial Serf peers from /etc/gluu/conf/serf-peers-static.json; reason=[Errno 2] No such file or directory: '/etc/gluu/conf/serf-peers-static.json' INFO - ldap_replicator - 2021-07-27 06:18:55,661 - Getting current server info INFO - ldap_replicator - 2021-07-27 06:18:55,727 - Checking replicated backends (attempt 1) [27/Jul/2021:06:18:58 +0000] category=com.forgerock.opendj.ldap.config.config severity=NOTICE msgID=571 msg=Loaded extension from file '/opt/opendj/lib/extensions/snmp-mib2605.jar' (build 4.4.10, revision 7d150b89b2bbc84ad5aa3431634de337a9d2e32c) [27/Jul/2021:06:18:59 +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 '4.4.10.7d150b89b2bbc84ad5aa3431634de337a9d2e32c' does not match the installed version '4.0.0.a647132f766ca29542a072c835a4a31a3436d12f'. Please run upgrade before continuing (DirectoryServer.java:1327 DirectoryServer.java:5041) Exception in thread "main" java.lang.NullPointerException It seems to be an issue inside the container, but the error message is kinda cryptic. What upgrade should I run? What could be the issue?

By Aliaksandr Samuseu staff 17 Aug 2021 at 1:07 p.m. CDT

Aliaksandr Samuseu gravatar
Hi, Ferenc. Apparently, there was an inssue with notifications about new tickets, so some of them were missed. Let us know if you still need help with this one.

By Ferenc Schulcz user 17 Aug 2021 at 4:18 p.m. CDT

Ferenc Schulcz gravatar
Hello, thanks for reaching back! Apparently I have found the issue. Opendj writes its version in a file named buildinfo. The last message in the logs show a version mismatch, as I had previously upgraded from an older version. I updated the file with the new version number and the crash loop was solved.

By Aliaksandr Samuseu staff 17 Aug 2021 at 4:43 p.m. CDT

Aliaksandr Samuseu gravatar
Glad to hear it's resolved. Mind me asking what upgrade procedure did you follow that resulted in such an issue? Was it something recommended in our docs? We may need to review them then.