And the other repo , is stuck at this stage (importing) stage for almost 3 days now.
Hello Santosh,
the first issue you described (configuration reset) looks pretty strange and we are investigating it, I’ll let you know as we get something. The long import, on the other hand, may not be an issue, the initial import can take quire a long time depending on the imported repository history and content. Besides, if the import fails for any reason, it’s being reflected in the UI, so at this time it looks pretty normal. It may worth to check the repository-specific SVN Mirror add-on log to find out what the add-on is doing exactly, but from the UI it looks OK.
Hi Ildar,
Did you find out something .
To put it more clear - The specific window when we click on SVN MIRROR in repository settings, gets greyed out .
While I will not be able to use the mouse in the greyed out part Im still able to use the keyboard TABS and can click on TAB until it goes to the buttons below like “IMPORT” , “MIRROR” etc.
Did you guys figure out if this is a bug with this version of a plugin or a browser issue or if its because we are using bitbucket datacenter
Please let us know when your investigations reveal something.
I would be happy to provide any information you need in this regard.
Hello Santosh,
we are still investigating the “configuration reset” issue you reported earlier; nothing to share yet, but I will inform you as we get something.
The greyed out window may not indicate any issues as the add-on can be busy handling the configuration or the data depending on the stage. If that is taking too long, it may worths to check logs to find out what is going on there, both repository-specific log and the global SVN Mirrors add-on log. Also, it would be good to know what exactly had been done in the UI prior the UI entered to the current state.
And I’d like to ask about you latest message where you posted an error message screenshot. Actually, an error (actually, any error) is a clear indicator that something went wrong, so better to investigate such an issue. Yet you have withdrawn the message, so I wanted to ask if that error is unrelated or has it been resolved already?
Hi Ildar,
Not sure how , but now I got an option of import for the second repository . So I started it - There was a temporary issue where it was unable to create a config file , when clicked on import button, for which I pasted screenshot and now its resolved.
Hence second repo import is just begun. I will monitor it . But my concern is
first-repo - Going on for the last 4 days
Im still observing rolling logs in both repository specific log file and also global svnmirror.log file. Please check both the logs below and let me know if you find any anomaly as its going on fore more than 4 days.
repo-1 repo log
2021-06-18 03:04:51,610 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/quadwafer_pizzaboxN/program_executor/definition.xml' with size=495
2021-06-18 03:04:51,808 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/quadwafer_pizzaboxN/recovery_agent/definition.xml' with size=491
2021-06-18 03:04:52,226 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/quadwafer_pizzaboxN/spindle_rotate_interlock_ok_sensor/definition.xml' with size=249
2021-06-18 03:04:52,453 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/quadwafer_pizzaboxN/spindle_rotate_interlock_ok_sensor/configuration.xml' with size=1367
2021-06-18 03:04:52,706 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/quadwafer_pizzaboxN/simulation.option.xml' with size=269
2021-06-18 03:04:53,004 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/mach4_socketTCRobot2/configuration.xml' with size=454
2021-06-18 03:04:53,440 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/mach4_socketTCRobot2/definition.xml' with size=215
2021-06-18 03:04:53,882 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_during_transfer/configuration.xml' with size=638
2021-06-18 03:04:54,028 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_during_transfer/definition.xml' with size=222
2021-06-18 03:04:54,248 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/configuration.xml' with size=5340
2021-06-18 03:04:54,670 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_complete_transfer/definition.xml' with size=240
2021-06-18 03:04:54,859 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_complete_transfer/configuration.xml' with size=485
2021-06-18 03:04:55,084 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_log_pressure/configuration.xml' with size=615
2021-06-18 03:04:55,191 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/command_log_pressure/definition.xml' with size=235
2021-06-18 03:04:55,425 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/location1/scheduler/system.equipment.dualwafer_pizzabox1.location1_to_transfer_chamber.rule' with size=6344
2021-06-18 03:04:55,646 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/location1/scheduler/system.equipment.dualwafer_pizzabox1.location1.rt' with size=308
2021-06-18 03:04:56,293 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/location1/configuration.xml' with size=543
2021-06-18 03:04:56,420 sync - successfully received 'branches/Project_2386_Access_Control/vxt/branches/VECTOR_Extreme_1_3_VIM/system/equipment/mach4/equipment/dualwafer_pizzabox1/location1/definition.xml' with size=224
global svnmirror log
$ tail -f svnmirror.log
2021-06-18 03:07:42,766 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703][bootstrap-504] queue load rejected, queue already present
2021-06-18 03:07:42,767 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote snapshot request
2021-06-18 03:07:42,767 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713][bootstrap-756] queue load rejected, queue already present
2021-06-18 03:07:43,150 [sg-publisher] INFO sg.scheduler - snapshots to proxy nodes: R_663_703,R_664_713
2021-06-18 03:07:43,158 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote scope release
2021-06-18 03:07:43,158 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote scope release
2021-06-18 03:07:48,773 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote snapshot request
2021-06-18 03:07:48,773 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713][bootstrap-062] queue load rejected, queue already present
2021-06-18 03:07:48,778 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote snapshot request
2021-06-18 03:07:48,779 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703][bootstrap-454] queue load rejected, queue already present
2021-06-18 03:07:49,154 [sg-publisher] INFO sg.scheduler - snapshots to proxy nodes: R_663_703,R_664_713
2021-06-18 03:07:49,162 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote scope release
2021-06-18 03:07:49,162 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote scope release
2021-06-18 03:07:52,430 [threadpool:thread-4] INFO sg.cluster - this node: 3e9783b2-7c21-4f76-a3b8-3d93ff7c8238; detected master records: 3e9783b2-7c21-4f76-a3b8-3d93ff7c8238
2021-06-18 03:07:52,442 [threadpool:thread-4] INFO sg.cluster - this node is a single master
2021-06-18 03:07:54,771 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote snapshot request
2021-06-18 03:07:54,771 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713][bootstrap-457] queue load rejected, queue already present
2021-06-18 03:07:54,772 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote snapshot request
2021-06-18 03:07:54,772 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703][bootstrap-586] queue load rejected, queue already present
2021-06-18 03:07:55,158 [sg-publisher] INFO sg.scheduler - snapshots to proxy nodes: R_663_703,R_664_713
2021-06-18 03:07:55,165 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote scope release
2021-06-18 03:07:55,165 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote scope release
2021-06-18 03:08:00,787 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote snapshot request
2021-06-18 03:08:00,787 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713][bootstrap-728] queue load rejected, queue already present
2021-06-18 03:08:00,789 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote snapshot request
2021-06-18 03:08:00,789 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703][bootstrap-268] queue load rejected, queue already present
2021-06-18 03:08:01,151 [threadpool:thread-4] INFO sg.cluster - this node: 3e9783b2-7c21-4f76-a3b8-3d93ff7c8238; detected master records: 3e9783b2-7c21-4f76-a3b8-3d93ff7c8238
2021-06-18 03:08:01,162 [sg-publisher] INFO sg.scheduler - snapshots to proxy nodes: R_663_703,R_664_713
2021-06-18 03:08:01,163 [threadpool:thread-4] INFO sg.cluster - this node is a single master
2021-06-18 03:08:01,170 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_663_703] remote scope release
2021-06-18 03:08:01,170 [topic-dispatcher:thread-1] INFO sg.scheduler - [R_664_713] remote scope releaseHello Santosh,
I’m investigation issue with auto-configuration you’ve experienced.
From the log files it looks like auto configuration process is unexpectedly interrupted just after SVN log is fetched, but before “origin” branch is discovered (location in SVN repository from which all other branches originates).
As you’ve mentioned that repository is rather large and contains many branches with complicated history, I suspect that there is a bug in auto-configuration code that unfortunately reveals itself on your particular repository.
As a workaround, so far, I could suggest manual configuration instead. In this mode you’ll have to specify branches and tags mapping in repository configuration yourself, not relying on auto configuration heuristics. You may read docs on branches mappings here - TMate SubGit: Branches and tags mapping
In most simple case mapping may look like:
branches = branches/:refs/heads/
tags = tag/:refs/tags/
shelves = shelves/:refs/shelves/
trunk = trunk:refs/heads/master
It will be of a great help if you could share your SVN repository history - with that data we’ll be able to reproduce and fix auto-configuration issue you experience. To get the history you’ll need to run the following command:
svn log --xml -v SVN_URL > log.xml
log file will contain repository history including file names, user names and comments.
hi Alex,
Currently we are past that error and I was able to see the import button couple of hours back and I clicked on it and the import process have started.
repository logs
713-repolog.txt (23.1 KB)
SVN mirror logs
713-svnmirrorlog (107.7 KB)
So does this mean that it is all good now and the import process is started with auto configuration . Or do we still need to follow the steps that you have mentioned ?
Hi Santosh,
since import has already started, there is no need to stop it and change the configuration, let the initial import runs.
Thanks Ildar, Sure I will let it run
But what about the other repo which started the import 4 days back and still running [nexus-git/build]. Is there a way I can know how much percentage is done and how much is pending ?
Because form the UI I can see the blue color bar shows 100 percent done . How can I know how much is done and how much pending and any estimated time etc .
Hello Santosh,
it may happen that the progress bar sticks at 100% for some time when the add-on finishes the import, but there is much data and thus it takes some time. So the mere fact it shows 100% for some time does not indicate a problem. I’m afraid that there is no more indicators or status information in the UI, the progress bar widget is the only one in the UI, but the log contains the complete information, so if you suspect anything goes wrong, it may worth to take a look at the log (repository-specific add-on log in the first place) or collect support.zip for us to analyze.
hi Team ,
This repo which is going on importing for the last 2 weeks, stopped writing the logs from yesterday. And this is what I see in the repo logs. and the UI
**Anything to be concerned about ? **
UI SCREENSHOT.
REPO LOGS
2021-06-23 19:41:25,456 sync - sendCopyFrom=false
======
r76031
A branches/PR_025536 (from config/config-pecvd:76030)
======
2021-06-23 19:41:25,471 sync - svn: E200015: task cancelled
2021-06-23 19:41:25,472 sync - svn: E200015: task cancelled com.a.a.a.b.e: svn: E200015: task cancelled
at com.a.a.a.b.i.a(SourceFile:26)
at com.a.a.a.d.C.b(SourceFile:738)
at com.a.a.a.d.C.a(SourceFile:436)
at com.a.a.a.d.C.a(SourceFile:396)
at com.a.a.a.d.C.a(SourceFile:342)
at com.a.a.a.d.C.a(SourceFile:169)
at com.a.a.a.d.O.c(SourceFile:43)
at com.a.a.a.d.O.b(SourceFile:36)
at org.tmatesoft.translator.m.aj.a(SourceFile:1464)
at org.tmatesoft.translator.m.aj.c(SourceFile:997)
at org.tmatesoft.translator.m.aj.a(SourceFile:1020)
at org.tmatesoft.translator.m.aj.b(SourceFile:1078)
at org.tmatesoft.translator.m.d.h.a(SourceFile:242)
at org.tmatesoft.translator.m.d.h.a(SourceFile:148)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.doSync(SourceFile:93)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.runSyncCommands(SourceFile:82)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.runSecurely(SourceFile:77)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.lambda$run$0(SourceFile:110)
at com.atlassian.stash.internal.user.DefaultEscalatedSecurityContext.call(DefaultEscalatedSecurityContext.java:59)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.run(SourceFile:108)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.run(SourceFile:22)
at org.tmatesoft.subgit.stash.mirror.scheduler.SgTaskScheduler$TaskWrapper.runTask(SourceFile:999)
at org.tmatesoft.subgit.stash.mirror.scheduler.SgTaskScheduler$TaskWrapper.run(SourceFile:961)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: task cancelled
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SourceFile:66)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SourceFile:57)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:760)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:352)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:340)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(SourceFile:910)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(SourceFile:363)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(SourceFile:1361)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(SourceFile:853)
at com.a.a.a.d.C.a(SourceFile:1893)
at com.a.a.a.d.C.a(SourceFile:1046)
at com.a.a.a.d.C.a(SourceFile:782)
at com.a.a.a.d.C.b(SourceFile:700)
... 24 common frames omitted
Caused by: com.a.a.a.b.e: task cancelled
at org.tmatesoft.translator.m.aj$7.a(SourceFile:1498)
at com.a.a.a.d.C$1.a(SourceFile:448)
at com.a.a.a.c.aw.checkCancelled(SourceFile:24)
at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeDir(SourceFile:100)
at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(SourceFile:497)
at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(SourceFile:103)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(SourceFile:898)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(SourceFile:863)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(SourceFile:220)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:451)
... 34 common frames omitted
2021-06-23 19:41:43,881 sync - Restoring refs to reflect SVN state.
2021-06-23 19:41:51,371 sync - Refs were successfully updated
2021-06-23 19:41:51,610 sync - ######### LOCATION STATE REPORT ############
2021-06-23 19:41:51,735 sync - svn: E200015: task cancelled
2021-06-23 19:41:51,752 sync - svn: E200015: task cancelled org.tmatesoft.translator.util.a: svn: E200015: task cancelled
at org.tmatesoft.translator.util.f.c(SourceFile:107)
at org.tmatesoft.translator.util.f.b(SourceFile:75)
at org.tmatesoft.translator.m.aj.c(SourceFile:1000)
at org.tmatesoft.translator.m.aj.a(SourceFile:1020)
at org.tmatesoft.translator.m.aj.b(SourceFile:1078)
at org.tmatesoft.translator.m.d.h.a(SourceFile:242)
at org.tmatesoft.translator.m.d.h.a(SourceFile:148)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.doSync(SourceFile:93)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.runSyncCommands(SourceFile:82)
at org.tmatesoft.subgit.stash.mirror.tasks.SgSyncTask.runSecurely(SourceFile:77)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.lambda$run$0(SourceFile:110)
at com.atlassian.stash.internal.user.DefaultEscalatedSecurityContext.call(DefaultEscalatedSecurityContext.java:59)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.run(SourceFile:108)
at org.tmatesoft.subgit.stash.mirror.tasks.SgMirrorTask.run(SourceFile:22)
at org.tmatesoft.subgit.stash.mirror.scheduler.SgTaskScheduler$TaskWrapper.runTask(SourceFile:999)
at org.tmatesoft.subgit.stash.mirror.scheduler.SgTaskScheduler$TaskWrapper.run(SourceFile:961)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.a.a.a.b.e: svn: E200015: task cancelled
at com.a.a.a.b.i.a(SourceFile:26)
at com.a.a.a.d.C.b(SourceFile:738)
at com.a.a.a.d.C.a(SourceFile:436)
at com.a.a.a.d.C.a(SourceFile:396)
at com.a.a.a.d.C.a(SourceFile:342)
at com.a.a.a.d.C.a(SourceFile:169)
at com.a.a.a.d.O.c(SourceFile:43)
at com.a.a.a.d.O.b(SourceFile:36)
at org.tmatesoft.translator.m.aj.a(SourceFile:1464)
at org.tmatesoft.translator.m.aj.c(SourceFile:997)
... 16 common frames omitted
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: task cancelled
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SourceFile:66)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SourceFile:57)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:760)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:352)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:340)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(SourceFile:910)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(SourceFile:363)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(SourceFile:1361)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(SourceFile:853)
at com.a.a.a.d.C.a(SourceFile:1893)
at com.a.a.a.d.C.a(SourceFile:1046)
at com.a.a.a.d.C.a(SourceFile:782)
at com.a.a.a.d.C.b(SourceFile:700)
... 24 common frames omitted
Caused by: com.a.a.a.b.e: task cancelled
at org.tmatesoft.translator.m.aj$7.a(SourceFile:1498)
at com.a.a.a.d.C$1.a(SourceFile:448)
at com.a.a.a.c.aw.checkCancelled(SourceFile:24)
at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.closeDir(SourceFile:100)
at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.endElement(SourceFile:497)
at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.endElement(SourceFile:103)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(SourceFile:898)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(SourceFile:863)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(SourceFile:220)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(SourceFile:451)
... 34 common frames omitted
2021-06-23 19:41:51,758 sync - ############## SVN LOG #############
2021-06-23 19:41:51,758 sync - Start svn log for location 'default'
2021-06-23 19:41:52,207 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:41:52,207 sync - added user name credentials: ChakiSa
2021-06-23 19:41:52,207 sync - explicit user name credentials: ChakiSa
2021-06-23 19:41:52,274 sync - Repository log for URL http://nexus.novellus.com/svn, from HEAD to HEAD with limit 16
2021-06-23 19:41:54,155 sync -
r81742 | Prasara1 | 2021-06-23 13:17:31 +0000 (Wed, 23 Jun 2021)
Changed paths:
M /build/trunk/development/sonar/nexus-devices-build.xml
M /build/trunk/development/sonar/nexus-ds-build.xml
M /build/trunk/development/sonar/nexus-gui-build.xml
M /build/trunk/development/sonar/nexus-rt-build.xml
PR-080399 : Update the build scripts to migrate the sonar instance to the Production server
* Fixed a typo in the jar name
2021-06-23 19:41:54,363 sync - ############## GIT LOG #############
2021-06-23 19:42:05,894 sync - ######### USER VISIBLE REPOSITORY CONFIG ############
2021-06-23 19:42:06,205 sync -
#
# Subversion to Git mapping options
#
[svn]
# Options below (trunk, branches, tags, shelves) define correspondence between Subversion
# directories and Git references. Depending on the actual Subversion project layout and whether
# all or only some of the branches have to be mirrored, these options might need to be adjusted.
#
# Generic mapping syntax is:
# <Subversion-Path-Pattern>:<Git-Reference-Pattern>
#
# Subversion paths are relative to the URL defined by the svn.url option.
#
# For more details refer to http://subgit.com/documentation pages.
trunk = trunk:refs/heads/master
branches = branches/*:refs/heads/*
tags = tags/*:refs/tags/*
shelves = shelves/*:refs/shelves/*
triggerGitGC = false
2021-06-23 19:42:06,205 sync - ######### ACTIVE REPOSITORY CONFIG ############
2021-06-23 19:42:06,393 sync -
#
# Subversion to Git mapping options
#
[svn]
# Subversion repository URL
url = http://nexus.novellus.com/svn
minimalRevision = 1
keepGitCommitTime = false
auth = default
# Options below (trunk, branches, tags, shelves) define correspondence between Subversion
# directories and Git references. Depending on the actual Subversion project layout and whether
# all or only some of the branches have to be mirrored, these options might need to be adjusted.
#
# Generic mapping syntax is:
# <Subversion-Path-Pattern>:<Git-Reference-Pattern>
#
# Subversion paths are relative to the URL defined by the svn.url option.
#
# For more details refer to http://subgit.com/documentation pages.
trunk = trunk:refs/heads/master
branches = branches/*:refs/heads/*
tags = tags/*:refs/tags/*
shelves = shelves/*:refs/shelves/*
triggerGitGC = false
[core]
shared = false
logs = subgit/logs
authorsFile = UTF-8
pathEncoding = UTF-8
[auth "default"]
subversionConfigurationDirectory = subgit
userName = hercule
[daemon]
pidFile = subgit/daemon.pid
idleTimeout = 0
classpath = /bitbucket_home/shared/data/subgit/lib/3.3.9-9999999
[translate]
eols = false
ignores = true
2021-06-23 19:42:06,393 sync - ######### REGISTRATION DATA ############
2021-06-23 19:42:06,630 sync - Repository id: 75cd1f3291ca1a21ceaa1473242bd3ba26047c4f
2021-06-23 19:42:06,630 sync - Initial revision: 81704
2021-06-23 19:42:06,630 sync - Installation time: Sun Jun 13 22:05:52 PDT 2021
2021-06-23 19:42:06,630 sync - Active license id: 4fc732dcd1192bc752955b2a0aa5415a10bbb05a
2021-06-23 19:42:06,630 sync - Purchase id: AE-d7684942959fa6801877ef72c6eb85648498f6fd
2021-06-23 19:42:06,630 sync - Registration date: Sun Jun 13 22:06:00 PDT 2021
2021-06-23 19:42:06,630 sync - Expiration date: Sun Jul 04 00:00:00 PDT 2021
2021-06-23 19:42:06,630 sync - Supported versions: *.*.*
2021-06-23 19:42:06,630 sync - Supported repository id: null
2021-06-23 19:42:06,630 sync - Registries: []
2021-06-23 19:42:06,630 sync - ######### ERROR REPORT ############
2021-06-23 19:42:06,639 sync - file '/bitbucket_home/shared/data/subgit/repositories/703/subgit/error' does not exist
2021-06-23 19:42:06,639 sync - ######### GIT TO SVN FAILURE REPORT END ############
2021-06-23 19:42:17,609 sync - ===
2021-06-23 19:43:14,508 bootstrap - ===
2021-06-23 19:43:28,081 verify - server 7.4.0 7004000; add-on 4.0.6; cluster has 2 nodes
2021-06-23 19:43:28,180 verify - core.trustfolderstat option will not be unset
2021-06-23 19:43:33,314 verify - starting verify from revision: 13014
2021-06-23 19:43:37,822 verify - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:43:37,933 verify - added user name credentials: ChakiSa
2021-06-23 19:43:37,943 verify - explicit user name credentials: ChakiSa
2021-06-23 19:43:38,053 verify - Verifying '/bitbucket_home/shared/data/subgit/repositories/703', revisions [13014:63567].
2021-06-23 19:43:38,065 verify - verifying revision range: 13014:63567
2021-06-23 19:43:41,020 verify - Verifying revision range [10108:10108].
2021-06-23 19:43:41,681 verify - Verifying revision range [13012:13014].
2021-06-23 19:43:43,297 verify - Verifying revision range [13980:13980].
2021-06-23 19:43:43,843 verify - Verifying revision range [18969:18969].
2021-06-23 19:43:44,363 verify - Verifying revision range [23428:23433].
2021-06-23 19:43:45,799 verify - Verifying revision range [29739:29739].
2021-06-23 19:43:48,302 verify - Verifying revision range [33795:33795].
2021-06-23 19:43:48,812 verify - Verifying revision range [58903:58912].
2021-06-23 19:43:50,560 verify - Verifying revision range [63565:63567].
2021-06-23 19:43:53,712 verify - Verification of '/bitbucket_home/shared/data/subgit/repositories/703' finished.
2021-06-23 19:44:01,650 verify - updating verify information:
2021-06-23 19:44:01,774 verify - version: 4.0.6
2021-06-23 19:44:01,801 verify - revision: 63567
2021-06-23 19:44:01,812 verify - completed: true
2021-06-23 19:44:01,825 verify - errors:
2021-06-23 19:44:01,859 verify - ===
2021-06-23 19:44:09,146 sync - server 7.4.0 7004000; add-on 4.0.6; cluster has 2 nodes
2021-06-23 19:44:12,603 sync - Repository fetch started.
2021-06-23 19:44:16,469 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:44:16,645 sync - added user name credentials: ChakiSa
2021-06-23 19:44:16,678 sync - explicit user name credentials: ChakiSa
2021-06-23 19:44:16,753 sync - Checking remote 'http://nexus.novellus.com/svn'.
2021-06-23 19:44:17,515 sync - Revisions: <fetched=63567; last=81742>
2021-06-23 19:44:20,419 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:44:20,663 sync - added user name credentials: ChakiSa
2021-06-23 19:44:20,675 sync - explicit user name credentials: ChakiSa
2021-06-23 19:44:25,758 sync - progress range: Fetching revisions from r63567 to r81742
2021-06-23 19:44:29,071 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:44:29,231 sync - added user name credentials: ChakiSa
2021-06-23 19:44:29,231 sync - explicit user name credentials: ChakiSa
2021-06-23 19:44:31,566 sync - Starting fetch-back preventing procedure.
2021-06-23 19:44:34,440 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:44:34,490 sync - added user name credentials: ChakiSa
2021-06-23 19:44:34,490 sync - explicit user name credentials: ChakiSa
2021-06-23 19:44:37,695 sync - Checking for fetch-back phase prevention feasibility.
2021-06-23 19:44:41,467 sync - svn authentication manager for ''http://nexus.novellus.com/svn''
2021-06-23 19:44:41,517 sync - added user name credentials: ChakiSa
2021-06-23 19:44:41,540 sync - explicit user name credentials: ChakiSa
2021-06-23 19:44:41,932 sync - Fetching http://nexus.novellus.com/svn up to revision=HEAD
2021-06-23 19:46:22,973 sync - Getting content of "" directory at revision 76030
2021-06-23 19:46:23,352 sync - Getting content of "branches" directory at revision 76030
2021-06-23 19:46:23,731 sync - SET_PATH '' 76031 not empty depth=infinity
2021-06-23 19:46:23,731 sync - SET_PATH 'branches' 76031 not empty depth=infinity
2021-06-23 19:46:23,964 sync - SET_PATH '' 76030 not empty depth=infinity
2021-06-23 19:46:23,964 sync - Switch from http://nexus.novellus.com/svn/branches/SIOCSII_01_XX_MAINTENANCE to http://nexus.novellus.com/svn/branches/PR_025536Hi Santosh,
judging from the logs you sent, there was an error “Task cancelled” and the import process was stopped, but a little later the add-on started fetching the data again – it is actually a regular fetch, but it does the same thing – imports the data according to the mapping configuration, so in fact it continues with the import. There is nothing to be concerned about, but worths checking logs from time to time, I think.
hi Ildar,
I have started the import for this particular repo more than 10 days ago and its still ongoing. Did you ever experienced any customer where a single repo takes this huge amount of time ?
Hi Santosh,
yes, we have seen such cases before. The only unusual thing I noticed in your case is that there are not so many revisions in the repository – only 80K which is not that many, usually, long-importing repository are of hundreds of thousands revisions. But it’s not always a problem evidence, it might be legal for your repository as the time for import depends not only on the number of revisions, but also on all other circumstances, like network speed, servers performance, repository size, translating setting, etc.
Also Ildar, when you say “add-on started fetching the data again” , does it start from the point where it left or will it start from the beginning again ?
yes, it starts from the latest imported revision, not from the very beginning.
hi Ildar,
Thanks for all your support through out. Appreciate that. But we are still facing issues.
These are currently the two projects that we are trying to pull from SVN
build - 703
src - 713
Looks we have got another issue for the 703 repository . Please find the attached logs.
log-25-06-src (66.8 KB)
I have some questions on how this work.
ISSUE-1 : What does the errors in above log file suggest . Is it something to worry about.
ISSUE-2 : From the SVNMIRROR.log of both the repos (703 & 713), I understand these are pulling branches from the root of our SVN repo rather than the individual project folders. (But I have actually selected different project folders when I have started the import) .
Here is what we have and I have initiated two mirrors for both the repos.
But looks like from the log file , it is getting branches from the root SVN repo and not individual SVN repos.
703- svnmirror log file [build]
2021-06-25 05:55:46,743 sync - successfully received 'branches/PR_025536/branches/P2672_Layer_Tuning_Offset_Table/system/equipment/pm1/equipment/ebr1/generator_power_enable_switch/definition.xml' with size=224
713- svnmirror log file
2021-06-25 03:04:02,990 sync - Switch from http://nexus.novellus.com/svn/branches/SIOCSII_01_XX_MAINTENANCE to http://nexus.novellus.com/svn/branches/PR_025536
Im confused how can I know if its pulling branches from root SVN repo or individual SVN repos.
Hi Santosh,
the “Missing unknown” error is definitely one that worths to be worried about. It means that the add-on expected to find an object in the repository (most probably previously imported) but for some reason that object is missing in the repository. That definitely means that something went wrong and data in Bitbucket incomplete. The reason for the error is not clear, however, the part of the log you sent does not reveal it. Such problems are often caused by files permissions, for example, so it may worth to check the server for that.
As for the branches – judging from the same log, the URL is set in the following way:
url = http://nexus.novellus.com/svn
and the branch mapping is
trunk = trunk:refs/heads/master
branches = branches/*:refs/heads/*
tags = tags/*:refs/tags/*
shelves = shelves/*:refs/shelves/*
for the repository 703 (which is the log was collected from). Such a configuration actually means that the add-on will translate the whole repository to Git instead of an individual directory. To translate an SVN directory to a separate Bitbucket project, the URL should be set like this:
url = http://nexus.novellus.com/svn/build
and the mapping configuration should be addicted to reflect the build directory content. If you want the whole directory content to appear in the master branch in Git, the mapping configuration should be set like this:
trunk = :refs/heads/master
or URL and mapping can be set in the following way:
url = http://nexus.novellus.com/svn
trunk = build:refs/heads/master
in both cases the build content would appear in master branch in Bitbucket which would be the only branch in the repository.
I’m not sure about repository 713 since I don’t have logs from that one, but if it download more branches than it should, most probably the URL and mapping are incorrect there, too.
So to resolve both issues the import should be stopped both repositories and re-configured correctly.
hi Team ,
Did you guys identify the root cause on why this greying out would happen when the initial configuration is in progress.
This is the current situation - Currently the svn initial configuration is in progress
screenshot from IE tab - where svn initial configuration is happening .
screenshot from any other tab / browser.
Funny thing is ,
-
I am able to give keyboard controls , by pressing TAB on the keyboard, where it will go from one field to another field.
-
URL information / username information / trunk information and everything is VANISHED and not observed
Did you observe this issue with other customers as well ? If yes are we working on any fix ? What should be the course of action in such cases ?
Hi Santosh,
honestly, I didn’t completely get what is the issue here? Previously you reported an issue with a repository where the configuration stage was not successful and the auto-configuration was restarting constantly. But it looks it’s not the case here, right?
If the question is only about the UI greyed out, then it’s expected, at least at the stage show on you first screenshot – it looks as if all the needed information was provided and not the add-on fetches the history to prepare the configuration and shows that modal progress bar window which should be closed once the history is fetched. Is that the only thing that bothers you or it suffers from other issues, too?