{"id":367,"date":"2014-08-18T00:00:00","date_gmt":"2014-08-18T00:00:00","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2014\/08\/18\/git-troubleshooting\/"},"modified":"2021-11-19T09:07:19","modified_gmt":"2021-11-19T09:07:19","slug":"git-troubleshooting","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/git-troubleshooting\/","title":{"rendered":"Git Troubleshooting | Git Troubleshooting Techniques"},"content":{"rendered":"

<\/p>\n

<\/p>\n

\"git-troubleshooting\"<\/p>\n

export GIT_CURL_VERBOSE=1<\/p>\n

git push -u origin –all –verbose<\/span><\/p>\n

git config –list<\/p>\n

&<\/p>\n

GIT_CURL_VERBOSE=1 git push<\/p>\n

&<\/p>\n

export GIT_CURL_VERBOSE=1<\/p>\n

git push<\/p>\n

git config --global http.postBuffer<\/span><\/code><\/p>\n

There are useful to debug, long running Git Commands or Git Commands that seem to be hanged for some reason,<\/p>\n

Git has an in-built functionality for us to peek into what is running behind the scenes of a git command, just add GIT_TRACE=1 before ANY git command to get additional info, for example:<\/p>\n

Other Flags that we can use are : GIT_CURL_VERBOSE=1, -v or \u2013verbose<\/p>\n

[server@user sp-server-branches]$ GIT_TRACE=1 git clone<\/p>\n

https:\/\/github.com\/gitlabhq\/gitlab-public-wiki\/wiki\/Trouble-Shooting-Guide<\/a><\/p>\n

https:\/\/drupal.org\/node\/1065850<\/a><\/p>\n

http:\/\/mattberther.com\/2013\/12\/29\/pushing-large-git-repos-with-ssh<\/a><\/p>\n

http:\/\/ocaoimh.ie\/2008\/12\/10\/how-to-fix-ssh-timeout-problems\/<\/a><\/p>\n

http:\/\/unix.stackexchange.com\/questions\/3026\/what-do-the-options-serveraliveinterval-and-clientaliveinterval-in-sshd-conf<\/a><\/p>\n\n