0

I have been developing a web app on Microsoft Azure with a Git repository using Node.js and AngularJS.

It has been deploying successfully for the past few weeks and then today, I have added a small animation to the page using ng-show and @keyframes. When attempting to push these changes to the git, I get the following output:

C:\Users\Alexander\Documents\Azure\AlexH>git push origin master
Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (10/10), done.
Writing objects: 100% (13/13), 49.24 KiB | 0 bytes/s, done.
Total 13 (delta 6), reused 10 (delta 3)
efrror: RPC failed; result=56, HTTP code = 0
atal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I have read that this was due to the HTTP post buffer limit so I have attempted the following, giving no improvement:

git config http.postBuffer 524288000

I have also restarted the web app through the Azure Portal and retried the push, again giving no improvement.

I'd appreciate any help you can provide to resolve this.

Alxandir
  • 3
  • 3
  • Can you share your site name, either directly or [indirectly](https://github.com/projectkudu/kudu/wiki/Reporting-your-site-name-without-posting-it-publicly)? This will help us investigate. Also, include the time of the deployment. – David Ebbo Sep 25 '15 at 17:54
  • @DavidEbbo I've set up a dummy app called dummy112233. I last attempted a deployment at around 5pm I believe but I was trying it all afternoon ever since my original post. – Alxandir Sep 25 '15 at 19:53

2 Answers2

1

Looking at last deployment (commit id starts with 4d00), it seems it was successful. Could it be that for some reason the client disconnected (for some reason), but that the deployment is actually working fine?

Please try going to the deployment list in the portal, so check whether it all looks successful. I suspect it will.

David Ebbo
  • 42,443
  • 8
  • 103
  • 117
  • The commit was still in my local repository so would not have shown up in the deployment as that id is for the previous push which worked. While looking at the git log on my computer, it attempted the git push again and it was successful. The only change I have made is that I am now on different WiFi since I have changed locations. What would cause this problem with other wifi hotspots? – Alxandir Sep 26 '15 at 02:24
  • Ah, you're right it failed so early that the server would not have started processing it. One thing I would try: try pushing the same repo from the 'bad' wifi to a GitHub repo, using https to match Azure (i.e. not using ssh). It it fails for it as well, then it may be some flakiness with that wifi. – David Ebbo Sep 27 '15 at 00:10
  • Apologies for the delay but I have been doing some development at university through the eduroam student wifi (which is generally very fast) and until now been having no bother with my pushes. I have since started a new web app on my azure account and am having this same RPC failed issue that I saw previously. This is strange since I have been successfully pushing from the same wifi to my first project. – Alxandir Oct 02 '15 at 12:30
  • Did you try the GitHub test suggested in my previous comment? – David Ebbo Oct 02 '15 at 16:11
  • You were right to have me try that. It also didn't push to github so I ended up setting up the ethernet and that fixed the problem. Thanks! – Alxandir Oct 02 '15 at 16:36
0

In a similar post, see Github Push Error: RPC failed; result=22, HTTP code = 413

the solution was to either reconfigure your webserver or to switch protocol (push via ssh instead of https).

You might want to try one of these solutions...

Community
  • 1
  • 1
BartBog
  • 1,889
  • 14
  • 28