From: Thomas Adam <thomas@xteddy.org>
To: git list <git@vger.kernel.org>
Subject: Certain git commands fail with "returned error: 128" running via Git.pm under mod_perl
Date: Thu, 15 Apr 2010 10:22:41 +0100 [thread overview]
Message-ID: <x2k18071eea1004150222x2980feb5ub9b15ec0522dd5ff@mail.gmail.com> (raw)
Hello all,
I've got a problem running certain git commands via Git.pm under
mod_perl. Specifically so far, these commands are "push" and "fetch"
(by way of "git pull"). Running the same command set without mod_perl
works as expected, including running these commands manually.
I won't bother to describe the application, but most web pages within
it will "git pull" and "git push" various bits of information once
they're entered. When I initially try this out, these commands work
fine, until a point in time when they stop and error with the
following:
trace: built-in: git 'push'
trace: run_command: 'git-receive-pack '\''/var/repository'\'''
trace: exec: 'sh' '-c' 'git-receive-pack '\''/var/repository'\'''
'git-receive-pack '\''/var/repository'\'''
trace: built-in: git 'receive-pack' '/var/repository'
fatal: read error: Bad file descriptor
fatal: write error: Broken pipe
Git command failure: push: command returned error: 128
Note that in the environment, I have enabled "GIT_TRACE=1", so that I
could at least make some sense of what's going on. When this happens
-- git will remain failing on this command until I restart Apache.
I said I am using Git.pm -- I am doing nothing fancy other than calling:
Git::command()
What do people think is happening? The fact that it's intermittent
would suggest to me there's either some global state running these
commands under mod_perl -- and perhaps the reason push returns error
128 with a broken pipe is that it's trying to write to a file handle
that's since closed (STDOUT or STDERR)? It's a little tricky knowing
where/how to diagnose this.
So any help/pointers would be greatly appreciated.
Kindly,
-- Thomas Adam
reply other threads:[~2010-04-15 9:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x2k18071eea1004150222x2980feb5ub9b15ec0522dd5ff@mail.gmail.com \
--to=thomas@xteddy.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).