r14 - 2015-05-27 - 14:31:56 - StephanieBagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > IntegrationsTroubleshootingRationalAdapterForGit > GeneralTroubleshootingRationalAdapterForGit

General Troubleshooting Rational Adapter for Git

Authors: IntegrationsTroubleshootingTeam
Build basis: Rational Adapter for Git Standard Edition v1.1, Rational Collaborative Lifecycle Management version 4.0, 4.0.1, 4.0.2, 4.0.3

This page provides general troubleshooting information for Rational Adapter for Git Standard Edition v1.1.

Gerrit patchset-created hook failure

Below are some possible sources of Gerrit patchset-created hook failures:

Install and Setup

  • The banner will not display before running *_setup.sh -i.

  • Linking will not work before registering the site, running *_setup.sh -r, and registering the project. Linking will only work for registered projects.

  • The correct URLs need to be used when initializing, registering, and installing the hook with the *_setup.sh scripts. The scripts can verify the URL is reachable but they do not verify that the URL points to the correct location.

  • A common mistake is to enter the wrong URL when using *_setup.sh -r. This should be the URL shown in the Git Adapter admin page after registering the Gitweb/Gerrit site, not after registering the project. The URL is also in the table on the Git Server Connections page.

  • Similar to above, when using *_setup.sh –hook, the URL to enter is displayed in the Git Adapter admin page after registering the Gitweb/Gerrit project, not the URL after registering the Gitweb/Gerrit site. The URL is also on the Git Server Connection page in the Registered Git Projects table.

  • The Gitweb and Gerrit pages need to be refreshed after initializing and registering using the *_setup.sh scripts for the changes to take effect (such as: the “Register project” link to appear in the administration menu).

  • The Register Project link does not go away after registering the project.

Configurations / Web

  • Banner does not shown for Gitweb or Gerrit
    • This could be due to Firewall between Gitweb/Gerrit server and the Git Adapter server
    • Gerrit needs a restart – A restart is required for any configuration changes
  • Unable to register Gerrit projects
    • Try to refresh the browser
    • Gerrit needs a restart – A restart is required for any configuration changes
  • Unable to add link from Gitweb or Gerrit web

IBM WebSphere Cache/Configurations

  • Git Adapter still shows the old version after an upgrade
    • Remove or rename the following folders, if they exist:
      • %WAS Install Directory%/profiles//temp/wscache/gitAdapter_war
      • %WAS Install Directory%/profiles//temp///gitAdapter_war
    • Restart the Git Adapter war file
  • User is still logged on to the Git Adapter even though logout is performed on the JTS.
    • Adding a custom session manager property.
      • Click Application servers > <server/node name> > Session management > Custom properties and add the !InvalidateOnUnauthorizedSessionRequestException = true custom property.
      • Restart the WebSphere Node
    • Clear the browser cookies/cache. A restart of the browser may be required as well

Command-line

  • Unable to add link using command-line interface (hook failure)
    • See the Error message from Git and clear the error condition.
      CRIGT0434E.jpg
    • If there is no Error message from Gerrit, check the Git Adapter log
    • Check your settings. Use the Git config --list command to list the configuration settings:
      • Adapter project URL (rtc.adaptedprojecturl or rtc.gerritadaptedprojecturl)
      • User (rtc.user)
      • Password (rtc.password)
      • JTS URL (rtc.jtsurl)
    • Git Adapter and/or CCM server is down
    • Friendship is not setup
    • User does not have access to the CCM project area
    • User does not have the license (Git Adapter and/or CCM)

Reprocess

  • Gerrit reprocess capability is new in Git Adapter version 1.1
  • Admin should periodically check for errors to reprocess
  • Reprocess can be run repeatedly on the same log file until the link is successful
  • Error logs are created in the %gerrit_root%/hooks/rtchookreprocess directory when the hook fails
    • Files named yyyymmdd-hh-mmssmicros-n.log, where yyyymmdd-hh-mmssmicros is a time stamp and n is the number of times commit processing failed
  • Is Reprocessing needed?
    • Check the failure log and clear the error condition
      • %git_project_repository%/hooks/rtchookreprocess
      • %gerrit install directory%/hooks/rtchookreprocess
    • Running reprocess command
      • Safe to reprocess when in doubt. Reprocess can be run as many times as needed.
      • Go to the %git project repository%/hooks directory and type perl reprocess.pl
      • Go to the %gerrit install directory%/hooks directory and type perl gerrit_reprocess.pl
    • Manual link creation in web UI

Related topics: Deployment web home

External links:

Additional contributors: KotTontranakwong
Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r14 < r13 < r12 < r11 < r10 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project