Common issues with Upsource
This document lists common issues that Upsource users and administrators face, and suggests solutions.
1. You forgot your administrator password
You can't access your administrator account because you forgot your password.
Reset your administrator account password as follows:
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.
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.
Instead of the expired license, please enter the following license name/key combination:
Upsource 3.5 Free 10 Users Pack
3. Not enough memory for Cassandra database
Apache Cassandra database won't start when Upsource launched
Increase heap size to Cassandra process as follows:
4. Insufficient memory settings in Linux may affect Cassandra database performance
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.
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
- 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
6. Code intelligence is not available
Code insight in Maven or Gradle based project is not working. The code analysis status indicator remains grey.
- 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 (or gradle.out) file:
Download the zipped generated tree at the following URL:
Where <Revision_ID> is an ID of the revision which lacks code intelligence.
Find the mvn.out (or gradle.out) file in that tree.
If no such file exists:
- Navigate to /.idea/model.info
- Open model.info and copy the revision ID
- Download the generated tree again, replacing the revision ID in the URL with the one you've copied.
- Find the mvn.out (or gradle.out) file in that tree.
7. Server SSL certificate is not found or expired
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.
Follow this instruction to import the Hub certificate to Upsource and configure Upsource to accept it:
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
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
Where keystore-password is the password you provided in Step 2.