- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-17-2022 09:58 AM
We've been working with Studio connected to out BitBucket git repos without issues for a while.
But as of today, all the git operations fail with the message "The repo cannot be accessed. Check URL, username, and password, and confirm user has read, write, and create branch access".
Our git connection settings have not changed, and they work fine from other instances.
We see the below exception in the logs, the relevant piece of which seems to be:
"java.security.AccessControlException: access denied ("java.io.FilePermission" "/var/empty/glide/.config/jgit/config" "read"):"
Has anyone come across this before? Is there any workaround / fix?
Thanks in advance:
Ignacio
Full exception trace:
The repo cannot be accessed. Check URL, username, and password, and confirm user has read, write, and create branch access: com.glide.sourcecontrol.SourceControlException: java.security.AccessControlException: access denied ("java.io.FilePermission" "/var/empty/glide/.config/jgit/config" "read"): com.glide.sourcecontrol.AGitRepository.loadGit(AGitRepository.java:233)
com.glide.sourcecontrol.AGitRepository.getCurrentBranch(AGitRepository.java:1056)
com.glide.sourcecontrol.worker.git.GitTestConnectionWorker.checkReadAccess(GitTestConnectionWorker.java:265)
com.glide.sourcecontrol.worker.git.GitTestConnectionWorker.isValidRemoteRepository(GitTestConnectionWorker.java:114)
com.glide.sourcecontrol.worker.git.GitTestConnectionWorker.isValidRemote(GitTestConnectionWorker.java:356)
com.glide.sourcecontrol.worker.git.GitTestConnectionWorker.execute(GitTestConnectionWorker.java:86)
com.glide.sourcecontrol.worker.RegisterRepositoryWorker.execute(RegisterRepositoryWorker.java:249)
com.glide.sourcecontrol.SourceControlWorker.startWork(SourceControlWorker.java:46)
com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:126)
com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:26)
com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59)
com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:129)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:132)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:116)
com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:338)
com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$0(SchedulerWorkerThread.java:220)
com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:220)
com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:101)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2022 09:34 AM
Well, the problem went away on its own.... good, I guess, but not ideal. Closing this anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2022 09:34 AM
Well, the problem went away on its own.... good, I guess, but not ideal. Closing this anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2022 09:20 PM
Hi Kilo,
I have also come across the same issue - We had a connection to Azure DevOps Repo which was working fine until yesterday and all of a sudden we started getting this error message 'The repo cannot be accessed. Check URL, username, and password, and confirm user has read, write, and create branch access' did you get any further info on what was causing this?
Thanks
Sravan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2022 01:03 AM
Hi:
We never got any definite info on what was causing the problem. As I mentioned above, the connection started working again after a few days without any action on our side :(.
I would recommend that you check for the same stack trace that I found on the logs. If you can see it, it's probably the same issue. If not, it may be something else.
Ignacio
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-06-2023 06:20 AM
Facing the same issue myself now, nothing has changed on the repo but it just stopped working on our Servicenow instance