Upsource 2017.1 Help

Common issues with Upsource

This document lists common issues that Upsource users and administrators face, and suggests solutions.

Issue

Cause

Solution

You forgot your administrator password.

Reset your administrator account password.

See instruction

Upsource fails to start.

External (standalone) Hub is not yet initialized.

  • Stop Upsource.
  • Wait a few minutes for Hub to initialize.
  • Start Upsource.

Code insight in Maven or Gradle based project is not working. The code analysis status indicator remains grey.

Code intelligence is disabled or not properly configured.

Enable/edit code intelligence settings. If it doesn't help, get mvn.out (gradle.out) file and contact support.

See instruction

Upsource services consume all memory.

OutOfMemory exception.

Increase heap size available to Upsource frontend process.

See instruction

New commits are not getting indexed.

Revisions are stuck in "indexing in progress" state.

Web UI is extremely slow.

Cassandra database won't start when Upsource launched.

Not enough memory for Cassandra database.

Increase heap size available to Cassandra process.

See instruction

Slow Cassandra performance.

Insufficient memory lock settings.

Increase memory lock limit.

See instruction

1. You forgot your administrator password

Problem

You can't access your administrator account because you forgot your password.

Solution

Reset your administrator account password as follows:

  1. Stop Upsource: <upsource_home>\bin\upsource.bat stop
  2. Enter your new password and start Upsource with the following command:

    <upsource_home>\bin\upsource.bat start --J-Djetbrains.jetpass.admin.restore=true --J-Djetbrains.jetpass.admin.password=XXXXX

    where XXXXX is your new password. Please notice two dashes before J, which means properties are applied to the current start only and should not be reverted by a user manually later.

2. Not enough memory for Cassandra database

Problem

Apache Cassandra database won't start when Upsource launched

Solution

Increase heap size to Cassandra process as follows:

  1. Stop Upsource: <upsource_home>\bin\upsource.bat stop
  2. Run the following command:

    <upsource_home>\apps\cassandra\bin\cassandra.bat configure -J-Xmx5000m

  3. Start Upsource: <upsource_home>\bin\upsource.bat start

3. Insufficient memory settings in Linux may affect Cassandra database performance

Problem

The following warning:

Unable to lock JVM memory (ENOMEM). This can result in part of the JVM being swapped out, especially with mmapped I/O enabled

encountered in the cassandra-stderr.log file indicates insufficient memory lock settings. Even though most of the time it will not cause any problem, it may potentially affect Cassandra performance in some cases.

Solution

Increase memory lock limit by running the ulimit command, or, if you work in Debian, modify the /etc/security/limits.conf file — change max locked memory to unlimited for the user under which Cassandra runs.

4. OutOfMemory exception

Problem

  • Upsource services consume all memory
  • New commits are not getting indexed
  • Some (all) revisions are stuck in "indexing in progress" state
  • Web UI is extremely slow

Solution

  1. Stop Upsource: <upsource_home>\bin\upsource.bat stop
  2. Run the following command:

    <upsource_home>\apps\upsource-frontend\bin\upsource-frontend.bat configure -J-Xmx2000m

  3. Start Upsource: <upsource_home>\bin\upsource.bat start

5. Code intelligence is not available

Problem

Code insight in Maven or Gradle based project is not working. The code analysis status indicator remains grey.

Solution

  1. Double-check that you have enabled code intelligence and set properties correctly when creating your Upsource project, including a correct path to project model. Edit if necessary.
  2. If it doesn't help, contact Upsource support and describe your problem. Please include a mvn.out or gradle.out file (for Maven or Gradle project correspondingly) with your inquiry.

To find mvn.out (or gradle.out) file:

  1. Download the zipped generated tree at the following URL: <Your_Upsource_URL>/~generatedTree/<Project_ID>:<Revision_ID>

    Where <Revision_ID> is an ID of the revision which lacks code intelligence.

  2. Find the mvn.out (or gradle.out) file in that tree.

    If no such file exists:

  3. Navigate to /.idea/model.info
  4. Open model.info and copy the revision ID
  5. Download the generated tree again, replacing the revision ID in the URL with the one you've copied.
  6. Find the mvn.out (or gradle.out) file in that tree.
Last modified: 13 July 2017