# Unable to create a branch

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969>\
**Category:** Rose/Cylc and FCM\
**Created:** [13 April 2023 13:05 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969 "2023-04-13T13:05:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gwy](https://avatars.discourse-cdn.com/v4/letter/g/8e8cbc/32.png) [@gwy](https://cms-helpdesk.ncas.ac.uk/u/gwy)\
**Post date:** [13 April 2023 13:05 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/1 "2023-04-13T13:05:44Z")

</div>

Dear CMS help desk,

I have been trying to create a branch in the MET office repository and I have created a ticket for it. However I still can not create it. The error message is  
[FAIL] svn info --xml [https://code.metoffice.gov.uk/svn/jules/main/trunk@24333](https://code.metoffice.gov.uk/svn/jules/main/trunk@24333) # rc=1  
[FAIL] svn: E170013: Unable to connect to a repository at URL ‘[https://code.metoffice.gov.uk/svn/jules/main/trunk](https://code.metoffice.gov.uk/svn/jules/main/trunk)’  
[FAIL] svn: E215004: No more credentials or we tried too many times.  
[FAIL] Authentication failed  
I can copy a branch to my local environment no problem. Could you take a look.  
Thanks

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [13 April 2023 14:20 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/2 "2023-04-13T14:20:44Z")

</div>

Have you set up caching of your MOSRS credentials?

Which machine is this on?

Regards  
Ros

---

<div class="post-metadata">

**Author:** ![pmcguire](https://avatars.discourse-cdn.com/v4/letter/p/b782af/32.png) [@pmcguire](https://cms-helpdesk.ncas.ac.uk/u/pmcguire)\
**Post date:** [13 April 2023 14:22 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/3 "2023-04-13T14:22:01Z")

</div>

Hi Wenyao:  
What command are you trying to use that generates the error message?  
Is this on JASMIN?  
Is it on the cylc1 Virtual Machine of JASMIN?

I had trouble caching my MOSRS password earlier today on cylc1 on JASMIN. It wouldn’t ask me for an MOSRS password when I logged in to cylc1. Does it ask you for an MOSRS password?  
If it doesn’t ask for an MOSRS password, then in order to fix this, I needed to kill and restart my gpg-agent by doing this:

1. ssh to cylc1
2. ps -elf | grep $USER
3. search for the PID of gpg-agent
4. kill -9 PID  
(where PID is the the PID of the gpg-agent)
5. log out of cylc1 and log back in. It should now ask for a MOSRS password.

Does this help?  
Patrick McGuire

---

<div class="post-metadata">

**Author:** ![gwy](https://avatars.discourse-cdn.com/v4/letter/g/8e8cbc/32.png) [@gwy](https://cms-helpdesk.ncas.ac.uk/u/gwy)\
**Post date:** [13 April 2023 14:56 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/4 "2023-04-13T14:56:37Z")

</div>

Dear Patrick,

Thanks for your help. This has been solved. I firstly tried . mosrs-setup-gpg-agent and it is caching ok. But the problem still exists. Then I tried the mosrs-cache-password together. The problem does not pop up again.

Thanks.

---

<div class="post-metadata">

**Author:** ![gwy](https://avatars.discourse-cdn.com/v4/letter/g/8e8cbc/32.png) [@gwy](https://cms-helpdesk.ncas.ac.uk/u/gwy)\
**Post date:** [13 April 2023 14:57 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/5 "2023-04-13T14:57:20Z")

</div>

it happened when I tried to create a branch as well as ‘fcm commit’ on the cylc1 on login2.

---

<div class="post-metadata">

**Author:** ![pmcguire](https://avatars.discourse-cdn.com/v4/letter/p/b782af/32.png) [@pmcguire](https://cms-helpdesk.ncas.ac.uk/u/pmcguire)\
**Post date:** [13 April 2023 15:11 UTC](https://cms-helpdesk.ncas.ac.uk/t/unable-to-create-a-branch/969/6 "2023-04-13T15:11:27Z")

</div>

Hi Wenyao  
Well, if the problem went away, as you say, then it was some sort of temporary internal problem.  
But if it does come back, then let us know.  
Patrick
