git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Error logging for git over ssh?

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jan 14, 2014, 18:44 UTC
Message-ID
<CACPiFCKBK49Zm8oYcGMVfmsgRwDrPyzWcU7vM6DwJeQitBNsnA@mail.gmail.com>

Diagnosing errors with git over ssh has historically required tooling up for debugging or looking at things from the client side, because git does not log anything on the server side.

It would be a boon to those running busy git servers to be able to diagnose by looking at a log. It can be both old-fashioned, or very modern (if you are using journald).

After digging around the mailing list, current git master and "what's cooking", I fail to see anything. Is there a built-in way in modern git to direct stderr on the server side to a logger or to a file? (I see git-daemon has some support, but it does not handle git ssh connections...)

Some common "use cases" I've had to debug the hard way:
 - a ref is not up to date and the server rejects non-FF pushes
 - perms issues over objects or refs
 - ENOSPC
 - refs have a stale .lock file
cheers,
m
-- 
 martin.langhoff@gmail.com
 -  ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 ~ http://docs.moodle.org/en/User:Martin_Langhoff
Next: Duy Nguyen
Message 1 of 3 in “Error logging for git over ssh?”
  1. Martin LanghoffJan 14, 2014
  2. Duy NguyenJan 15, 2014
  3. Martin LanghoffJan 15, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.