Common issues with Upsource

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

1. Following data restore from Upsource 2.0 EAP build, Upsource doesn't switch EAP license to a free 10-user license

Problem

This issue only affects Upsource users who have taken part in Upsource 2.0 Early Access Program.

After backing up project data from a pre-release build, upgrading to the release build of Upsource 2.0 and restoring project data, Upsource may not switch from a EAP license to the bundled release license allowing free use of Upsource with up to 10 users. The erroneously preserved EAP license however manifests itself as expired and does not allow using Upsource.

Solution

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

Name:

Upsource 2.0 Free 10 Users Pack

Key:

bec61c738621fb9bee6dfc650e0b23012d935564a6169ec44d45eb40fb07a52325f441c89c57d923ca83fa1b1a4d766655f90a365c1de49f1ed20292b2f0c72ed29abd20c8aa5f160eb5eba32f5d5b46523eea35674f07042a10cc6112e9fecc020c50890b51f6d374e36fb60cc37427daf09b238c09a88e09de8b9cfbefc254

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:

Open <upsource_home>\conf\cassandra directory
Copy cassandra.jvmoptions.dist into cassandra.jvmoptions (remove .dist from name)
Open cassandra.jvmoptions
Replace #-Xmx3000m with -Xmx5000m in the file and save it
Make sure you have enough memory/swap on the host
Restart Upsource.

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. Code intelligence is not available

Problem

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

Solution

Double-check that you have set Upsource properties correctly when creating your Upsource project, including a correct path to project model. Edit if necessary.
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 gradle.out file:

Open your Upsource project
Click Browse code at the top of the revisions list
Navigate to /.idea/maven/mvn.out (or /.idea/gradle/gradle.out for Gradle)

If no such file exists:

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

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

Navigate to <upsource_home>/conf
Create a file called upsource.jvmoptions
Place the following lines into this file:
-Djetbrains.jetpass.admin.restore=true -Djetbrains.jetpass.admin.password=XXXXX
replacing XXXXX with a password of your choice
Restart Upsource. Now you should be able to log in with your existing admin account name and your new password.
After logging in with the new password, you can delete the upsource.jvmoptions file to prevent unauthorized access.

Last modified: 14 September 2016