Sylvain, you wrote Saturday, February 27, 2010 3:15 PM
This reminds me of MTU networking issues - as soon as there's a
big
enough packet, the connection hangs.
This was the clue I needed. SSH sets the DF bit in the
IP header to prevent packet fragmentation. This is
deliberate to avoid a po
Hi,
> Thanks. That confirms that the ssh tunnel and my keys
> are not the problem, right?
Yes.
This reminds me of MTU networking issues - as soon as there's a big
enough packet, the connection hangs.
To precise what that means technically and give you a few keywords, I
usually need to add thi
Trevor Daniels wrote Saturday, February 27, 2010 9:31 AM
Sylvain, you wrote Saturday, February 27, 2010 7:12 AM
Is there also a problem with other repositories?
e.g.
git clone ssh://trev...@git.sv.gnu.org/srv/git/freedink.git
I tried this. Interesting! It got a little further.
Here's wha
Sylvain, you wrote Saturday, February 27, 2010 7:12 AM
We do get logs of your connection:
Feb 27 00:04:14 vcs-noshell sshd[17954]: Accepted publickey for
trevord from 86.138.108.87 port 55534 ssh2
Feb 27 00:04:14 vcs-noshell sshd[17954]: pam_env(sshd:setcred):
Unable to open env file: /etc/
We do get logs of your connection:
Feb 27 00:04:14 vcs-noshell sshd[17954]: Accepted publickey for trevord from
86.138.108.87 port 55534 ssh2
Feb 27 00:04:14 vcs-noshell sshd[17954]: pam_env(sshd:setcred): Unable to open
env file: /etc/default/locale: No such file or directory
Feb 27 00:04:14 vc
Sylvain, you wrote Friday, February 26, 2010 10:07 PM
I would suggest trying without relying on .ssh/config, and making
sure
there's nothing weird in /etc/hosts.
You should see something like this:
$ git clone ssh://b...@git.sv.gnu.org/srv/git/lilypond.git
Initialized empty Git repository in
I would suggest trying without relying on .ssh/config, and making sure
there's nothing weird in /etc/hosts.
You should see something like this:
$ git clone ssh://b...@git.sv.gnu.org/srv/git/lilypond.git
Initialized empty Git repository in /tmp/lilypond/.git/
remote: Counting objects: 189704
Re
Sylvain Beucler wrote Thursday, February 25, 2010 7:03 AM
This works for me.
Yes, it seems to work for everyone else, but not for
me.
I issued a 'git gc' just in case.
Tried that. No change.
I've checked that the call set-up packet is getting
to and through my router, and I've tried usi
Hi,
This works for me.
I issued a 'git gc' just in case.
--
Sylvain
On Thu, Feb 25, 2010 at 12:44:44AM -, Trevor Daniels wrote:
> Hi
>
> I have been able to use ssh to pull and push to lilypond.git at
> 199.232.41.69 for many months, but sometime between 8 Feb 2010 and
> 16 Feb 2010 this
Hi
I have been able to use ssh to pull and push to lilypond.git at
199.232.41.69 for many months, but sometime between 8 Feb 2010 and
16 Feb 2010 this stopped working with the attempt timing out. I've
tried to resolve this by moving to 140.186.70.72, but I still cannot
push or pull with ssh.
10 matches
Mail list logo