It's all about the answers!

Ask a question

Failed to run repotools-jts reindex all for jts/ccm/qm/rm


Qin Wang (111) | asked Nov 24 '15, 12:11 a.m.
   Environemnt: 
APP server: CLM502, WAS 8.5.5.5 
DB2 server: DB2 10.1.0.4 

We want to build a test environment(keep the same URL with production: https://server082.pssc.mop.fr.ibm.com:9443/jts: 
1. Install CLM, WAS and DB2 on test servers. 
2. Restored DBs from production to test environment. 
3. Copy the installation path of CLM and WAS to the test servers. 
4. Replaced the database connection parameters in the teamserver.properties files and /etc/hosts. 
5. Reset lock id by running repotools-.sh -resetRepoLockId (as there are logs to require reset lockid) 
6. Start WAS, and jts/admins shows: 
CRJZS5676E The index at "/opt/IBM/WebSphere85/AppServer/profiles/CLM01/conf/jts/indices/10816fc004444091b8a56d5e28c2a47a/jfs-textindex" was indexed with public url "https://server071.pssc.mop.fr.ibm.com:9443/jts", but it is now set to "https://server082.pssc.mop.fr.ibm.com:9443/jts". Revert your public url or run the repotools command -reindex all if the change is intended

Then we tried to run "repotools-.sh reindex all", but failed: 
repotools-jts.sh -reindex all 
Repo Tools 
Provisioning using "./conf/jts/provision_profiles". 
Jazz Foundation - Core Libraries, Version 5.0.2 (RJF-I20141028-1603) 

To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum
To find more information about a message, see the online product documentation. 
CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties". 
CRJAZ1779I This server is configured as a JTS. 
CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false. 
CRJAZ1365I The server is attempting to connect to the following database: "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;" 
CRJAZ1364I The connection to the following database was successful: 
Db Product Name: DB2/AIX64 
Db Product Version: SQL10014 
Db URL: jdbc:db2://server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx; 
Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ 
Jdbc Driver Version: 4.17.28 
CRJAZ1971I The server is configured with: 
Public URI: "https://server082.pssc.mop.fr.ibm.com:9443/jts" 
CRJAZ2523I Setting the global server rename state to false and the validation state to false. 
Plug-in "com.ibm.team.dashboard.viewlets.service" was unable to instantiate class "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService". 
CRJAZ1093E The "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService" feature could not start. 
CRJAZ2105I Checking for a running server... 
The user "ADMIN" has logged in to the database "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;". 
CRJZS5170I Reindexing resources from database //server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx; 
CRJAZ1141I Cannot get the service "com.ibm.team.jfs.indexing.service.IHttpIndexingService". 
CRJZS5169E The command cannot be run. 
CRJZS6110E Resources from the //server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx; database could not be reindexed. 
The user "ADMIN" has logged out of the database "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;". 

The repotools-jts_reindex.log shows: 
2015-11-24 04:10:47,314 Repo Tools 
2015-11-24 04:10:47,315 java.version=1.6.0 
2015-11-24 04:10:47,315 java.runtime.version=pxa6460sr16fp1-20140706_01 (SR16 FP1) 
2015-11-24 04:10:47,321 Provisioning using "./conf/jts/provision_profiles". 
2015-11-24 04:10:47,353 repotools-jts -reindex all 
2015-11-24 04:10:47,361 Jazz Foundation - Core Libraries, Version 5.0.2 (RJF-I20141028-1603) 

2015-11-24 04:10:47,390 
To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum
To find more information about a message, see the online product documentation. 
2015-11-24 04:10:47,390 CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties". 
2015-11-24 04:10:47,794 CRJAZ1779I This server is configured as a JTS. 
2015-11-24 04:10:48,856 CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false. 
2015-11-24 04:10:50,352 CRJAZ1365I The server is attempting to connect to the following database: "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;" 
2015-11-24 04:10:51,361 CRJAZ1364I The connection to the following database was successful: 
Db Product Name: DB2/AIX64 
Db Product Version: SQL10014 
Db URL: jdbc:db2://server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx; 
Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ 
Jdbc Driver Version: 4.17.28 
2015-11-24 04:10:51,625 CRJAZ1971I The server is configured with: 
Public URI: "https://server082.pssc.mop.fr.ibm.com:9443/jts" 
2015-11-24 04:10:53,007 CRJAZ2523I Setting the global server rename state to false and the validation state to false. 
2015-11-24 04:11:01,113 Plug-in "com.ibm.team.dashboard.viewlets.service" was unable to instantiate class "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService". 
org.eclipse.core.runtime.CoreException: Plug-in "com.ibm.team.dashboard.viewlets.service" was unable to instantiate class "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService". 
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194) 
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:188) 
at com.ibm.team.repository.service.internal.registry.ClientLocalizingRegistryStrategy.createExecutableExtension(ClientLocalizingRegistryStrategy.java:56) 
at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904) 
at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) 
at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) 
at com.ibm.team.repository.service.internal.registry.ClientLocalizingConfigurationElement.createExecutableExtension(ClientLocalizingConfigurationElement.java:137) 
at com.ibm.team.repository.common.transport.AbstractElementDescriptor.createInstance(AbstractElementDescriptor.java:254) 
at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderElementDescriptor.createImplementation(ServiceProviderElementDescriptor.java:81) 
at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderElementDescriptor.getImplementation(ServiceProviderElementDescriptor.java:140) 
at com.ibm.team.repository.common.transport.internal.registry.ServiceProviderActivationManagerOwner.getImplementation(ServiceProviderActivationManagerOwner.java:63) 
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.getImplementation(AbstractActivationManagerOwner.java:851) 
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.performActivation(AbstractActivationManagerOwner.java:684) 
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:749) 
at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.activate(AbstractActivationManagerOwner.java:211) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.activate(BundleActivationManager.java:290) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.performActivation(BundleActivationManager.java:1589) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.access$2(BundleActivationManager.java:1574) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager$3.acquired(BundleActivationManager.java:573) 
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.serviceAcquired(ImportServiceRecordContainer.java:582) 
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.access$1(ImportServiceRecordContainer.java:566) 
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$5.serviceAcquired(ImportServiceRecordContainer.java:352) 
at org.eclipse.soda.sat.core.internal.record.ImportServiceRecord.acquire(ImportServiceRecord.java:116) 
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer$1.execute(ImportServiceRecordContainer.java:64) 
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForService(ServiceRecordContainer.java:181) 
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach(ServiceRecordContainer.java:150) 
at org.eclipse.soda.sat.core.internal.record.container.ServiceRecordContainer.doForEach(ServiceRecordContainer.java:365) 
at org.eclipse.soda.sat.core.internal.record.container.ImportServiceRecordContainer.acquire(ImportServiceRecordContainer.java:303) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportedServices(BundleActivationManager.java:234) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.acquireImportServiceRecords(BundleActivationManager.java:250) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.startSync(BundleActivationManager.java:2054) 
at org.eclipse.soda.sat.core.internal.framework.bundle.BundleActivationManager.start(BundleActivationManager.java:2023) 
at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.startServiceProvider(OsgiServicesManager.java:531) 
at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.register(OsgiServicesManager.java:470) 
at com.ibm.team.repository.common.transport.services.TeamServiceRegist

