Still indexing after 16 hours

I originally created my project and linked to the root of my Visual SVN repo. The indexing took about an hour to complete but I was not seeing any of the branch mapping on the left side. All of the commits looked to be in one branch. After reviewing the docs I realized that I should have created my project and linked it to the trunk (Master/trunk) of my repo. I deleted and recreated the project and it has been indexing for the last 16 hours.

Is there somewhere I can see the progress/status of the indexing?

Update:
It appears that deleting a (all) project and recreating puts Upsource in a bad state. If I delete all of the projects and try to recreate the one that was still indexing I will get the same "Project is being indexed, please check back later". To my users it looks the project is no longer there, even after going in and adding them to the new groups.



Attachment(s):
indexing.png
12 comments

Hi David,

Indexing can take some time, especially for huge repositories. We have Indexing progress bar in our priority pool and it should be implemented in the nearest future. As for now some info could be found in Administration page - it shows earliest processed commit. Also please check the following file Upsource/logs/upsource-analyzer/errors.log for any errors or exceptions, if any, please post it here.

0

Like my update shows, I created a new project with a different name. I'll let this one run for 24 hours but having no progress or status it doesn't give me hope that it will complete.

0

Hello together,

i have the same problem.

I don't have any errors in the error.out, but a lot of warnings in upsource-analyzer-stderr.log like this one.

[Upsource Analyzer Error] [2014-12-14 11:28:00,738] WARN  ing send processor-1 urce.messaging.impl.Connection - Error sending message '127.0.0.1:10041'->'127.0.0.1:8886' on upsource~monitoring
[Upsource Analyzer Error] java.io.IOException: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
[Upsource Analyzer Error]       at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
[Upsource Analyzer Error]       at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
[Upsource Analyzer Error]       at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
[Upsource Analyzer Error]       at sun.nio.ch.IOUtil.write(IOUtil.java:65)
[Upsource Analyzer Error]       at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:487)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.SocketOutputStream$1.performIO(SocketOutputStream.java:49)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:110)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.SocketOutputStream.write(SocketOutputStream.java:109)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.SocketOutputStream.write(SocketOutputStream.java:81)
[Upsource Analyzer Error]       at java.io.OutputStream.write(OutputStream.java:75)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.Connection.writeTo(Connection.java:194)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.Connection.write(Connection.java:167)
[Upsource Analyzer Error]       at com.jetbrains.upsource.messaging.impl.MessagingImpl$8.run(MessagingImpl.java:381)
[Upsource Analyzer Error]       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[Upsource Analyzer Error]       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[Upsource Analyzer Error]       at java.lang.Thread.run(Thread.java:724)


Could this be a problem?



Thanks a lot for helping.
0

The indexing has been running since Thursday. It's now Monday and it's still indexing.



Attachment(s):
upsource_error.log.zip
0

I the log I see errors concerning project 'master'.
Was it removed?

0

Yes, I was trying to recreate Master and it wouldn't let me. So I created a new project svn-master.

0

Well, we had several issues when recreating a project with the same name, so it might be a case here. We'll be investigating this matter on our side.

For now I would suggest 2 options:

1. In case you have a backup of your project, stop Upsource, copy "conf" and "data" folders from the backup folder* and replace current conf and data folders in the
Upsource home directory.

* backup folder is located in home Upsource directory

2. Make a fresh Upsource install.


0

I did a fresh installation and now it looks good. Only 5 minutes for indexing.

0

Alexander,

From the given output it's difficult to say what really happened, so when you have a chance please zip and post all entire contents of the following folder <Upsource_home_directory>\log

Thanks in advance.

0

Having issues with trying to reinstall Upsource. I couldn't delete 3 of the CommitLog files so I rebooted the server. Now I'm seeing:

C:\Upsource\bin>upsource.bat start
Starting Upsource...
* Bundle is running in upgrade mode
* Loading logging configuration from C:\Upsource\lib\log4j.xml
* Redirecting Upsource 1.0 logging to C:\Upsource\logs\bundleProcess
* Configuring Service-Container[bundleProcess]
* Configuring Starting Page Service
* Configuring Apache Cassandra
* Configuring Hub
* Configuring Service-Container[vcsSettingsContainer]
* Configuring VCS Settings
[Upsource Error] [APP-WRAPPER] Failed to start the application: Failed to start
Upsource 1.0: Not allowed exit code -1 from process: bin/vcs-settings configure
[Upsource Error] [APP-WRAPPER] com.jetbrains.launcher.StartupException: Failed t
o start Upsource 1.0: Not allowed exit code -1 from process: bin/vcs-settings co
nfigure
[Upsource Error]        at com.jetbrains.bundle.BundleMain.start(BundleMain.java
:164)
[Upsource Error]        at com.jetbrains.launcher.AppProxy$4.call(AppProxy.java:
79)
[Upsource Error]        at com.jetbrains.launcher.AppProxy$4.call(AppProxy.java:
77)
[Upsource Error]        at java.util.concurrent.FutureTask.run(FutureTask.java:2
62)
[Upsource Error]        at java.util.concurrent.ThreadPoolExecutor.runWorker(Thr
eadPoolExecutor.java:1145)
[Upsource Error]        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Th
readPoolExecutor.java:615)
[Upsource Error]        at java.lang.Thread.run(Thread.java:745)
[Upsource Error] Caused by: com.jetbrains.service.util.StatusException: Not allo
wed exit code -1 from process: bin/vcs-settings configure
[Upsource Error]        at com.jetbrains.bundle.services.impl.CliService.execute
ServiceCommand(CliService.java:121)
[Upsource Error]        at com.jetbrains.bundle.services.impl.CliService.configu
re(CliService.java:107)
[Upsource Error]        at com.jetbrains.bundle.services.impl.BundledCliService.
configure(BundledCliService.java:23)vcs-settings: Using Java: C:\Upsource\intern
al\java\windows-amd64\jre (version "1.7.0_71")

[Upsource Error]        at com.jetbrains.bundle.Services.configure(Services.java
:519)
vcs-settings: Failed to configure JetLauncher: C:\Upsource\conf\vcs-settings\vcs
-settings.launch.config (The system cannot find the path specified)[Upsource Err
or]     at com.jetbrains.bundle.BundleMain.start(BundleMain.java:187)

[Upsource Error]        at com.jetbrains.bundle.BundleMain.start(BundleMain.java
:158)
[Upsource Error]        ... 6 more
Upsource process finished
Launcher is exiting
Upsource failed to start.

This is after deleting and restoring the the conf and data directory from the EAP backup.

0

Looks like restoring configuration from backup isn't compatible with the other software on your computer. Better I couls say after inspection full logs from the Upsource/logs/ directory

0

Gotcha. The only configuration change made was to add our SMTP host.

I completely deleted and restored the Upsource directory and it is now indexing again with our Master repository.

+1 for adding commit graphs with SVN repo feature :O

0

Please sign in to leave a comment.