public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
* can not clone via git:// anymore
@ 2009-03-04 11:24 Hinko Kocevar
  2009-03-04 12:59 ` Michael J Gruber
  0 siblings, 1 reply; 5+ messages in thread
From: Hinko Kocevar @ 2009-03-04 11:24 UTC (permalink / raw)
  To: git

Hi,

I've recently discovered that my GIT repository is not letting me clone it via git clone git://.
It works using git clone git@.. (SSH) but with GIT protocol..

Here is the case:
hinkok@alala /tmp $ git --version
git version 1.6.0.6
hinkok@alala /tmp $ git clone git://zidar/sdk.git
Initialized empty Git repository in /tmp/sdk/.git/
fatal: The remote end hung up unexpectedly

My earlier clone (few months old) has this in .git/config:
hinkok@alala /work/git/sdk.git $ cat .git/config 
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[remote "origin"]
	url = git@zidar:repositories/sdk.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master


But I remember cloning via SSH that time, because I needed git push to work,
but now other developer do not need the SSH access, but only GIT read-only -
they can only clone, not push.

I do not administer the server git repos is located on, so I must have some
information before I attack the admin..

Thank you,
Hinko

-- 
Hinko Kočevar, OSS developer
ČETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel     ++386 (0) 4 280 66 03
e-mail  hinko.kocevar@cetrtapot•si
http    www.cetrtapot.si

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: can not clone via git:// anymore
  2009-03-04 11:24 can not clone via git:// anymore Hinko Kocevar
@ 2009-03-04 12:59 ` Michael J Gruber
  2009-03-04 13:28   ` Hinko Kocevar
  0 siblings, 1 reply; 5+ messages in thread
From: Michael J Gruber @ 2009-03-04 12:59 UTC (permalink / raw)
  To: Hinko Kocevar; +Cc: git

Hinko Kocevar venit, vidit, dixit 04.03.2009 12:24:
> Hi,
> 
> I've recently discovered that my GIT repository is not letting me clone it via git clone git://.
> It works using git clone git@.. (SSH) but with GIT protocol..
> 
> Here is the case:
> hinkok@alala /tmp $ git --version
> git version 1.6.0.6
> hinkok@alala /tmp $ git clone git://zidar/sdk.git
> Initialized empty Git repository in /tmp/sdk/.git/
> fatal: The remote end hung up unexpectedly
> 
> My earlier clone (few months old) has this in .git/config:
> hinkok@alala /work/git/sdk.git $ cat .git/config 
> [core]
> 	repositoryformatversion = 0
> 	filemode = true
> 	bare = false
> 	logallrefupdates = true
> [remote "origin"]
> 	url = git@zidar:repositories/sdk.git
> 	fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
> 	remote = origin
> 	merge = refs/heads/master
> 
> 
> But I remember cloning via SSH that time, because I needed git push to work,
> but now other developer do not need the SSH access, but only GIT read-only -
> they can only clone, not push.
> 
> I do not administer the server git repos is located on, so I must have some
> information before I attack the admin..

Sorry in case this is trivial, but has git: access ever worked? It
requires a git daemon running on the server, whereas ssh access does not
require that. git@zidar:repositories/sdk.git uses ssh access.

Michael

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: can not clone via git:// anymore
  2009-03-04 12:59 ` Michael J Gruber
@ 2009-03-04 13:28   ` Hinko Kocevar
  2009-03-04 14:24     ` Jeff King
  0 siblings, 1 reply; 5+ messages in thread
From: Hinko Kocevar @ 2009-03-04 13:28 UTC (permalink / raw)
  To: Michael J Gruber; +Cc: git

