From: Christian <crich-ml@beronet•com>
To: git@vger•kernel.org
Subject: http push Lock
Date: Fri, 27 Apr 2007 11:07:23 +0200 [thread overview]
Message-ID: <4631BD4B.8040507@beronet.com> (raw)
Hi ,
after another git-http-push segfault i have a funny lock in the central
repository left, that was not released unfortunately, my apache error
log says something like:
[Fri Apr 27 11:11:08 2007] [error] [client 217.86.133.46] Could not LOCK
/git/mISDN.git/info/refs due to a failed precondition (e.g. other
locks). [423, #0]
[Fri Apr 27 11:11:08 2007] [error] [client 217.86.133.46] Existing
lock(s) on the requested resource prevent an exclusive lock. [423, #0]
[Fri Apr 27 11:11:17 2007] [error] [client 217.86.133.46] Could not LOCK
/git/mISDN.git/refs/heads/master due to a failed precondition (e.g.
other locks). [423, #0]
[Fri Apr 27 11:11:17 2007] [error] [client 217.86.133.46] Existing
lock(s) on the requested resource prevent an exclusive lock. [423, #0]
how can i resolve this locked situation? pushes are currently not
possible anymore...
The segfault is the same like last time i think:
Loaded symbols for /lib/tls/libnss_dns.so.2
#0 decode_tree_entry (desc=0xbfaed7bc, buf=0x0, size=503) at tree-walk.c:10
10 while ((c = *str++) != ' ') {
(gdb) bt
#0 decode_tree_entry (desc=0xbfaed7bc, buf=0x0, size=503) at tree-walk.c:10
#1 0x0804b9a8 in mark_tree_uninteresting (tree=0x80d0240) at revision.c:65
#2 0x080534cd in main (argc=2, argv=Cannot access memory at address 0x1fb
) at http-push.c:1998
(gdb)
next reply other threads:[~2007-04-27 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 9:07 Christian [this message]
2007-04-27 9:19 ` http push Lock Christian
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=4631BD4B.8040507@beronet.com \
--to=crich-ml@beronet$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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