Common issues with Upsource
This document lists common issues that Upsource users and administrators face, and suggests solutions.
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:
- Stop Upsource:
<upsource_home>\bin\upsource.bat stop
-
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:
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
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
- 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.
- 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:
<Your_Upsource_URL>/~generatedTree/<Project_ID>:<Revision_ID>
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.