{"id":35265,"date":"2024-10-15T19:45:00","date_gmt":"2024-10-15T17:45:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/?p=35265"},"modified":"2024-10-15T17:37:16","modified_gmt":"2024-10-15T15:37:16","slug":"documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/","title":{"rendered":"Documentum – xPlore Dsearch not starting with a stuck rebuild"},"content":{"rendered":"\n

I recently faced another interesting issue (c.f. this one<\/a>) with Documentum xPlore where the Dsearch would refuse to start because of a stuck online rebuild. It happened on a Kubernetes environment using custom images we built (for security and scalability). The K8s Nodes were split across two DataCenters for DR reasons. However, one of the DataCenter had an important issue which caused all VMs running there to freeze and become unresponsive. Some Documentum pods were “running” on these VMs, at that point in time. While putting these K8s Nodes offline, the pods were properly rescheduled on the other DataCenter. However, post that operation, one specific Dsearch pod couldn’t start anymore. This Documentum environment has two xPlore Federations, each containing one Dsearch (with embedded local CPS), one IndexAgent and two CPS-Only pods (so four xPlore pods per Federation). All pods were up&running properly, except for that particular Dsearch.<\/p>\n\n\n\n

The startup logs of the Dsearch were as follow:<\/p>\n\n\n

\n[xplore@ds1-0 ~]$ cdlogPrimaryDsearch\n[xplore@ds1-0 logs]$ ls -ltr\ntotal 108\n-rw-r----- 1 xplore xplore     0 Oct 14 07:20 rest.log\n-rw-r----- 1 xplore xplore   139 Oct 14 07:20 dsearchadminweb.log\n-rw-r----- 1 xplore xplore 37722 Oct 14 07:21 cps_daemon.log\n-rw-r----- 1 xplore xplore  1353 Oct 14 07:21 cps.log\n-rw-r----- 1 xplore xplore  3218 Oct 14 07:21 xdb.log\n-rw-r----- 1 xplore xplore  7445 Oct 14 07:21 dfc.log\n-rw-r----- 1 xplore xplore 39287 Oct 14 07:21 dsearch.log\n[xplore@ds1-0 logs]$\n[xplore@ds1-0 logs]$ grep ERROR *\ndfc.log:2024-10-14 07:21:18,279 ERROR [default task-1] io.undertow.servlet.request - UT015002: Stopping servlet IndexServerServlet due to permanent unavailability\ndsearch.log:2024-10-14 07:21:09,858 ERROR [ServerService Thread Pool -- 76] c.e.d.c.f.i.core.collection.ESSCollection - Failed to create index on library REPO_NAME\/dsearch\/Data\/col1.\ndsearch.log:2024-10-14 07:21:09,860 ERROR [ServerService Thread Pool -- 76] c.e.d.core.fulltext.webapp.IndexServerServlet - Failed to start\ndsearch.log:2024-10-14 07:21:18,278 ERROR [default task-1] c.e.d.core.fulltext.webapp.IndexServerServlet - Failed to start\ndsearch.log:2024-10-14 07:21:45,963 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\ndsearch.log:2024-10-14 07:21:45,966 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\ndsearch.log:2024-10-14 07:21:45,968 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\ndsearch.log:2024-10-14 07:21:45,968 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\ndsearch.log:2024-10-14 07:21:45,970 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\n[xplore@ds1-0 logs]$\n[xplore@ds1-0 logs]$ cat dsearch.log\n2024-10-14 07:20:59,035 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.core.ESSNode - Starting xPlore\n2024-10-14 07:20:59,044 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.core.ESSContext - Initializing xPlore instance\n2024-10-14 07:20:59,062 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initializing xDB federation and database\n2024-10-14 07:21:00,265 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveSchemaHandler - Not loading configuration from file system, revision 1.29 equal to xDB revision of indexserverconfig.xml\n2024-10-14 07:21:00,725 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.indexserver.core.ESSActiveNodesRegistry - Register instance PrimaryDsearch\n2024-10-14 07:21:00,726 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Starting xDB for instance primary\n2024-10-14 07:21:00,967 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initialize xDB driver to local driver with cache pages: 524288 and Socket timeout :1000 ms\n2024-10-14 07:21:01,153 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - XDB is listening at 9330 successfully\n2024-10-14 07:21:01,253 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initialize xDB driver to remote driver with cache pages: 524288 and Socket timeout :1000 ms\n2024-10-14 07:21:01,253 INFO [ServerService Thread Pool -- 76] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - The XML database server is started successfully. {xDB version=xDB 10_7@4558357}\n2024-10-14 07:21:01,261 DEBUG [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (local)  with connection 3\n2024-10-14 07:21:08,559 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a local Content Processing Service with version [20.2.0000.0015].\n2024-10-14 07:21:08,630 DEBUG [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (https:\/\/cps1-0.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl)  with connection 3\n2024-10-14 07:21:09,077 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a remote Content Processing Service [https:\/\/cps1-0.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl] with version [20.2.0000.0015].\n2024-10-14 07:21:09,244 DEBUG [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (https:\/\/cps1-1.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl)  with connection 3\n2024-10-14 07:21:09,437 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a remote Content Processing Service [https:\/\/cps1-1.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl] with version [20.2.0000.0015].\n2024-10-14 07:21:09,626 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.core.ESSContext - Initialize domain SystemData\n2024-10-14 07:21:09,706 INFO [ServerService Thread Pool -- 76] c.e.d.core.fulltext.indexserver.core.ESSContext - Initialize domain REPO_NAME\n2024-10-14 07:21:09,858 ERROR [ServerService Thread Pool -- 76] c.e.d.c.f.i.core.collection.ESSCollection - Failed to create index on library REPO_NAME\/dsearch\/Data\/col1.\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ReindexStatus.reset(ReindexStatus.java:68)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.addLMPIReindexTaskIfNecessary(ESSCollection.java:2766)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.createIndexes(ESSCollection.java:2824)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.initIndex(ESSCollection.java:2665)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.init(ESSCollection.java:2347)\n        ...\n2024-10-14 07:21:09,860 ERROR [ServerService Thread Pool -- 76] c.e.d.core.fulltext.webapp.IndexServerServlet - Failed to start\ncom.emc.documentum.core.fulltext.common.exception.IndexServerRuntimeException: com.emc.documentum.core.fulltext.common.exception.IndexServerException: Failed to create index on library REPO_NAME\/dsearch\/Data\/col1.\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSContext.initialize(ESSContext.java:261)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSNode.startUp(ESSNode.java:67)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.webapp.IndexServerServlet.init(IndexServerServlet.java:48)\n        at io.undertow.servlet@2.0.21.Final\/\/io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)\n        ...\nCaused by: com.emc.documentum.core.fulltext.common.exception.IndexServerException: Failed to create index on library REPO_NAME\/dsearch\/Data\/col1.\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.createIndexes(ESSCollection.java:2864)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.initIndex(ESSCollection.java:2665)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.init(ESSCollection.java:2347)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.<init>(ESSCollection.java:145)\n        ...\nCaused by: java.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ReindexStatus.reset(ReindexStatus.java:68)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.addLMPIReindexTaskIfNecessary(ESSCollection.java:2766)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.createIndexes(ESSCollection.java:2824)\n        ... 34 common frames omitted\n2024-10-14 07:21:09,861 INFO [Index-Rebuilder-col1-0] c.e.d.c.f.i.core.collection.ESSCollection - Rebuilding index [dmftdoc] for collection [col1].\n2024-10-14 07:21:09,863 INFO [Index-Rebuilder-col1-0] c.e.d.c.f.i.core.collection.ESSCollection - Rebuild index dmftdoc with non-blocking mode.\n2024-10-14 07:21:18,256 INFO [default task-1] c.e.d.core.fulltext.indexserver.core.ESSNode - Starting xPlore\n2024-10-14 07:21:18,256 INFO [default task-1] c.e.d.core.fulltext.indexserver.core.ESSContext - Initializing xPlore instance\n2024-10-14 07:21:18,276 INFO [default task-1] c.e.d.c.f.indexserver.core.ESSActiveNodesRegistry - Register instance PrimaryDsearch\n2024-10-14 07:21:18,276 INFO [default task-1] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Starting xDB for instance primary\n2024-10-14 07:21:18,278 ERROR [default task-1] c.e.d.core.fulltext.webapp.IndexServerServlet - Failed to start\ncom.emc.documentum.core.fulltext.common.exception.IndexServerRuntimeException: com.emc.documentum.core.fulltext.common.exception.EngineException: Failed to start xDB socket listener\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSContext.initialize(ESSContext.java:261)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSNode.startUp(ESSNode.java:67)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.webapp.IndexServerServlet.init(IndexServerServlet.java:48)\n        at io.undertow.servlet@2.0.21.Final\/\/io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)\n        ...\nCaused by: com.emc.documentum.core.fulltext.common.exception.EngineException: Failed to start xDB socket listener\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.engine.xhive.impl.XhiveManager.startDatabase(XhiveManager.java:646)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSContext.startDatabase(ESSContext.java:187)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.ESSContext.initialize(ESSContext.java:237)\n        ... 49 common frames omitted\nCaused by: java.net.BindException: Address already in use (Bind failed)\n        at java.base\/java.net.PlainSocketImpl.socketBind(Native Method)\n        ...\n2024-10-14 07:21:45,963 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.ESSIndexHelper.getObjectCategoryConfig(ESSIndexHelper.java:97)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.ESSIndexHelper.shouldCheckObjectVersion(ESSIndexHelper.java:115)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.FtIndexObject.<init>(FtIndexObject.java:71)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.callCPSPlugin(ESSXMLNodeHandler.java:379)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.enter(ESSXMLNodeHandler.java:123)\n        at deployment.dsearch.war\/\/com.xhive.xDB_10_7_r4558357.ch$b.c(xdb:617)\n        ...\n2024-10-14 07:21:45,966 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.prepareDomDocument(ESSXMLNodeHandler.java:304)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.callCPSPlugin(ESSXMLNodeHandler.java:350)\n        ...\n2024-10-14 07:21:45,968 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.prepareDomDocument(ESSXMLNodeHandler.java:304)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.callCPSPlugin(ESSXMLNodeHandler.java:350)\n        ...\n2024-10-14 07:21:45,968 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.prepareDomDocument(ESSXMLNodeHandler.java:304)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.callCPSPlugin(ESSXMLNodeHandler.java:350)\n        ...\n2024-10-14 07:21:45,970 ERROR [Index-Rebuilder-col1-0-Worker-0] c.e.d.c.f.i.core.index.xhive.ESSXMLNodeHandler - Failed to handle 090f123480096bde\njava.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.ESSIndexHelper.getObjectCategoryConfig(ESSIndexHelper.java:97)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.ESSIndexHelper.shouldCheckObjectVersion(ESSIndexHelper.java:115)\n        ...\n2024-10-14 07:21:46,427 WARN [Index-Rebuilder-col1-0] c.e.d.c.f.i.core.collection.FtReindexTask - Reindex for index col1.dmftdoc failed\ncom.emc.documentum.core.fulltext.common.exception.IndexServerException: java.lang.NullPointerException\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.recreatePathIndexNB(ESSCollection.java:3391)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.reindexNB(ESSCollection.java:1360)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.ESSCollection.reindex(ESSCollection.java:1249)\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.collection.FtReindexTask.run(FtReindexTask.java:204)\n        at java.base\/java.lang.Thread.run(Thread.java:834)\nCaused by: java.lang.NullPointerException: null\n        at deployment.dsearch.war\/\/com.emc.documentum.core.fulltext.indexserver.core.index.xhive.ESSXMLNodeHandler.getTokens(ESSXMLNodeHandler.java:163)\n        at deployment.dsearch.war\/\/com.xhive.xDB_10_7_r4558357.ch$b.hasNext(xdb:473)\n        at deployment.dsearch.war\/\/com.xhive.core.index.PathValueIndexModifier.a(xdb:328)\n        ...\n[xplore@ds1-0 logs]$\n<\/pre><\/div>\n\n\n
In terms of processes, it looked “OK”, as all expected Dsearch processes were present, including the (local) CPS Indexing & Querying ones. However, the K8s liveness (a custom one I created long ago) was showing an issue with “\/dsearch<\/strong>” not responding, and the pod was restarting continuously:<\/p>\n\n\n
\n[xplore@ds1-0 logs]$ ps uxf\nUSER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND\nxplore   3015817  0.0  0.0  13920  3220 pts\/1    S    07:20   0:00 \/bin\/sh .\/startPrimaryDsearch.sh\nxplore   3015819  0.0  0.0  13940  3276 pts\/1    S    07:20   0:00  \\_ \/bin\/sh \/app\/xPlore\/wildfly17.0.1\/bin\/standalone.sh\nxplore   3015920 52.9  1.5 10265428 2030744 pts\/1 Sl  07:20   1:14      \\_ \/app\/xPlore\/java64\/JAVA_LINK\/bin\/java -D[Standalone] -server -Xms8g -Xmx8g -XX:MaxMetaspaceSize=512m -XX:+UseG1GC -XX:+UseStringDeduplicati\nxplore   3016359  0.1  0.0 670524 59008 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml Daemon0 9322\nxplore   3016412  0.1  0.0 670460 59868 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml Daemon1 9323\nxplore   3016486  0.1  0.0 670652 61400 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml Daemon2 9324\nxplore   3016539  0.1  0.0 670396 58836 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml Daemon3 9325\nxplore   3016660  0.1  0.0 670588 63384 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml Daemon4 9326\nxplore   3016714  0.1  0.0 670524 61196 pts\/1    Sl   07:21   0:00          \\_ \/app\/xPlore\/dsearch\/cps\/cps_daemon\/bin\/CPSDaemon \/app\/xPlore\/dsearch\/cps\/cps_daemon\/PrimaryDsearch_local_configuration.xml QDaemon0 932\nxplore   3012770  0.0  0.0  14064  3668 pts\/1    Ss   07:14   0:00 bash -l\nxplore   3017548  0.0  0.0  53832  3960 pts\/1    R+   07:22   0:00  \\_ ps uxf\nxplore   3011206  0.0  0.0  14064  3656 pts\/2    Ss+  07:10   0:00 bash -l\nxplore   2988030  0.0  0.0  14064  3720 pts\/0    Ss+  06:21   0:00 bash -l\nxplore   2981707  0.0  0.0  13932  3464 ?        Ss   06:15   0:00 \/bin\/bash \/scripts\/dbi_entrypoint.sh\n[xplore@ds1-0 logs]$\n[xplore@ds1-0 logs]$ \/scripts\/dbi_ft_liveness.sh\nINFO - FT liveness exit code is '1' -- Unexpected http response from component 'PrimaryDsearch' for url 'https:\/\/xxx:9302\/dsearch'...\n[xplore@ds1-0 logs]$\n<\/pre><\/div>\n\n\n
Same thing when trying to stop xPlore to begin the investigations, it shows a problem connecting to the Dsearch:<\/p>\n\n\n
\n[xplore@ds1-0 logs]$ $STARTSTOP stop\n  **\n  **  The PrimaryDsearch is running with PID: 3015920\n  **\nINFO - Stopping the PrimaryDsearch...\nInstance {PrimaryDsearch} is about to shut down, wait for shutdown complete message.\nException in thread "main" java.lang.IllegalArgumentException: Fail to connect remote server (https:\/\/ds1-0.ds1.dctm-ns1-name.svc.cluster.local:9302)\n        at com.emc.documentum.core.fulltext.client.admin.cli.DSearchAdminScript.getAdminService(DSearchAdminScript.java:86)\n        at com.emc.documentum.core.fulltext.client.admin.cli.DSearchAdminScript.stopNode(DSearchAdminScript.java:187)\n        ...\nCaused by: com.emc.documentum.core.fulltext.common.admin.DSearchAdminException: [ERROR] ServiceException thrown out:\n        com.emc.documentum.core.fulltext.indexserver.admin.controller.ServiceException: Exception happened while connect to instance: PrimaryDsearch\n        at com.emc.documentum.core.fulltext.client.admin.api.impl.ESSAdminSOAPClient.<init>(ESSAdminSOAPClient.java:110)\n        at com.emc.documentum.core.fulltext.client.admin.api.impl.ESSAdminServiceImpl.<init>(ESSAdminServiceImpl.java:62)\n        ...\nCaused by: com.emc.documentum.core.fulltext.indexserver.admin.controller.ServiceException: Exception happened while connect to instance: PrimaryDsearch\n        at java.base\/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\n        at java.base\/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\n        at java.base\/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\n        ...\n{\n    "outcome" => "success",\n    "result" => undefined\n}\n[xplore@ds1-0 logs]$\n<\/pre><\/div>\n\n\n
I had no idea what was happening in this environment in the few days prior to the DataCenter issue as the day-to-day support was handled by another team. However, based on the logs, it looked like it could be linked to an online rebuild. Therefore, I went and checked on the recent changes done to the indexserverconfig.xml<\/strong> file and I found that:<\/p>\n\n\n
\n[xplore@ds1-0 logs]$ cd $CONFIG_HOME\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ ll -tr indexserverconfig.xml*\n-rw-r----- 1 xplore xplore 33388 Jul  3  2021 indexserverconfig.xml.bakHttp\n-rw-r----- 1 xplore xplore 33389 Jul  3  2021 indexserverconfig.xml.patch.bak.custom-v1\n-rw-r----- 1 xplore xplore 34628 Oct  8 07:34 indexserverconfig.xml.patch.bak.custom-v2\n-rw-r----- 1 xplore xplore 36696 Oct 10 01:11 indexserverconfig.xml\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ diff indexserverconfig.xml indexserverconfig.xml.patch.bak.custom-v2\n2c2\n< <index-server-configuration enable-lemmatization="true" config-check-interval="60000" revision="1.29">\n---\n> <index-server-configuration enable-lemmatization="true" config-check-interval="60000" revision="1.22">\n159,163d158\n<                     <sub-path path="dmftmetadata\/\/a_status" type="string" enumerate-repeating-elements="false" full-text-search="true" value-comparison="true" returning-contents="true" include-descendants="false" description="Used by REPO_NAME to compute facets." boost-value="1.0" compress="true" leading-wildcard="false" sortable="false" include-start-end-token-flags="true"\/>\n<                     <sub-path path="dmftmetadata\/\/doc_business_unit" type="string" enumerate-repeating-elements="false" full-text-search="true" value-comparison="true" returning-contents="true" include-descendants="false" description="Used by REPO_NAME to compute facets." boost-value="1.0" compress="true" leading-wildcard="false" sortable="false" include-start-end-token-flags="true"\/>\n<                     <sub-path path="dmftmetadata\/\/site_unit" type="string" enumerate-repeating-elements="false" full-text-search="true" value-comparison="true" returning-contents="true" include-descendants="false" description="Used by REPO_NAME to compute facets." boost-value="1.0" compress="true" leading-wildcard="false" sortable="false" include-start-end-token-flags="true"\/>\n<                     <sub-path path="dmftmetadata\/\/doc_responsible_author" type="string" enumerate-repeating-elements="false" full-text-search="true" value-comparison="true" returning-contents="true" include-descendants="false" description="Used by REPO_NAME to compute facets." boost-value="1.0" compress="true" leading-wildcard="false" sortable="false" include-start-end-token-flags="true"\/>\n<                     <sub-path path="dmftmetadata\/\/material_number" type="string" enumerate-repeating-elements="false" full-text-search="true" value-comparison="true" returning-contents="true" include-descendants="false" description="Used by REPO_NAME to compute facets." boost-value="1.0" compress="true" leading-wildcard="false" sortable="false" include-start-end-token-flags="true"\/>\n373,377c368\n<         <collection usage="Data" document-category="dftxml" name="col1">\n<             <properties>\n<                 <property value="dmftdoc_9640f" name="Build_dmftdoc"\/>\n<             <\/properties>\n<         <\/collection>\n---\n>         <collection usage="Data" document-category="dftxml" name="col1"\/>\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ date\nMon Oct 14 07:23:34 UTC 2024\n[xplore@ds1-0 config]$\n<\/pre><\/div>\n\n\n
Based on the above, it looked evident that five new facets were added by someone on the 8-Oct and for these facets to appear on Documentum Search, you would then need to perform an online rebuild. The last section\/difference is related to that online rebuild. Whenever you start an online rebuild, the collection definition is changed in such way, to include a new property named “Build_dmftdoc<\/strong>“. And when it’s completed, it gets removed. However, this is a fairly small index, so an online rebuild should be done in half a day, at most. Above, it appears as if the online rebuild that has been started on the 10-Oct was still in progress, which is definitively not normal.<\/p>\n\n\n\n
I have no evidence of it, but I can only assume that someone started an online rebuild on the 10-Oct for the “col1<\/strong>” collection and before it could complete, the DataCenter issue started, which rendered the Dsearch pod (or one of the CPS-Only pods) frozen and in an inconsistent\/corrupted state. Because of it, there would be a different status for the document 090f123480096bde<\/strong> in the index \/ xDB and that would be preventing the Dsearch to start properly as we see on the logs.<\/p>\n\n\n\n
To fix this issue, I tried to cancel\/remove the online rebuild by modifying the indexserverconfig.xml file manually. For that purpose, I simply incremented the revision number and restored the collection “col1<\/strong>” definition to what it should be without a running online rebuild (so removing the 3 properties lines):<\/p>\n\n\n
\n[xplore@ds1-0 config]$ cp -p indexserverconfig.xml indexserverconfig.xml.with_issue\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ vi indexserverconfig.xml ### Corrected the file here\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ cp -p indexserverconfig.xml indexserverconfig.xml.with_modification\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ diff indexserverconfig.xml.with_issue indexserverconfig.xml.with_modification\n2c2\n< <index-server-configuration enable-lemmatization="true" config-check-interval="60000" revision="1.29">\n---\n> <index-server-configuration enable-lemmatization="true" config-check-interval="60000" revision="1.30">\n373,377c373\n<         <collection usage="Data" document-category="dftxml" name="col1">\n<             <properties>\n<                 <property value="dmftdoc_9640f" name="Build_dmftdoc"\/>\n<             <\/properties>\n<         <\/collection>\n---\n>         <collection usage="Data" document-category="dftxml" name="col1"\/>\n[xplore@ds1-0 config]$\n<\/pre><\/div>\n\n\n
With this new revision “1.30<\/strong>“, I started the Dsearch again and this time it was able to start successfully:<\/p>\n\n\n
\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ $STARTSTOP start\n  **\n  **  The PrimaryDsearch is shutdown\n  **\nINFO - Starting the PrimaryDsearch...\n  **\n  **  The PrimaryDsearch is running with PID: 53180\n  **\n[xplore@ds1-0 config]$\n[xplore@ds1-0 config]$ cdlogPrimaryDsearch\n[xplore@ds1-0 logs]$ cat dsearch.log\n2024-10-14 07:30:24,118 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSNode - Starting xPlore\n2024-10-14 07:30:24,126 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Initializing xPlore instance\n2024-10-14 07:30:24,143 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initializing xDB federation and database\n2024-10-14 07:30:25,376 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveSchemaHandler - File system configuration (revision 1.30) is higher than xDB revision (1.29). Updating indexserverconfig.xml in xDB.\n2024-10-14 07:30:25,931 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.indexserver.core.ESSActiveNodesRegistry - Register instance PrimaryDsearch\n2024-10-14 07:30:25,932 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Starting xDB for instance primary\n2024-10-14 07:30:26,123 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initialize xDB driver to local driver with cache pages: 524288 and Socket timeout :1000 ms\n2024-10-14 07:30:26,395 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - XDB is listening at 9330 successfully\n2024-10-14 07:30:26,504 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - Initialize xDB driver to remote driver with cache pages: 524288 and Socket timeout :1000 ms\n2024-10-14 07:30:26,504 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.engine.xhive.impl.XhiveManager - The XML database server is started successfully. {xDB version=xDB 10_7@4558357}\n2024-10-14 07:30:26,514 DEBUG [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (local)  with connection 3\n2024-10-14 07:30:33,925 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a local Content Processing Service with version [20.2.0000.0015].\n2024-10-14 07:30:33,986 DEBUG [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (https:\/\/cps1-0.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl)  with connection 3\n2024-10-14 07:30:34,447 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a remote Content Processing Service [https:\/\/cps1-0.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl] with version [20.2.0000.0015].\n2024-10-14 07:30:34,636 DEBUG [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Begin to connect to CPS at (https:\/\/cps1-1.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl)  with connection 3\n2024-10-14 07:30:34,838 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.cps.CPSSubmitter - Connected to a remote Content Processing Service [https:\/\/cps1-1.cps1.dctm-ns1-name.svc.cluster.local:9302\/cps\/ContentProcessingService?wsdl] with version [20.2.0000.0015].\n2024-10-14 07:30:35,030 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Initialize domain SystemData\n2024-10-14 07:30:35,128 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Initialize domain REPO_NAME\n2024-10-14 07:30:35,387 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Starting Audit Service\n2024-10-14 07:30:35,391 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.services.audit.impl.FtAuditService - Audit records purge task will launch at: 2024-10-15T00:00:00+00:00\n2024-10-14 07:30:35,392 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.indexserver.services.FtBaseService - Auditing service started\n2024-10-14 07:30:35,392 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Starting System Metrics Service\n2024-10-14 07:30:35,396 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.indexserver.services.FtBaseService - SystemMetrics service started\n2024-10-14 07:30:35,396 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Starting Group Cache Service\n2024-10-14 07:30:35,397 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.s.groupcache.impl.FtGroupCacheService - Enable incremental group cache update\n2024-10-14 07:30:35,397 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.indexserver.services.FtBaseService - GroupCache service started\n2024-10-14 07:30:35,399 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.services.security.GlobalACLCache - Use global ACL cache, user count=10, clear delay time=0\n2024-10-14 07:30:35,400 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.services.security.GlobalACECache - Use global ACE cache, ACE cache size=1000000\n2024-10-14 07:30:35,400 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - Starting Auto Warmup Service\n2024-10-14 07:30:35,410 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.indexserver.services.FtBaseService - Warmup service started\n2024-10-14 07:30:35,417 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSContext - The xPlore instance PrimaryDsearch initialized\n2024-10-14 07:30:35,425 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.core.index.thread.WorkerThreadPool - Spawn a new thread CPSWorkerThread-1\n2024-10-14 07:30:35,426 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.core.index.thread.WorkerThreadPool - Spawn a new thread CPSWorkerThread-2\n2024-10-14 07:30:35,427 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.core.index.thread.WorkerThreadPool - Spawn a new thread IndexWorkerThread-1\n2024-10-14 07:30:35,427 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.core.index.thread.WorkerThreadPool - Spawn a new thread IndexWorkerThread-2\n2024-10-14 07:30:35,438 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSNode - The xPlore instance PrimaryDsearch started the indexing threads.\n2024-10-14 07:30:35,451 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.search.threads.SearchThreadPool - Spawn 4 search threads\n2024-10-14 07:30:36,445 INFO [ServerService Thread Pool -- 80] c.e.d.c.f.i.admin.controller.jmx.ESSAdminJMXPlugin - Admin agent started.\n2024-10-14 07:30:36,445 INFO [ServerService Thread Pool -- 80] c.e.d.core.fulltext.indexserver.core.ESSNode - The xPlore instance PrimaryDsearch started. {version=20.2.0000.0015}\n[xplore@ds1-0 logs]$\n<\/pre><\/div>\n\n\n
To close this topic, a new online rebuild was started, to make sure the facets are properly showing-up, since I wasn’t sure what was the exact status of other collections. Once it was done, the Dsearch pod could restart again without problems, so the issue was fully fixed.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
I recently faced another interesting issue (c.f. this one) with Documentum xPlore where the Dsearch would refuse to start because of a stuck online rebuild. It happened on a Kubernetes environment using custom images we built (for security and scalability). The K8s Nodes were split across two DataCenters for DR reasons. However, one of the […]<\/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":[1101,2609,912,91,2046,474],"type_dbi":[],"class_list":["post-35265","post","type-post","status-publish","format-standard","hentry","category-enterprise-content-management","tag-cps","tag-documentum-2","tag-dsearch","tag-index","tag-query","tag-xplore"],"acf":[],"yoast_head":"\nDocumentum - xPlore Dsearch not starting with a stuck rebuild - dbi Blog<\/title>\n<meta name=\"description\" content=\"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!\" \/>\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\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Documentum - xPlore Dsearch not starting with a stuck rebuild\" \/>\n<meta property=\"og:description\" content=\"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2024-10-15T17:45:00+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=\"3 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\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/\"},\"author\":{\"name\":\"Morgan Patou\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"headline\":\"Documentum – xPlore Dsearch not starting with a stuck rebuild\",\"datePublished\":\"2024-10-15T17:45:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/\"},\"wordCount\":623,\"commentCount\":0,\"keywords\":[\"CPS\",\"Documentum\",\"Dsearch\",\"index\",\"query\",\"xPlore\"],\"articleSection\":[\"Enterprise content management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/\",\"name\":\"Documentum - xPlore Dsearch not starting with a stuck rebuild - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2024-10-15T17:45:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/c4d05b25843a9bc2ab20415dae6bd2d8\"},\"description\":\"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Documentum – xPlore Dsearch not starting with a stuck rebuild\"}]},{\"@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":"Documentum - xPlore Dsearch not starting with a stuck rebuild - dbi Blog","description":"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!","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\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/","og_locale":"en_US","og_type":"article","og_title":"Documentum - xPlore Dsearch not starting with a stuck rebuild","og_description":"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!","og_url":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/","og_site_name":"dbi Blog","article_published_time":"2024-10-15T17:45:00+00:00","author":"Morgan Patou","twitter_card":"summary_large_image","twitter_creator":"@MorganPatou","twitter_misc":{"Written by":"Morgan Patou","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/"},"author":{"name":"Morgan Patou","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"headline":"Documentum – xPlore Dsearch not starting with a stuck rebuild","datePublished":"2024-10-15T17:45:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/"},"wordCount":623,"commentCount":0,"keywords":["CPS","Documentum","Dsearch","index","query","xPlore"],"articleSection":["Enterprise content management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/","url":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/","name":"Documentum - xPlore Dsearch not starting with a stuck rebuild - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2024-10-15T17:45:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/c4d05b25843a9bc2ab20415dae6bd2d8"},"description":"An apparently working xPlore Dsearch is suddenly not able to start anymore? It might be related to a stuck online rebuild!","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/documentum-xplore-dsearch-not-starting-with-a-stuck-rebuild\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Documentum – xPlore Dsearch not starting with a stuck rebuild"}]},{"@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\/35265","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=35265"}],"version-history":[{"count":4,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/35265\/revisions"}],"predecessor-version":[{"id":35273,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/35265\/revisions\/35273"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=35265"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=35265"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=35265"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=35265"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}