{"id":43385,"date":"2026-03-07T12:43:02","date_gmt":"2026-03-07T11:43:02","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=43385"},"modified":"2026-03-07T12:46:02","modified_gmt":"2026-03-07T11:46:02","slug":"dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/","title":{"rendered":"Dctm – Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT"},"content":{"rendered":"\n

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<\/a>).<\/p>\n\n\n\n

1. Environment details<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

At the Documentum level, the Connection Broker was configured with “host=${Current-IPv4}<\/strong><\/em>” to force it to start with IPv4 only. The Repository had “ip_mode = V4ONLY<\/strong><\/em>” in its “server.ini<\/strong><\/em>” 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.<\/p>\n\n\n\n

2. Upgrade to Documentum 25.4<\/h2>\n\n\n\n

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.<\/p>\n\n\n\n

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:<\/p>\n\n\n

\n[dmadmin@cs-0 ~]$ cat $DM_HOME\/install\/logs\/install.log\n20:30:29,056  INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - Log is ready and is set to the level - INFO\n20:30:29,060  INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product name is: UniversalServerConfigurator\n20:30:29,060  INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - The product version is: 25.4.0000.0143\n20:30:29,060  INFO [main]  -\n20:30:29,089  INFO [main] com.documentum.install.shared.installanywhere.actions.InitializeSharedLibrary - Done InitializeSharedLibrary ...\n20:30:29,117  INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentCheckVaultStatus - Checking the vault status: Silent mode\n20:30:29,117  INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentCheckVaultStatus - Checking whether vault enabled or not\n20:30:29,121  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBROKER value to TRUE for SERVER\n20:30:29,121  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerInformation - Setting CONFIGURE_DOCBASE value to TRUE for SERVER\n20: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.\n20:30:30,124  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable DOCUMENTUM.\n20:30:30,124  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - existingVersion : 25.4serverMajorversion : 25.4\n20:30:33,125  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - The installer will determine the value of environment variable PATH.\n20:30:33,125  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckEnvrionmentVariable - existingVersion : 25.4serverMajorversion : 25.4\n20:30:36,126  INFO [main]  - existingVersion : 25.4serverMajorversion : 25.4\n20:30:36,136  INFO [main] com.documentum.install.server.installanywhere.actions.DiWASilentConfigurationInstallationValidation - Start to validate docbase parameters.\n20:30:36,140  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerPatchExistingDocbaseAction - The installer will obtain all the DOCBASE on the machine.\n20: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.\n20:30:38,148  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadDocBaseComponentInfo - The installer will gather information about the component GR_REPO.\n20:30:41,151  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerReadServerIniForLockbox - Lockbox disabled for the repository : GR_REPO.\n20:30:41,153  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeepAEKUnchanged - vaule of isVaultEnabledinPrevious : null\n20:30:41,156  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatusForOld - The installer will check old AEK key status.\n20:30:41,219  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1\n20:30:41,221  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadValidAEKs - AEK key type provided in properties is  : Local\n20:30:41,266  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1\n20:30:41,269  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerEnableLockBoxValidation - The installer will validate AEK fields.\n20:30:41,272  INFO [main]  - Is Vault enabled :false\n20:30:41,273  INFO [main]  - Is Vault enabled :false\n20:30:41,326  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerValidateLockboxPassphrase - Installer will boot AEK key\n20:31:11,376  INFO [main]  - Is Vault enabled :false\n20:31:11,377  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - The installer will check keystore status.\n20:31:11,419  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckKeystoreStatus - Executed dm_crypto_create -check command and the return code - 1\n20: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.\n20:31:11,425  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerQueryDatabaseInformation - The installer is gathering database connection information from the local machine.\n20:31:11,427  INFO [main] com.documentum.install.appserver.services.DiAppServerUtil - appServer == null\n20:31:11,427  INFO [main] com.documentum.install.appserver.services.DiAppServerUtil - isTomcatInstalled == true -- tomcat version is null\n20:31:11,431  INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - setApplicationServer sharedDfcLibDir is:$DOCUMENTUM\/dfc\n20:31:11,431  INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - getFileFromResource for templates\/appserver.properties\n20:31:11,434  INFO [main] com.documentum.install.appserver.tomcat.TomcatApplicationServer - Tomcat Home = $DOCUMENTUM\/tomcat\n20:31:11,438  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerModifyDocbaseDirectory - The installer will create the folder structure for repository GR_REPO.\n20:31:11,440  INFO [main]  - The installer will stop component process for GR_REPO.\n20:31:11,479  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateTCSUnixServiceFile - The installer will check service entries for repository GR_REPO.\n20:31:11,483  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerModifyDfcProperties - The installer will update dfc.properties file.\n20: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.\n20:31:13,488  INFO [main]  - The installer will update server.ini file for the repository.\n20:31:13,493  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerDataIniGenerator - The installer will create data_dictionary.ini for the repository.\n20:31:13,496  INFO [main]  - The installer will obtain database server name for database dctmdb.\n20:31:13,497  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerLoadServerWebcacheInfo - The installer will obtain database information of dctmdb.\n20:31:13,498  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerWebCacheIniGenerator - The installer will update webcache.ini file for the repository.\n20:31:13,503  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerTestDatabaseConnection4Docbase_Upgrade - The installer is testing the database connection information\n20:31:13,503  INFO [main] com.documentum.install.server.common.services.db.DiServerDbSvrOracleServer - The installer is validating the database version is supported.\n20: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.\n20:31:13,910  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckIfDMSUpgraded - Check if upgrade of DMS tables is needed for current docbase.\n20:31:13,911  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerCheckIfDMSUpgraded - The current repository doesn't need to upgrade DMS table.\n20:31:13,922  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateDocbaseServiceScript - The installer will update start script for  repository GR_REPO.\n20:31:13,929  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpdateDocbaseServiceScript - The installer will update stop script for  repository GR_REPO.\n20:31:13,937  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpgradeAEKUtility - will not execute start and stop services\n20:31:13,944  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAServerUpgradeAEKUtility - will not execute start and stop services\n20:31:13,947  INFO [main]  - The installer will start component process for GR_REPO.\n20:31:14,997  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:16,005  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:17,015  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:18,024  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:19,030  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:20,038  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:21,045  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:22,053  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n...\n20:31:43,060  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:31:44,066  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n...\n20:32:10,073  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n20:32:11,080  INFO [main] com.documentum.install.server.installanywhere.actions.DiWAUnixServiceControl - logPath is $DOCUMENTUM\/dba\/log\/GR_REPO.log\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
3. Repository startup crash on DM_SERVER_E_SOCKOPT?<\/h2>\n\n\n\n
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<\/strong><\/em>“:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ ps uxf | grep GR_REPO\ndmadmin  2233289  0.0  0.0   3348  1824 pts\/0    S+   20:32   0:00  \\_ grep --color=auto GR_REPO\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
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:<\/p>\n\n\n
\n[dmadmin@cs-0 dba]$ cat $DOCUMENTUM\/dba\/log\/GR_REPO.log\n\n    OpenText Documentum Content Server (version 25.4.0000.0143 Linux64.Oracle)\n    Copyright (c) 2025. OpenText Corporation\n    All rights reserved.\n\n2026-02-05T20:31:15.702051\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO attempting to open"\n\n2026-02-05T20:31:15.802801\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_START_KEY_STORAGE_MODE]info:  "Docbase GR_REPO is using database for cryptographic key storage"\n\n2026-02-05T20:31:15.802878\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO process identity: user(dmadmin)"\n\n2026-02-05T20:31:16.073327\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Post Upgrade Processing."\n\n2026-02-05T20:31:16.073843\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Base Types."\n\n2026-02-05T20:31:16.074476\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmRecovery."\n\n2026-02-05T20:31:16.089286\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmACL."\n\n...\n\n2026-02-05T20:31:17.886348\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Acs Config List."\n\n2026-02-05T20:31:17.886487\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmLiteSysObject."\n\n2026-02-05T20:31:17.886957\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmBatchManager."\n\n2026-02-05T20:31:17.891417\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Partition Scheme."\n\n2026-02-05T20:31:17.891883\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Critical Event Registry."\n\n2026-02-05T20:31:17.891947\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Transaction Tracking Event Registry."\n\n2026-02-05T20:31:17.892014\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Initialze External User Event Set."\n\n2026-02-05T20:31:17.893580\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Authentication Plugins."\n\n2026-02-05T20:31:17.895070\t2235323[2235323]\t0000000000000000\t[DM_SESSION_I_AUTH_PLUGIN_LOADED]info:  "Loaded Authentication Plugin with code 'dm_krb' ($DOCUMENTUM\/dba\/auth\/libkerberos.so)."\n\n2026-02-05T20:31:17.895090\t2235323[2235323]\t0000000000000000\t[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."\n\n2026-02-05T20:31:17.896397\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO opened"\n\n2026-02-05T20:31:17.896463\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_SERVER]info:  "Setting exception handlers to catch all interrupts"\n\n2026-02-05T20:31:17.896475\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_START]info:  "Starting server using service name:  GR_REPO"\n\n2026-02-05T20:31:17.933282\t2235323[2235323]\t0000000000000000\t[DM_LICENSE_E_NO_LICENSE_CONFIG]error:  "Could not find dm_otds_license_config object."\n\n2026-02-05T20:31:17.998180\t2235323[2235323]\t0000000000000000\t[DM_SERVER_I_LAUNCH_MTHDSVR]info:  "Launching Method Server succeeded."\n\n2026-02-05T20:31:17.999298\t2235323[2235323]\t0000000000000000\t[DM_SERVER_E_SOCKOPT]error:  "setsockopt failed for (SO_REUSEADDR (client)) with error (88)"\n\n[dmadmin@cs-0 dba]$\n<\/pre><\/div>\n\n\n
4. Investigation of the DM_SERVER_E_SOCKOPT<\/h2>\n\n\n\n
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<\/strong><\/em>” error appeared and crashed the Repository process.<\/p>\n\n\n\n
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<\/strong><\/em>“, 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.<\/p>\n\n\n\n
So, what should I do next? As usual, I just tried things that could make sense based on the information available.<\/p>\n\n\n\n
The error refers to SOCKOPT<\/strong><\/em>, which I assumed meant socket options, so possibly something related to networking or communications. I checked the “setsockopt<\/strong><\/em>” documentation (c.f. this man page<\/a>), which indeed seemed related to networking protocols. I also reviewed the “SO_REUSEADDR<\/strong><\/em>” documentation (c.f. this other man page<\/a>), which refers to address binding apparently.<\/p>\n\n\n\n
5. Fix & Resolution<\/h2>\n\n\n\n
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}<\/strong><\/em>” setting, I focused on the Repository configuration.<\/p>\n\n\n\n
Therefore, I tried disabling what I had added for 23.4 to work. Specifically, I commented out the line “#ip_mode = V4ONLY<\/strong><\/em>” in “server.ini<\/strong><\/em>” so that it would return to the default value:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ grep ip_mode $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\nip_mode = V4ONLY\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ sed -i 's\/^\\(ip_mode\\)\/#\\1\/' $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ grep ip_mode $DOCUMENTUM\/dba\/config\/GR_REPO\/server.ini\n#ip_mode = V4ONLY\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
Then I tried starting the Repository again:<\/p>\n\n\n
\n[dmadmin@cs-0 ~]$ $DOCUMENTUM\/dba\/dm_start_GR_REPO\nstarting Documentum server for repository: [GR_REPO]\nwith server log: [$DOCUMENTUM\/dba\/log\/GR_REPO.log]\nserver pid: 2268601\n[dmadmin@cs-0 ~]$\n[dmadmin@cs-0 ~]$ cat $DOCUMENTUM\/dba\/log\/GR_REPO.log\n\n    OpenText Documentum Content Server (version 25.4.0000.0143 Linux64.Oracle)\n    Copyright (c) 2025. OpenText Corporation\n    All rights reserved.\n\n2026-02-05T20:57:34.417095\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO attempting to open"\n\n2026-02-05T20:57:34.517792\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START_KEY_STORAGE_MODE]info:  "Docbase GR_REPO is using database for cryptographic key storage"\n\n2026-02-05T20:57:34.517854\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO process identity: user(dmadmin)"\n\n2026-02-05T20:57:34.750986\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Post Upgrade Processing."\n\n2026-02-05T20:57:34.751390\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Base Types."\n\n2026-02-05T20:57:34.751810\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmRecovery."\n\n2026-02-05T20:57:34.763115\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmACL."\n\n...\n\n2026-02-05T20:57:35.977776\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Acs Config List."\n\n2026-02-05T20:57:35.977873\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmLiteSysObject."\n\n2026-02-05T20:57:35.978265\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize dmBatchManager."\n\n2026-02-05T20:57:35.981015\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Partition Scheme."\n\n2026-02-05T20:57:35.981417\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Critical Event Registry."\n\n2026-02-05T20:57:35.981479\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Transaction Tracking Event Registry."\n\n2026-02-05T20:57:35.981543\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Initialze External User Event Set."\n\n2026-02-05T20:57:35.983046\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_INIT_BEGIN]info:  "Initialize Authentication Plugins."\n\n2026-02-05T20:57:35.984583\t2268601[2268601]\t0000000000000000\t[DM_SESSION_I_AUTH_PLUGIN_LOADED]info:  "Loaded Authentication Plugin with code 'dm_krb' ($DOCUMENTUM\/dba\/auth\/libkerberos.so)."\n\n2026-02-05T20:57:35.984604\t2268601[2268601]\t0000000000000000\t[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."\n\n2026-02-05T20:57:35.986125\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START_SERVER]info:  "Docbase GR_REPO opened"\n\n2026-02-05T20:57:35.986189\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_SERVER]info:  "Setting exception handlers to catch all interrupts"\n\n2026-02-05T20:57:35.986199\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START]info:  "Starting server using service name:  GR_REPO"\n\n2026-02-05T20:57:36.016709\t2268601[2268601]\t0000000000000000\t[DM_LICENSE_E_NO_LICENSE_CONFIG]error:  "Could not find dm_otds_license_config object."\n\n2026-02-05T20:57:36.067861\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_LAUNCH_MTHDSVR]info:  "Launching Method Server succeeded."\n\n2026-02-05T20:57:36.073641\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: GR_REPO, Host Name: cs-0 :V4 IP)"\n\n2026-02-05T20:57:36.082139\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_LISTENING]info:  "The server is listening on network address (Service Name: GR_REPO_s, Host Name: cs-0 :V4 IP)"\n\n2026-02-05T20:57:37.135498\t2268601[2268601]\t0000000000000000\t[DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent master (pid : 2268748, session 0101234580000007) is started sucessfully."\nIsProcessAlive: Process ID 0 is not > 0\n2026-02-05T20:57:37.136533\t2268601[2268601]\t0000000000000000\t[DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (pid : 2268749, session 010123458000000a) is started sucessfully."\nIsProcessAlive: Process ID 0 is not > 0\n2026-02-05T20:57:38.137780\t2268601[2268601]\t0000000000000000\t[DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (pid : 2268770, session 010123458000000b) is started sucessfully."\nIsProcessAlive: Process ID 0 is not > 0\n2026-02-05T20:57:39.139572\t2268601[2268601]\t0000000000000000\t[DM_WORKFLOW_I_AGENT_START]info:  "Workflow agent worker (pid : 2268823, session 010123458000000c) is started sucessfully."\n2026-02-05T20:57:40.139741\t2268601[2268601]\t0000000000000000\t[DM_SERVER_I_START]info:  "Sending Initial Docbroker check-point "\n\n2026-02-05T20:57:40.143121\t2268601[2268601]\t0000000000000000\t[DM_MQ_I_DAEMON_START]info:  "Message queue daemon (pid : 2268845, session 0101234580000456) is started sucessfully."\n2026-02-05T20:57:42.758073\t2268844[2268844]\t0101234580000003\t[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))."\n[dmadmin@cs-0 ~]$\n<\/pre><\/div>\n\n\n
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.<\/p>\n\n\n\n
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)<\/strong><\/em>“. However, it does not accept the setting “ip_mode = V4ONLY<\/strong><\/em>“, somehow.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
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 […]<\/p>\n","protected":false},"author":20,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[525],"tags":[3889,3890,3891,2609,1760,3892,2601],"type_dbi":[],"class_list":["post-43385","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-23-4","tag-25-4","tag-dm_server_e_sockopt","tag-documentum-2","tag-repository","tag-sockopt","tag-upgrade-2"],"acf":[],"yoast_head":"\nDctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT - dbi Blog<\/title>\n<meta name=\"description\" content=\"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter "ip_mode = V4ONLY" is set\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Dctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT\" \/>\n<meta property=\"og:description\" content=\"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter "ip_mode = V4ONLY" is set\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-03-07T11:43:02+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-07T11:46:02+00:00\" \/>\n<meta name=\"author\" content=\"Morgan Patou\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@MorganPatou\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Morgan Patou\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Dctm – Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT\",\"datePublished\":\"2026-03-07T11:43:02+00:00\",\"dateModified\":\"2026-03-07T11:46:02+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\"},\"wordCount\":815,\"commentCount\":0,\"keywords\":[\"23.4\",\"25.4\",\"DM_SERVER_E_SOCKOPT\",\"Documentum\",\"repository\",\"SOCKOPT\",\"upgrade\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\",\"name\":\"Dctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2026-03-07T11:43:02+00:00\",\"dateModified\":\"2026-03-07T11:46:02+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"description\":\"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter \\\"ip_mode = V4ONLY\\\" is set\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Dctm – Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8\",\"name\":\"Morgan Patou\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g\",\"caption\":\"Morgan Patou\"},\"description\":\"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.\",\"sameAs\":[\"https:\/\/blog.dbi-services.com\/author\/morgan-patou\/\",\"https:\/\/x.com\/MorganPatou\"],\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Dctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT - dbi Blog","description":"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter \"ip_mode = V4ONLY\" is set","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/","og_locale":"en_US","og_type":"article","og_title":"Dctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT","og_description":"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter \"ip_mode = V4ONLY\" is set","og_url":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/","og_site_name":"dbi Blog","article_published_time":"2026-03-07T11:43:02+00:00","article_modified_time":"2026-03-07T11:46:02+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Dctm – Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT","datePublished":"2026-03-07T11:43:02+00:00","dateModified":"2026-03-07T11:46:02+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/"},"wordCount":815,"commentCount":0,"keywords":["23.4","25.4","DM_SERVER_E_SOCKOPT","Documentum","repository","SOCKOPT","upgrade"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/","url":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/","name":"Dctm - Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2026-03-07T11:43:02+00:00","dateModified":"2026-03-07T11:46:02+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"description":"Upgrading a Documentum Repository from 23.4 to 25.4 may fail with the error DM_SERVER_E_SOCKOPT if the parameter \"ip_mode = V4ONLY\" is set","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dctm-upgrade-from-23-4-to-25-4-fails-with-dm_server_e_sockopt\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Dctm – Upgrade from 23.4 to 25.4 fails with DM_SERVER_E_SOCKOPT"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8","name":"Morgan Patou","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5d7f5bec8b597db68a09107a6f5309e3870d6296ef94fb10ead4b09454ca67e5?s=96&d=mm&r=g","caption":"Morgan Patou"},"description":"Morgan Patou has over 12 years of experience in Enterprise Content Management (ECM) systems, with a strong focus in recent years on platforms such as Alfresco, Documentum, and M-Files. He specializes in the architecture, setup, customization, and maintenance of ECM infrastructures in complex & critical environments. Morgan is well-versed in both engineering and operations aspects, including high availability design, system integration, and lifecycle management. He also has a solid foundation in open-source and proprietary technologies - ranging from Apache, OpenLDAP or Kerberos to enterprise-grade systems like WebLogic. Morgan Patou holds an Engineering Degree in Computer Science from ENSISA (\u00c9cole Nationale Sup\u00e9rieure d'Ing\u00e9nieurs Sud Alsace) in Mulhouse, France. He is Alfresco Content Services Certified Administrator (ACSCA), Alfresco Content Services Certified Engineer (ACSCE) as well as OpenText Documentum Certified Administrator. His industry experience spans the Public Sector, IT Services, Financial Services\/Banking, and the Pharmaceutical industry.","sameAs":["https:\/\/blog.dbi-services.com\/author\/morgan-patou\/","https:\/\/x.com\/MorganPatou"],"url":"https:\/\/www.dbi-services.com\/blog\/author\/morgan-patou\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43385","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/20"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=43385"}],"version-history":[{"count":5,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43385\/revisions"}],"predecessor-version":[{"id":43391,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/43385\/revisions\/43391"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=43385"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=43385"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=43385"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=43385"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}