Since its release in Q4 2025, I have worked on several upgrades from 23.4 to 25.4. The first one I worked on was for a customer using our own custom Documentum images. If you have followed my posts for some time, you might recall a previous blog post where I discussed a Documentum 20.2 to 23.4 upgrade and some issues related to IPv6 being disabled (c.f. this blog).
1. Environment details
The source Documentum 23.4 environment was configured exactly like the one from that previous blog post, with the fix to ensure the components could start and run on IPv4 only. Using the exact same source code, I simply rebuilt the image with the same OS version (RHEL8 for Dctm 23.4). One difference was that I was previously running on a vanilla Kubernetes cluster, while for this blog I used RKE2 (from SUSE), meaning the OS and Kubernetes cluster were not the same.
At the Documentum level, the Connection Broker was configured with “host=${Current-IPv4}” to force it to start with IPv4 only. The Repository had “ip_mode = V4ONLY” in its “server.ini” to achieve the same behavior. With these two configurations, the Documentum 23.4 environment was installed from scratch without any issues and was running properly. I performed several pod restarts over the next few days, and everything was running smoothly.
2. Upgrade to Documentum 25.4
Then it was time to upgrade the environment to 25.4. For that purpose, I built a new image on RHEL9 (switching from ubi8 to ubi9 for the base image). I had no problems with the preparation or the installation of the other binaries.
I then triggered the upgrade process, which completed successfully for the Connection Broker. However, when it reached the Repository part, things were not that simple. The Repository upgrade log file contained the following:
[dmadmin@cs-0 ~]$ cat $DM_HOME/install/logs/install.log
20:30:29,056 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - Log is ready and is set to the level - INFO
20:30:29,060 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product name is: UniversalServerConfigurator
20:30:29,060 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product version is: 25.4.0000.0143
20:30:29,060 INFO [main] -
20:30:29,089 INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - Done InitializeSharedLibrary ...
20:30:29,117 INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentCheckVaultStatus - Checking the vault status: Silent mode
20:30:29,117 INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentCheckVaultStatus - Checking whether vault enabled or not
20:30:29,121 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBROKER value to TRUE for SERVER
20:30:29,121 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBASE value to TRUE for SERVER
20:30:30,124 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer was started using the dm_launch_server_config_program.sh script.
20:30:30,124 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable DOCUMENTUM.
20:30:30,124 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - existingVersion : 25.4serverMajorversion : 25.4
20:30:33,125 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable PATH.
20:30:33,125 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - existingVersion : 25.4serverMajorversion : 25.4
20:30:36,126 INFO [main] - existingVersion : 25.4serverMajorversion : 25.4
20:30:36,136 INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentConfigurationInstallationValidation - Start to validate docbase parameters.
20:30:36,140 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerPatchExistingDocbaseAction - The installer will obtain all the DOCBASE on the machine.
20:30:38,146 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerDocAppFolder - The installer will obtain all the DocApps which could be installed for the repository.
20:30:38,148 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadDocBaseComponentInfo - The installer will gather information about the component GR_REPO.
20:30:41,151 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerReadServerIniForLockbox - Lockbox disabled for the repository : GR_REPO.
20:30:41,153 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeepAEKUnchanged - vaule of isVaultEnabledinPrevious : null
20:30:41,156 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - The installer will check old AEK key status.
20:30:41,219 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1
20:30:41,221 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - AEK key type provided in properties is : Local
20:30:41,266 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1
20:30:41,269 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - The installer will validate AEK fields.
20:30:41,272 INFO [main] - Is Vault enabled :false
20:30:41,273 INFO [main] - Is Vault enabled :false
20:30:41,326 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Installer will boot AEK key
20:31:11,376 INFO [main] - Is Vault enabled :false
20:31:11,377 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - The installer will check keystore status.
20:31:11,419 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1
20:31:11,419 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - The installer detected the keystore already exists and was created using user password.
20:31:11,425 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerQueryDatabaseInformation - The installer is gathering database connection information from the local machine.
20:31:11,427 INFO [main] com.documentum.install.appserver.services.DiAppServerUtil - appServer == null
20:31:11,427 INFO [main] com.documentum.install.appserver.services.DiAppServerUtil - isTomcatInstalled == true -- tomcat version is null
20:31:11,431 INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - setApplicationServer sharedDfcLibDir is:$DOCUMENTUM/dfc
20:31:11,431 INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - getFileFromResource for templates/appserver.properties
20:31:11,434 INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - Tomcat Home = $DOCUMENTUM/tomcat
20:31:11,438 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerModifyDocbaseDirectory - The installer will create the folder structure for repository GR_REPO.
20:31:11,440 INFO [main] - The installer will stop component process for GR_REPO.
20:31:11,479 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateTCSUnixServiceFile - The installer will check service entries for repository GR_REPO.
20:31:11,483 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerModifyDfcProperties - The installer will update dfc.properties file.
20:31:11,485 INFO [main] com.documentum.install.shared.common.services.dfc.DiDfcProperties - Installer is not adding connection broker information as it is already added.
20:31:13,488 INFO [main] - The installer will update server.ini file for the repository.
20:31:13,493 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerDataIniGenerator - The installer will create data_dictionary.ini for the repository.
20:31:13,496 INFO [main] - The installer will obtain database server name for database dctmdb.
20:31:13,497 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadServerWebcacheInfo - The installer will obtain database information of dctmdb.
20:31:13,498 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerWebCacheIniGenerator - The installer will update webcache.ini file for the repository.
20:31:13,503 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerTestDatabaseConnection4Docbase_Upgrade - The installer is testing the database connection information
20:31:13,503 INFO [main] com.documentum.install.server.common.services.db.DiServerDbSvrOracleServer - The installer is validating the database version is supported.
20:31:13,638 INFO [main] com.documentum.install.server.common.services.db.DiServerDbSvrOracleServer - The installer is validating the database connection information in the server.ini file.
20:31:13,910 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckIfDMSUpgraded - Check if upgrade of DMS tables is needed for current docbase.
20:31:13,911 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckIfDMSUpgraded - The current repository doesn't need to upgrade DMS table.
20:31:13,922 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateDocbaseServiceScript - The installer will update start script for repository GR_REPO.
20:31:13,929 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateDocbaseServiceScript - The installer will update stop script for repository GR_REPO.
20:31:13,937 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpgradeAEKUtility - will not execute start and stop services
20:31:13,944 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpgradeAEKUtility - will not execute start and stop services
20:31:13,947 INFO [main] - The installer will start component process for GR_REPO.
20:31:14,997 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:16,005 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:17,015 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:18,024 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:19,030 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:20,038 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:21,045 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:22,053 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
...
20:31:43,060 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:31:44,066 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
...
20:32:10,073 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
20:32:11,080 INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM/dba/log/GR_REPO.log
[dmadmin@cs-0 ~]$
3. Repository startup crash on DM_SERVER_E_SOCKOPT?
Everything looked fine at the beginning of the log file, at least until the start of the Repository process. After waiting a little less than one minute, there was still nothing happening, which was not normal. Therefore, I checked the OS processes and found none for the Repository “GR_REPO“:
[dmadmin@cs-0 ~]$ ps uxf | grep GR_REPO
dmadmin 2233289 0.0 0.0 3348 1824 pts/0 S+ 20:32 0:00 \_ grep --color=auto GR_REPO
[dmadmin@cs-0 ~]$
Therefore, something happened to the Repository process, which means that the upgrade process failed or will remain stuck in that loop. When checking the Repository log file, I saw the following:
[dmadmin@cs-0 dba]$ cat $DOCUMENTUM/dba/log/GR_REPO.log
OpenText Documentum Content Server (version 25.4.0000.0143 Linux64.Oracle)
Copyright (c) 2025. OpenText Corporation
All rights reserved.
2026-02-05T20:31:15.702051 2235323[2235323] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO attempting to open"
2026-02-05T20:31:15.802801 2235323[2235323] 0000000000000000 [DM_SERVER_I_START_KEY_STORAGE_MODE]info: "Docbase GR_REPO is using database for cryptographic key storage"
2026-02-05T20:31:15.802878 2235323[2235323] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO process identity: user(dmadmin)"
2026-02-05T20:31:16.073327 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Post Upgrade Processing."
2026-02-05T20:31:16.073843 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Base Types."
2026-02-05T20:31:16.074476 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmRecovery."
2026-02-05T20:31:16.089286 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmACL."
...
2026-02-05T20:31:17.886348 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Acs Config List."
2026-02-05T20:31:17.886487 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmLiteSysObject."
2026-02-05T20:31:17.886957 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmBatchManager."
2026-02-05T20:31:17.891417 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Partition Scheme."
2026-02-05T20:31:17.891883 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Critical Event Registry."
2026-02-05T20:31:17.891947 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Transaction Tracking Event Registry."
2026-02-05T20:31:17.892014 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Initialze External User Event Set."
2026-02-05T20:31:17.893580 2235323[2235323] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Authentication Plugins."
2026-02-05T20:31:17.895070 2235323[2235323] 0000000000000000 [DM_SESSION_I_AUTH_PLUGIN_LOADED]info: "Loaded Authentication Plugin with code 'dm_krb' ($DOCUMENTUM/dba/auth/libkerberos.so)."
2026-02-05T20:31:17.895090 2235323[2235323] 0000000000000000 [DM_SESSION_I_AUTH_PLUGIN_LOAD_INIT]info: "Authentication plugin ( 'dm_krb' ) was disabled. This is expected if no keytab file(s) at location ($DOCUMENTUM/dba/auth/kerberos).Please refer the content server installation guide."
2026-02-05T20:31:17.896397 2235323[2235323] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO opened"
2026-02-05T20:31:17.896463 2235323[2235323] 0000000000000000 [DM_SERVER_I_SERVER]info: "Setting exception handlers to catch all interrupts"
2026-02-05T20:31:17.896475 2235323[2235323] 0000000000000000 [DM_SERVER_I_START]info: "Starting server using service name: GR_REPO"
2026-02-05T20:31:17.933282 2235323[2235323] 0000000000000000 [DM_LICENSE_E_NO_LICENSE_CONFIG]error: "Could not find dm_otds_license_config object."
2026-02-05T20:31:17.998180 2235323[2235323] 0000000000000000 [DM_SERVER_I_LAUNCH_MTHDSVR]info: "Launching Method Server succeeded."
2026-02-05T20:31:17.999298 2235323[2235323] 0000000000000000 [DM_SERVER_E_SOCKOPT]error: "setsockopt failed for (SO_REUSEADDR (client)) with error (88)"
[dmadmin@cs-0 dba]$
4. Investigation of the DM_SERVER_E_SOCKOPT
The Repository log file was also quite clean. Everything at the beginning was as expected, until the very last line. The Repository was about to become available when suddenly a “DM_SERVER_E_SOCKOPT” error appeared and crashed the Repository process.
I tried to start the Repository again, but without success. It always ended up with the exact same error as the last line. It was my first time encountering that error “DM_SERVER_E_SOCKOPT“, so I checked the official documentation and the OpenText support website. But I had no luck there either; there was not a single reference to that error anywhere.
So, what should I do next? As usual, I just tried things that could make sense based on the information available.
The error refers to SOCKOPT, which I assumed meant socket options, so possibly something related to networking or communications. I checked the “setsockopt” documentation (c.f. this man page), which indeed seemed related to networking protocols. I also reviewed the “SO_REUSEADDR” documentation (c.f. this other man page), which refers to address binding apparently.
5. Fix & Resolution
With that in mind, I remembered the IPv4 versus IPv6 issue I encountered back in 2024 and the blog post I wrote about it (linked earlier). Since there was no issue starting the Connection Broker with the “host=${Current-IPv4}” setting, I focused on the Repository configuration.
Therefore, I tried disabling what I had added for 23.4 to work. Specifically, I commented out the line “#ip_mode = V4ONLY” in “server.ini” so that it would return to the default value:
[dmadmin@cs-0 ~]$ grep ip_mode $DOCUMENTUM/dba/config/GR_REPO/server.ini
ip_mode = V4ONLY
[dmadmin@cs-0 ~]$
[dmadmin@cs-0 ~]$ sed -i 's/^\(ip_mode\)/#\1/' $DOCUMENTUM/dba/config/GR_REPO/server.ini
[dmadmin@cs-0 ~]$
[dmadmin@cs-0 ~]$ grep ip_mode $DOCUMENTUM/dba/config/GR_REPO/server.ini
#ip_mode = V4ONLY
[dmadmin@cs-0 ~]$
Then I tried starting the Repository again:
[dmadmin@cs-0 ~]$ $DOCUMENTUM/dba/dm_start_GR_REPO
starting Documentum server for repository: [GR_REPO]
with server log: [$DOCUMENTUM/dba/log/GR_REPO.log]
server pid: 2268601
[dmadmin@cs-0 ~]$
[dmadmin@cs-0 ~]$ cat $DOCUMENTUM/dba/log/GR_REPO.log
OpenText Documentum Content Server (version 25.4.0000.0143 Linux64.Oracle)
Copyright (c) 2025. OpenText Corporation
All rights reserved.
2026-02-05T20:57:34.417095 2268601[2268601] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO attempting to open"
2026-02-05T20:57:34.517792 2268601[2268601] 0000000000000000 [DM_SERVER_I_START_KEY_STORAGE_MODE]info: "Docbase GR_REPO is using database for cryptographic key storage"
2026-02-05T20:57:34.517854 2268601[2268601] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO process identity: user(dmadmin)"
2026-02-05T20:57:34.750986 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Post Upgrade Processing."
2026-02-05T20:57:34.751390 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Base Types."
2026-02-05T20:57:34.751810 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmRecovery."
2026-02-05T20:57:34.763115 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmACL."
...
2026-02-05T20:57:35.977776 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Acs Config List."
2026-02-05T20:57:35.977873 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmLiteSysObject."
2026-02-05T20:57:35.978265 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize dmBatchManager."
2026-02-05T20:57:35.981015 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Partition Scheme."
2026-02-05T20:57:35.981417 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Critical Event Registry."
2026-02-05T20:57:35.981479 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Transaction Tracking Event Registry."
2026-02-05T20:57:35.981543 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Initialze External User Event Set."
2026-02-05T20:57:35.983046 2268601[2268601] 0000000000000000 [DM_SESSION_I_INIT_BEGIN]info: "Initialize Authentication Plugins."
2026-02-05T20:57:35.984583 2268601[2268601] 0000000000000000 [DM_SESSION_I_AUTH_PLUGIN_LOADED]info: "Loaded Authentication Plugin with code 'dm_krb' ($DOCUMENTUM/dba/auth/libkerberos.so)."
2026-02-05T20:57:35.984604 2268601[2268601] 0000000000000000 [DM_SESSION_I_AUTH_PLUGIN_LOAD_INIT]info: "Authentication plugin ( 'dm_krb' ) was disabled. This is expected if no keytab file(s) at location ($DOCUMENTUM/dba/auth/kerberos).Please refer the content server installation guide."
2026-02-05T20:57:35.986125 2268601[2268601] 0000000000000000 [DM_SERVER_I_START_SERVER]info: "Docbase GR_REPO opened"
2026-02-05T20:57:35.986189 2268601[2268601] 0000000000000000 [DM_SERVER_I_SERVER]info: "Setting exception handlers to catch all interrupts"
2026-02-05T20:57:35.986199 2268601[2268601] 0000000000000000 [DM_SERVER_I_START]info: "Starting server using service name: GR_REPO"
2026-02-05T20:57:36.016709 2268601[2268601] 0000000000000000 [DM_LICENSE_E_NO_LICENSE_CONFIG]error: "Could not find dm_otds_license_config object."
2026-02-05T20:57:36.067861 2268601[2268601] 0000000000000000 [DM_SERVER_I_LAUNCH_MTHDSVR]info: "Launching Method Server succeeded."
2026-02-05T20:57:36.073641 2268601[2268601] 0000000000000000 [DM_SERVER_I_LISTENING]info: "The server is listening on network address (Service Name: GR_REPO, Host Name: cs-0 :V4 IP)"
2026-02-05T20:57:36.082139 2268601[2268601] 0000000000000000 [DM_SERVER_I_LISTENING]info: "The server is listening on network address (Service Name: GR_REPO_s, Host Name: cs-0 :V4 IP)"
2026-02-05T20:57:37.135498 2268601[2268601] 0000000000000000 [DM_WORKFLOW_I_AGENT_START]info: "Workflow agent master (pid : 2268748, session 0101234580000007) is started sucessfully."
IsProcessAlive: Process ID 0 is not > 0
2026-02-05T20:57:37.136533 2268601[2268601] 0000000000000000 [DM_WORKFLOW_I_AGENT_START]info: "Workflow agent worker (pid : 2268749, session 010123458000000a) is started sucessfully."
IsProcessAlive: Process ID 0 is not > 0
2026-02-05T20:57:38.137780 2268601[2268601] 0000000000000000 [DM_WORKFLOW_I_AGENT_START]info: "Workflow agent worker (pid : 2268770, session 010123458000000b) is started sucessfully."
IsProcessAlive: Process ID 0 is not > 0
2026-02-05T20:57:39.139572 2268601[2268601] 0000000000000000 [DM_WORKFLOW_I_AGENT_START]info: "Workflow agent worker (pid : 2268823, session 010123458000000c) is started sucessfully."
2026-02-05T20:57:40.139741 2268601[2268601] 0000000000000000 [DM_SERVER_I_START]info: "Sending Initial Docbroker check-point "
2026-02-05T20:57:40.143121 2268601[2268601] 0000000000000000 [DM_MQ_I_DAEMON_START]info: "Message queue daemon (pid : 2268845, session 0101234580000456) is started sucessfully."
2026-02-05T20:57:42.758073 2268844[2268844] 0101234580000003 [DM_DOCBROKER_I_PROJECTING]info: "Sending information to Docbroker located on host (cs-0.cs.dctm-ns.svc.cluster.local) with port (1490). Information: (Config(GR_REPO), Proximity(1), Status(Open), Dormancy Status(Active))."
[dmadmin@cs-0 ~]$
As you can see, it is working again. This means that what I previously had to add for the 23.4 environment to work is now causing an issue on 25.4. Obviously the OS is not the same (both the container and the real host), and the Kubernetes environment is also different. Still, it is interesting that something fixing an issue in a specific version can introduce a problem in a newer version.
As shown in the logs, the Repository still starts on IPv4, as it clearly states: “The server is listening on network address (Service Name: GR_REPO, Host Name: cs-0 :V4 IP)“. However, it does not accept the setting “ip_mode = V4ONLY“, somehow.
That’s pretty incredible, don’t you think? Anyway, once the Repository processes were running, I was able to restart the upgrade process properly by ensuring that ip_mode was not specified for version 25.4.
![Thumbnail [60x60]](https://www.dbi-services.com/blog/wp-content/uploads/2022/08/MOP_web-min-scaled.jpg)
![Thumbnail [90x90]](https://www.dbi-services.com/blog/wp-content/uploads/2022/08/GME_web-min-scaled.jpg)