Upsource 3.5 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

Expired free license.

Following the upgrade, Upsource fails to convert an older license to the new free license.

Provide new license.

See instruction

"Server SSL certificate not trusted" displayed during upgrade.

Upsource can't connect to the external Hub because the server SSL certificate is not found or expired.

Import the Hub certificate to Upsource and configure Upsource to accept it.

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.

Upsource can't connect to the external Hub because the server SSL certificate is not found or expired.

Import the Hub certificate to Upsource and configure Upsource to accept it.

See instruction

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. Following the upgrade from earlier versions (2.X.X) to version 3.5, 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.5 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.5 Free 10 Users Pack

Key:

7df4fea355a244e799d0a34bdb7b2d384ecd5e2c244b338ae5baac82b85b93d172d6998c68d22818248e2cc721e602a87ced6cac5ebb36f8579582aac00d033e7a2c3fa1fd26e0219d71de568ffc3caf55759c91768642d07b9615a2ce832b79556ec5ee826125fba7ecb14224a3534d37913c8b6cdbf9f2b1796bc85aa0b4dd

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

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

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

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

7. Server SSL certificate is not found or expired

Problem

Upsource is unable to connect to external Hub, which results in the following:

  • Upsource fails to start.
  • During an upgrade procedure, the message Server SSL certificate not trusted is shown in the Upsource web UI.

Solution

Follow this instruction to import the Hub certificate to Upsource and configure Upsource to accept it:

  1. Download your host's certificate from the browser (the instruction is for Google Chrome):

    • Open the Hub home page (for instance https://myhub.com)
    • Click the lock icon in the address bar to display information about the host.
    • Go to the Connections tab and click Certificate information. A dialog with information about the host's certificate will be displayed.
    • Go to the Details tab and click the Export... button at the bottom.
    • Save the certificate in the "Base64-encoded ASCII, single certificate" format (let's call it myhub.com.cer
  2. Create a new keystore and import the certificate into it. Give it a new password (it must be at least 6 characters) and confirm that you trust the certificate.

    keytool -import -trustcacerts -file myhub.com.cer -alias myhub.com -keystore keystore.jks Enter keystore password: <keystore password> Re-enter new password: <keystore password> ... <Certificate info shown here> ... Trust this certificate? [no]: yes Certificate was added to keystore
  3. Copy the file keystore.jks to <upsource-home>/conf/internal/keystore.jks

  4. In <upsource-home>/conf/internal/bundle.properties set:

    additional-keystore-path=<upsource-home>/conf/internal/keystore.jks additional-keystore-password=<keystore-password>
    Where keystore-password is the password you provided in Step 2.

  5. Restart Upsource <upsource-home>\bin\upsource.bat restart

Last modified: 1 December 2016