33

This has something that's just started happening recently, although I'm not sure what I could have done to trigger it.

Whenever I run a git push I get the following error:

ERROR: ld.so: object '/lib/liblm.so' from LD_PRELOAD cannot be preloaded: ignored.

The push does procede after that and works correctly.

I've updated to the latest version of Git (via homebrew) and that didn't solve it.

EDIT: Apologies, I wasn't very clear exactly what I was asking. I guess my question is two fold:

  • Out of interest, what is causing the error?
  • How can I fix the error so it goes away? It doesn't seem to be causing any problems that I can see, but it's a bit irritating!
Jack Franklin
  • 3,765
  • 6
  • 26
  • 34
  • 1
    Are you pushing to GitHub? I'm getting the exact same error. Asked on #github but no response yet. – Trevor Norris Jan 09 '13 at 08:00
  • 2
    I just noticed this too. Happens only when remote is GitHub. – n0nick Jan 09 '13 at 08:01
  • 2
    That's what I figured since the message was coming through the server response. Must be a configuration mishap in their end. – Trevor Norris Jan 09 '13 at 08:02
  • 2
    Also occurring when doing `git pull` for me. – terje Jan 09 '13 at 08:03
  • worth a read http://stackoverflow.com/questions/426230/what-is-the-ld-preload-trick – amitchhajer Jan 09 '13 at 08:11
  • 1
    Guestimate from the number of upvotes and people in this question: Working hours started 10 minutes ago in Europe :-) – yas4891 Jan 09 '13 at 08:12
  • This question is not really a good fit for SO, it attracts a lot of me too answers and it's not really possible to answer this question – Ikke Jan 09 '13 at 08:17
  • Fixed by GitHub :) Try git pull to check it.. – Svetoslav Jan 09 '13 at 08:21
  • Got the same message, but the fine folks at github.com seem to have fixed it now. – thomax Jan 09 '13 at 08:21
  • @Ikke it was not originally obvious that this is a remote issue... It looks like a general system problem, and I for one found this SO page very informative regarding that. – n0nick Jan 09 '13 at 08:30
  • Yeah, but this question is hardly relevant anymore, fitting the criteria of too localized. – Ikke Jan 09 '13 at 08:38
  • @Ikke - I think the question "what does this error message mean and why might I receive it" is still relevant. In this particular case, it just happens that the reason for receiving it is unknown, since it's caused by GitHub. – James Allardice Jan 09 '13 at 08:41
  • But all the answers point to a temporal glitch and wont be of any use to anyone coming here in the future. – Ikke Jan 09 '13 at 09:38
  • This appears to be an issue at GitHub, not a problem on your end. You didn't do anything to trigger it and can't do anything to resolve it, so just ignore the warnings and wait for GitHub to repair things on their end. – Dave Sherohman Jan 09 '13 at 08:10
  • This is not that localized, actually. Pretty common thing to run into. Voting to reopen. –  Jan 29 '13 at 21:28

1 Answers1

9

I have to assume it's a server mis-configuration. The message is originating from the GitHub server. So rest assured it has nothing to do with your git.

For anyone who cares, here's a good SO explanation for LD_PRELOAD: https://stackoverflow.com/a/426260/591166

Update: GitHub has apparently fixed the issue.

Community
  • 1
  • 1
Trevor Norris
  • 20,499
  • 4
  • 26
  • 28