• Check the triggers.log and ensure that the trigger has fired.

• Check the KandoBridge.log and ensure that the trigger is reaching the bridge.

• Test server_master_trig.pl as described in the GitCentric Installation and Release Notes to check for missing dependencies.

• Check that all necessary processes are running: postgres, tomcat, accurev_server.

• Retry by “tickling” the stream: accurev chstream –E t -s <stream>.

• Check for any git push error messages.

• If you receive the following error, particularly when first mapping an existing Git repository to an AccuRev stream, you may be trying to map a case-sensitive Git repo to a case-insensitive AccuRev depot:

• If you are using Gerrit Code Review, make sure that the change is submitted (marked as review passed) after push.

• If you are using Gerrit Code Review and the change state is ‘merge failed’ then the import failed. Import errors (which are usually push errors) appear in the Comments table at the bottom of the Gerrit Code Review Change page.

• Check the kandoGerrit.log and ensure that the bridge is being called.

• Check the kandoBridge.log and ensure that hooks are reaching the bridge.

• Check that all processes are running: postgres, tomcat, accurev_server.

• Check the AccuRev acserver.cnf configuration file and ensure that the service account group (typically "scm_bridge_group") is set as the value for ASSIGN_USER_PRIVILEGE, and that the group includes the actual user account (typically "gcSyncUser") as a member, and that this user account is the one that was specified when the branch was mapped to the AccuRev stream. (Note: some installations may use CC_USER rather than ASSIGN_USER_PRIVILEGE.)

• Retry by redoing the push.