Michael J Gruber wrote:
> Hinko Kocevar venit, vidit, dixit 04.03.2009 12:24:
>> Hi,
>>
>> I've recently discovered that my GIT repository is not letting me clone it via git clone git://.
>> It works using git clone git@.. (SSH) but with GIT protocol..
>>
>> Here is the case:
>> hinkok@alala /tmp $ git --version
>> git version 1.6.0.6
>> hinkok@alala /tmp $ git clone git://zidar/sdk.git
>> Initialized empty Git repository in /tmp/sdk/.git/
>> fatal: The remote end hung up unexpectedly
>>
>> My earlier clone (few months old) has this in .git/config:
>> hinkok@alala /work/git/sdk.git $ cat .git/config 
>> [core]
>> 	repositoryformatversion = 0
>> 	filemode = true
>> 	bare = false
>> 	logallrefupdates = true
>> [remote "origin"]
>> 	url = git@zidar:repositories/sdk.git
>> 	fetch = +refs/heads/*:refs/remotes/origin/*
>> [branch "master"]
>> 	remote = origin
>> 	merge = refs/heads/master
>>
>>
>> But I remember cloning via SSH that time, because I needed git push to work,
>> but now other developer do not need the SSH access, but only GIT read-only -
>> they can only clone, not push.
>>
>> I do not administer the server git repos is located on, so I must have some
>> information before I attack the admin..
> 
> Sorry in case this is trivial, but has git: access ever worked? It

It did. I found this repos on the server that used git to checkout the repo:
CETRTAPOT\zidarhw@zidar:~$ cat sdk/.git/config 
[core]
	repositoryformatversion = 0
	filemode = true
	bare = false
	logallrefupdates = true
[remote "origin"]
	url = git://zidar/sdk.git
	fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
	remote = origin
	merge = refs/heads/master


> requires a git daemon running on the server, whereas ssh access does not
> require that. git@zidar:repositories/sdk.git uses ssh access.
> 
> Michael

git-daemon was/is running:

CETRTAPOT\zidarhw@zidar:~$ ps -ef | grep git
root      3207     1  0 14:15 ?        00:00:00 runsvdir -P /etc/service log: d user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?
root      3208  3207  0 14:15 ?        00:00:00 runsv git-daemon
root      3373  3208  0 14:16 ?        00:00:00 git-daemon --verbose --base-path=/var/cache /var/cache/git
11418     3399  2762  0 14:16 pts/0    00:00:00 grep git

But after doing:
/etc/init.d/git-daemon stop
/etc/init.d/git-daemon start

Nothing much happened (this is on Ubuntu 8.04.1)!

After a while I managed to get git-daemon to die properly
- '/etc/init.d/git-daemon stop' didn't do that. After
'/etc/init.d/git-daemon start' the git clone git://.. works!


hinkok@alala /tmp $ git clone git://zidar/sdk.git
Initialized empty Git repository in /tmp/sdk/.git/
remote: Counting objects: 62636, done.
remote: Compressing objects: 100% (49201/49201), done.
Receiving objects:  40% (25055/62636), 59.97 MiB | 11069 KiB/s   

Thank your for the 'obvious' I haven't checked myself!

Best regards,
Hinko

--
Hinko Kočevar, OSS developer
ČETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel     ++386 (0) 4 280 66 03
e-mail  hinko.kocevar@cetrtapot•si
http    www.cetrtapot.si

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: can not clone via git:// anymore
  2009-03-04 13:28   ` Hinko Kocevar
@ 2009-03-04 14:24     ` Jeff King
  2009-03-05  9:16       ` Hinko Kocevar
  0 siblings, 1 reply; 5+ messages in thread
From: Jeff King @ 2009-03-04 14:24 UTC (permalink / raw)
  To: Hinko Kocevar; +Cc: Michael J Gruber, git

On Wed, Mar 04, 2009 at 02:28:40PM +0100, Hinko Kocevar wrote:

> git-daemon was/is running:
> 
> CETRTAPOT\zidarhw@zidar:~$ ps -ef | grep git
> root      3207     1  0 14:15 ?        00:00:00 runsvdir -P /etc/service log: d user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?
> root      3208  3207  0 14:15 ?        00:00:00 runsv git-daemon
> root      3373  3208  0 14:16 ?        00:00:00 git-daemon --verbose --base-path=/var/cache /var/cache/git
> 11418     3399  2762  0 14:16 pts/0    00:00:00 grep git

See all the runsvdir errors? That probably means that git-daemon's log
output is going nowhere, since the log is not running. Which means
eventually the pipe from git-daemon to the log will get full, and
git-daemon will block writing out the log. And then stop dealing with
requests.

So even if restarting helps now, it may fill up again unless you fix the
logging problem (presumably by creating the right "gitlog" user).

-Peff

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: can not clone via git:// anymore
  2009-03-04 14:24     ` Jeff King
@ 2009-03-05  9:16       ` Hinko Kocevar
  0 siblings, 0 replies; 5+ messages in thread
From: Hinko Kocevar @ 2009-03-05  9:16 UTC (permalink / raw)
  To: Jeff King; +Cc: Michael J Gruber, git

Jeff King wrote:
> On Wed, Mar 04, 2009 at 02:28:40PM +0100, Hinko Kocevar wrote:
> 
>> git-daemon was/is running:
>>
>> CETRTAPOT\zidarhw@zidar:~$ ps -ef | grep git
>> root      3207     1  0 14:15 ?        00:00:00 runsvdir -P /etc/service log: d user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?chown: invalid user: `gitlog:adm'?
>> root      3208  3207  0 14:15 ?        00:00:00 runsv git-daemon
>> root      3373  3208  0 14:16 ?        00:00:00 git-daemon --verbose --base-path=/var/cache /var/cache/git
>> 11418     3399  2762  0 14:16 pts/0    00:00:00 grep git
> 
> See all the runsvdir errors? That probably means that git-daemon's log
> output is going nowhere, since the log is not running. Which means
> eventually the pipe from git-daemon to the log will get full, and
> git-daemon will block writing out the log. And then stop dealing with
> requests.
> 
> So even if restarting helps now, it may fill up again unless you fix the
> logging problem (presumably by creating the right "gitlog" user).

I added the 'gitlog' user yesterday too, when I noticed that unusual runsvdir line.

ps output:
CETRTAPOT\zidarhw@zidar:~$ ps -ef | grep git
git       5547     1  0 Mar04 ?        00:00:00 /usr/bin/git-daemon --reuseaddr --verbose --detach --base-path=/home/git/repositories/ --export-all

Thank you!

-- 
Hinko Kočevar, OSS developer
ČETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel     ++386 (0) 4 280 66 03
e-mail  hinko.kocevar@cetrtapot•si
http    www.cetrtapot.si

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2009-03-05  9:20 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-03-04 11:24 can not clone via git:// anymore Hinko Kocevar
2009-03-04 12:59 ` Michael J Gruber
2009-03-04 13:28   ` Hinko Kocevar
2009-03-04 14:24     ` Jeff King
2009-03-05  9:16       ` Hinko Kocevar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox