Bryan Veloso

Tag: Git

  • Bitbucket Connection Refused / No Route to Host (Siteground Server)

    If you recently encountered this issue when pushing a your git updates to Bitbucket and you’re using Siteground as your server, then you found your solution. I recently encountered this issue in my multiple Siteground hosts, using shared or cloud SG servers.

    Not really sure if this is a Siteground issue or a Bitbucket issue, but changing the port via config works.

    One solution I found online is adding 104.192.143.2 bitbucket.org to your /etc/hosts file. But sadly, at Siteground GoGeek servers, you have limited access and you cannot access your hosts file.

    If you’re getting a No Route to Host error, or a Connection Refused error when trying to push repo updates/commits.

    Just go to your .ssh/config file (create one if you don’t have one yet), and add these lines:

    Host bitbucket.org
    Hostname altssh.bitbucket.org
    Port 443

    No need to thank me. I just found the solution here by oliverkocsis.
    https://jira.atlassian.com/browse/BCLOUD-9519

  • git: User was holding a relation lock for too long

    git: User was holding a relation lock for too long

    Screen Shot 2016-06-16 at 10.06.11 AM
    If you encountered this error while pushing your recent change to your git repo, worry not. You’re not alone. Just recently, like a few minutes ago, I’m having trouble pushing my latest commit to my Bitbucket repo. Good thing I found out that it’s just a bitbucket issue, not really an issue with my repo or with my server or with my localhost.

    Below is the exact error I’m getting while trying to push my latest commits:
    remote: canceling statement due to conflict with recovery
    remote: LINE 1: …er”.”date_joined” FROM “bb_repository” INNER JOIN “auth_user…
    remote: DETAIL:  User was holding a relation lock for too long.
     ! [remote rejected] master -> master (pre-receive hook declined)

    I actually tried pushing it again and again, switch branches, cloned a new repo, but no can do. Nothing I tried worked, it’s because Bitbucket is having issues, not me. Haha!

    Let’s just wait for Bitbucket to fix the issue and not panic.

  • Git Push Error: fatal: Out of memory, malloc failed

    Git Push Error: fatal: Out of memory, malloc failed

    git
    If you encountered a fatal: Out of memory, malloc failed error after pushing your local repo to your remote repo, then you tried over and over again to push it but to no avail, then you’re pretty lucky to have found this blog post.
    (more…)