{"thread":{"id":"16461","subject":"inted problems when upgrading to 1.6.0.4","startedAt":"2008-11-25T09:29:14Z","lastAt":"2008-11-25T11:14:34Z","messageCount":8,"participants":["Luis Gutierrez","Arafangion","Johannes Sixt","Brian Foster"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"96464","messageId":"492BC56A.6040506@xmos.com","threadId":"16461","inReplyTo":null,"subject":"inted problems when upgrading to 1.6.0.4","fromName":"Luis Gutierrez","fromEmail":"luis.gutierrez@xmos.com","sentAt":"2008-11-25T09:29:14Z","receivedAt":"2008-11-25T09:29:14Z","isPatch":false,"sender":{"key":"luis.gutierrez@xmos.com","avatar":null},"body":"Hi All,\n\nAt my company we have been using git for the past months, and except for \na few people, everyone is happy with it. Last week, we discovered that \nthe mac version of git was misbehaving (v1.5.6.4), but upgrading the \nclient to the latest one (v1.6.0.4) fixed the issue. Fearing consistency \nissue between version, I decided to update the version of the central \nrepository (ie, the place were people can go and synchronize their code) \non a RHEL4 box from 1.5.6.4 to 1.6.0.4.\nwent to my git directory, pulled, checkout v1.6.0.4, and compiled with \n'make --prefix=/usr/loca/ all' and installed with the same comamnd. \nxinted dameon was restarted and then all hell broke loose.\n\nAll push/pull/clone operations were failing with the dreaded 'fatal: The \nremote end hung up unexpectedly'. After a few tests, this is what I found:\n\n- I can clone/pull/push if I do it through ssh (ie, git clone \nssh://server/project)\n- I can clone/pull/push if I start git daemon on the command line through\ngit daemon --syslog --verbose --export-all \n--base-path=/vol0/git/projects --verbose --reuseaddr\n\nBut the way I had setup git, through xinetd is broken.\n\nThis is my current xinetd config:\nservice git\n{\n    disable      = yes\n    socket_type  = stream\n    wait         = no\n    user         = git\n    type         = UNLISTED\n    protocol     = tcp\n    log_on_failure    += USERID\n    port         = 9418\n    server       = /usr/local/bin/git\n    server_args  = daemon --inetd --syslog --verbose --export-all \n--base-path=/vol0/git/projects --allow-override=uploadpack\n}\n\nAnd I'm getting the following errors:\n > git clone git://romanticism/tutorial tutorial.git\nInitialized empty Git repository in /tmp/tutorial.git/.git/\nfatal: protocol error: bad line length character\n\nbefore adding the --allow-override=uploadpack I was getting this:\n > git clone git://romanticism/tutorial tutorial.git\nInitialized empty Git repository in /tmp/tutorial.git/.git/\nfatal: The remote end hung up unexpectedly\n\nSince the error appeared after the upgrade, it seems likely it is either \na but, or something change regarding inte/xinetd, but I can't find any \ndocumentation about changes here.\n\nAny help will be appreciated.\n\nLuis Gutierrez\n"},{"id":"96466","messageId":"492BD01C.8070807@viscovery.net","threadId":"16461","inReplyTo":"492BC56A.6040506@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2008-11-25T10:14:52Z","receivedAt":"2008-11-25T10:14:52Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Luis Gutierrez schrieb:\n> At my company we have been using git for the past months, and except for\n> a few people, everyone is happy with it. Last week, we discovered that\n> the mac version of git was misbehaving (v1.5.6.4), but upgrading the\n> client to the latest one (v1.6.0.4) fixed the issue. Fearing consistency\n> issue between version, I decided to update the version of the central\n> repository (ie, the place were people can go and synchronize their code)\n> on a RHEL4 box from 1.5.6.4 to 1.6.0.4.\n> went to my git directory, pulled, checkout v1.6.0.4, and compiled with\n> 'make --prefix=/usr/loca/ all' and installed with the same comamnd.\n\nIt's not necessarily the cause of your problems, but didn't make install\nwarn you:\n\n        !! You have installed git-* commands to new gitexecdir.\n        !! Old version git-* commands still remain in bindir.\n        !! Mixing two versions of Git will lead to problems.\n        !! Please remove old version commands in bindir now.\n\nDid you do as you were told?\n\n-- Hannes\n"},{"id":"96465","messageId":"1227608420.3222.2.camel@therock.nsw.bigpond.net.au","threadId":"16461","inReplyTo":"492BC56A.6040506@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Arafangion","fromEmail":"thestar@fussycoder.id.au","sentAt":"2008-11-25T10:20:20Z","receivedAt":"2008-11-25T10:20:20Z","isPatch":false,"sender":{"key":"thestar@fussycoder.id.au","avatar":null},"body":"On Tue, 2008-11-25 at 09:29 +0000, Luis Gutierrez wrote:\n<snip>\n> All push/pull/clone operations were failing with the dreaded 'fatal: The \n> remote end hung up unexpectedly'. After a few tests, this is what I found:\n> \n> - I can clone/pull/push if I do it through ssh (ie, git clone \n> ssh://server/project)\n> - I can clone/pull/push if I start git daemon on the command line through\n> git daemon --syslog --verbose --export-all \n> --base-path=/vol0/git/projects --verbose --reuseaddr\n> \n> But the way I had setup git, through xinetd is broken.\n\nI'm just guessing, as I'm too new to the git world to respond with more\nexpertise, but I will suggest that perhaps your problem is that your\n$PATH is different with the xinitd configuration as contrasted with your\nssh configuration, as the locations of the git binaries could be\ndifferent.\n"},{"id":"96467","messageId":"200811251136.03546.brian.foster@innova-card.com","threadId":"16461","inReplyTo":"492BC56A.6040506@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Brian Foster","fromEmail":"brian.foster@innova-card.com","sentAt":"2008-11-25T10:36:03Z","receivedAt":"2008-11-25T10:36:03Z","isPatch":false,"sender":{"key":"brian.foster@innova-card.com","avatar":null},"body":"On Tuesday 25 November 2008 10:29:14 Luis Gutierrez wrote:\n>[ ... ]\n> This is my current xinetd config:\n> service git\n> {\n>     disable      = yes\n>     socket_type  = stream\n>     wait         = no\n>     user         = git\n>     type         = UNLISTED\n>     protocol     = tcp\n>     log_on_failure    += USERID\n>     port         = 9418\n>     server       = /usr/local/bin/git\n>     server_args  = daemon --inetd --syslog --verbose --export-all --base-path=/vol0/git/projects --allow-override=uploadpack\n> }\n\n   In the past I also had a problem when git was installed\n  in /usr/local/bin and git-daemon was launched from xinetd.\n  I don't recall the details now, but believe all the obvious\n  suspects (conflicting git installation, /usr/local/bin not\n  in PATH, mis-installed/mis-configured git, et al.) seemed Ok.\n  In any case, I debugged the problem by adding:\n\n     env  +=  GIT_TRACE=/tmp/LOG-git-daemon\n\n  to the xinetd config.  I suggest trying that and seeing\n  what the logfile contains.\n\ncheers!\n\t-blf-\n\np.s.  In my case, *using the information in the logfile*,\n     I eventually worked-around it by adding\n     ‘--exec-path=/usr/local/bin’ to the ‘server_args’.\n     I never did work out exactly what was going wrong (this\n     was with a self-built git v1.5.5 on CentOS release 5).\n\n-- \n“How many surrealists does it take to   | Brian Foster\n change a lightbulb? Three. One calms   | somewhere in south of France\n the warthog, and two fill the bathtub  |   Stop E$$o (ExxonMobil)!\n with brightly-coloured machine tools.” |      http://www.stopesso.com\n"},{"id":"96469","messageId":"492BD951.1010200@xmos.com","threadId":"16461","inReplyTo":"1227610459.3222.4.camel@therock.nsw.bigpond.net.au","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Luis Gutierrez","fromEmail":"luis.gutierrez@xmos.com","sentAt":"2008-11-25T10:54:09Z","receivedAt":"2008-11-25T10:54:09Z","isPatch":false,"sender":{"key":"luis.gutierrez@xmos.com","avatar":null},"body":"Arafangion wrote:\n> On Tue, 2008-11-25 at 10:12 +0000, Luis Gutierrez wrote:\n>   \n>> Arafangion wrote: \n>>     \n>>> On Tue, 2008-11-25 at 09:29 +0000, Luis Gutierrez wrote:\n>>> <snip>\n>>>   \n>>>       \n>>>> All push/pull/clone operations were failing with the dreaded 'fatal: The \n>>>> remote end hung up unexpectedly'. After a few tests, this is what I found:\n>>>>\n>>>> - I can clone/pull/push if I do it through ssh (ie, git clone \n>>>> ssh://server/project)\n>>>> - I can clone/pull/push if I start git daemon on the command line through\n>>>> git daemon --syslog --verbose --export-all \n>>>> --base-path=/vol0/git/projects --verbose --reuseaddr\n>>>>\n>>>> But the way I had setup git, through xinetd is broken.\n>>>>     \n>>>>         \n>>> I'm just guessing, as I'm too new to the git world to respond with more\n>>> expertise, but I will suggest that perhaps your problem is that your\n>>> $PATH is different with the xinitd configuration as contrasted with your\n>>> ssh configuration, as the locations of the git binaries could be\n>>> different.\n>>>\n>>>   \n>>>       \n>> I've tried that, they are the same:\n>>\n>> # which git\n>> /usr/local/bin/git\n>>     \n>\n> What about the other git-* commands?\n>\n>   \nThis is what I have now:\nls /usr/local/bin/git*\ngit  git-cvsserver  gitk  git-receive-pack  git-shell  \ngit-upload-archive  git-upload-pack\nit seems.. a lot less than it used to be, but then again, perhaps this \nis why the git-* commands were deprecated?\n\n\n-- \n* Luis Gutierrez | * XMOS Semiconductor <http://www.xmos.com>\nVenturers House, King Street, Bristol BS1 4PB, UK\n"},{"id":"96468","messageId":"1227610459.3222.4.camel@therock.nsw.bigpond.net.au","threadId":"16461","inReplyTo":"492BCFA0.5030708@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Arafangion","fromEmail":"thestar@fussycoder.id.au","sentAt":"2008-11-25T10:54:19Z","receivedAt":"2008-11-25T10:54:19Z","isPatch":false,"sender":{"key":"thestar@fussycoder.id.au","avatar":null},"body":"On Tue, 2008-11-25 at 10:12 +0000, Luis Gutierrez wrote:\n> Arafangion wrote: \n> > On Tue, 2008-11-25 at 09:29 +0000, Luis Gutierrez wrote:\n> > <snip>\n> >   \n> > > All push/pull/clone operations were failing with the dreaded 'fatal: The \n> > > remote end hung up unexpectedly'. After a few tests, this is what I found:\n> > > \n> > > - I can clone/pull/push if I do it through ssh (ie, git clone \n> > > ssh://server/project)\n> > > - I can clone/pull/push if I start git daemon on the command line through\n> > > git daemon --syslog --verbose --export-all \n> > > --base-path=/vol0/git/projects --verbose --reuseaddr\n> > > \n> > > But the way I had setup git, through xinetd is broken.\n> > >     \n> > \n> > I'm just guessing, as I'm too new to the git world to respond with more\n> > expertise, but I will suggest that perhaps your problem is that your\n> > $PATH is different with the xinitd configuration as contrasted with your\n> > ssh configuration, as the locations of the git binaries could be\n> > different.\n> > \n> >   \n> I've tried that, they are the same:\n> \n> # which git\n> /usr/local/bin/git\n\nWhat about the other git-* commands?\n\n> \n"},{"id":"96470","messageId":"492BDBA4.2020202@viscovery.net","threadId":"16461","inReplyTo":"492BC56A.6040506@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Johannes Sixt","fromEmail":"j.sixt@viscovery.net","sentAt":"2008-11-25T11:04:04Z","receivedAt":"2008-11-25T11:04:04Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Luis Gutierrez schrieb:\n> This is my current xinetd config:\n> service git\n> {\n>    disable      = yes\n\nRemove this line.\n\n-- Hannes\n"},{"id":"96471","messageId":"1227611674.3222.7.camel@therock.nsw.bigpond.net.au","threadId":"16461","inReplyTo":"492BD951.1010200@xmos.com","subject":"Re: inted problems when upgrading to 1.6.0.4","fromName":"Arafangion","fromEmail":"thestar@fussycoder.id.au","sentAt":"2008-11-25T11:14:34Z","receivedAt":"2008-11-25T11:14:34Z","isPatch":false,"sender":{"key":"thestar@fussycoder.id.au","avatar":null},"body":"On Tue, 2008-11-25 at 10:54 +0000, Luis Gutierrez wrote:\n<snip>\n> This is what I have now:\n> ls /usr/local/bin/git*\n> git  git-cvsserver  gitk  git-receive-pack  git-shell  \n> git-upload-archive  git-upload-pack\n> it seems.. a lot less than it used to be, but then again, perhaps this \n> is why the git-* commands were deprecated?\n\nAs Johannes Sixt mentioned, they have been moved from the bindir to the\nnew gitexecdir.\n"}]}