Upsource 3.0 Help

Common issues with Upsource

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

1. Following the upgrade from earlier versions (2.X.X) to version 3.0, Upsource Free 10 Users Pack license is not recognised as valid.

Problem

After backing up project data from an older build and upgrading to Upsource 3.0 with that project data, Upsource may fail to convert an older license to the new free license. The erroneously preserved license manifests itself as expired and does not allow using Upsource.

Solution

Instead of the expired license, please enter the following license name/key combination:

Name:

Upsource 3.0 Free 10 Users Pack

Key:

7389b9a178ee7eb94a7a903523ef059a94d106b9ab16372771f6ce4d3b800c6b66c035f71f318eba3fda5f882c23ed35fc61cdc9b46b5e63ebd1b471d1edce5011a849c41a7fa4d04af1fff9043fad90a71639fbeda953c19f9d6be1d23a4d81d00337b8ebd9b49d8e9cae5ed9990bec21075966c19ebdbaf47a854daeae8909

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 set Upsource 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. Open your Upsource project
  2. Click Browse code at the top of the revisions list
  3. Navigate to /.idea/maven/mvn.out (or /.idea/gradle/gradle.out for Gradle)

If no such file exists:

  1. Navigate to /.idea/model.info
  2. Open model.info and copy the revision ID
  3. Using the search, locate that revision and open it up
  4. Click Browse code and navigate to /.idea/maven/mvn.out (or /.idea/gradle/gradle.out for Gradle)

6. 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.

Last modified: 14 September 2016