3 answers



permanent link
Ralph Schoon (63.1k33645) | answered Nov 24 '15, 2:55 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
 If you carefully read the error message

was indexed with public url "...://server071.pssc.mop.fr.ibm.com:9443/jts", but it is now set to "...://server082.pssc.mop.fr.ibm.com:9443/jts". Revert your public url or run the repotools command -reindex all if the change is intended

You changed the public URI of your system, which you can't do unless you run a server rename.
Install your test servers on an isolated test system and make sure to keep the public URI stabe.

permanent link
Qin Wang (111) | answered Nov 24 '15, 4:48 a.m.
 Hello Ralph Schoon ,
Yes, you're right, we changed the hostname from server071 to server082, the error disappeared. Thanks a lot

But we got the error:
 2015-11-24 09:29:51,682 [WebContainer : 3 @@ 09:29 <unauthenticated> <com.ibm.team.dashboard.DashboardUpdateTask@692bc7a2-dae2-4c58-a30c-3c19cfe08e5f> /jts/storage/com.ibm.team.dashboard.nohistory/__version] ERROR com.ibm.team.jfs                                    - CRJZS5644E The information in the index for private applications might be incorrect because the time stamp of the triple live index, 2015-11-19T06:13:40.063Z, is ahead of the time stamp of the database, 2015-11-09T17:19:56.027Z. Stop the server and either restore the index that corresponds to the database or recover the correct index by running this command: "repotools-jts -reindex all".


Then we run repotools-jts.sh -reindex all
but failed: 
repotools-jts.sh reindex all
Repo Tools
Provisioning using "./conf/jts/provision_profiles".
  Jazz Foundation - Core Libraries, Version 5.0.2 (RJF-I20141028-1603)
 To submit questions about issues, go to the Jazz.net forum at https://jazz.net/forum. 
 To find more information about a message, see the online product documentation.
CRJAZ1363I Loading the configuration from "file:conf/jts/teamserver.properties".
CRJAZ1779I This server is configured as a JTS.
CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false.
CRJAZ1365I The server is attempting to connect to the following database: "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
 Db Product Name: DB2/AIX64
  Db Product Version: SQL10014
  Db URL: jdbc:db2://server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ
  Jdbc Driver Version: 4.17.28
CRJAZ1971I The server is configured with: 
  Public URI: "https://server082.pssc.mop.fr.ibm.com:9443/jts"
CRJAZ2523I Setting the global server rename state to false and the validation state to false.
Plug-in "com.ibm.team.dashboard.viewlets.service" was unable to instantiate class "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService".
CRJAZ1093E The "com.ibm.team.dashboard.viewlets.service.internal.feed.FeedService" feature could not start.
CRJAZ2105I Checking for a running server...
The user "ADMIN" has logged in to the database "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;".
CRJZS5170I Reindexing resources from database //server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;
CRJAZ1141I Cannot get the service "com.ibm.team.jfs.indexing.service.IHttpIndexingService".
CRJZS5169E The command cannot be run.
CRJZS6110E Resources from the //server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx; database could not be reindexed.
The user "ADMIN" has logged out of the database "//server117.pssc.mop.fr.ibm.com:60000/JTS:user=xxxxxxxx;password=xxxxxxxx;".


Comments
Ralph Schoon commented Nov 24 '15, 4:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Which likely has the same reason. I wouldn't even look at the second error if you did not fix the first problem.


permanent link
Qin Wang (111) | answered Dec 14 '15, 3:30 a.m.
The problem solved.
Start Applications, excute the following command:
https://serverhostname:port/app/admin/cmd/requestReset

Stop the Server, try the repotools-jts -reindex, succeeded.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.