From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: No connection to repo
Date: Sun, 05 Mar 2017 12:41:20 +0000 [thread overview]
Message-ID: <1488717680.2451.2.camel@ipfire.org> (raw)
In-Reply-To: <e2fcf1fb-7422-4685-5876-d794bc63c212@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
Hi,
I am just updating that machine :)
Sorry. Probably should have announced that...
It should be back up in about 10-15 minutes...
-Michael
On Sun, 2017-03-05 at 13:40 +0100, Matthias Fischer wrote:
> Hi,
>
> Devel is running without problems, but all of a sudden, he can't
> "pull": ;-)
>
> ...
> root(a)Devel: /home/matz/ipfire-2.x # git pull origin next
> ssh: connect to host git.ipfire.org port 22: No route to host
> fatal: Konnte nicht vom Remote-Repository lesen.
>
> Bitte stellen Sie sicher, dass die korrekten Zugriffsberechtigungen
> bestehen und das Repository existiert.
> ...
>
> ...
> root(a)Devel: /home/matz/ipfire-2.x # ping git.ipfire.org
> PING git.ipfire.org (81.3.27.45) 56(84) bytes of data.
> 64 bytes from 81.3.27.45: icmp_seq=1 ttl=57 time=20.6 ms
> 64 bytes from 81.3.27.45: icmp_seq=2 ttl=57 time=20.1 ms
> 64 bytes from 81.3.27.45: icmp_seq=3 ttl=57 time=20.4 ms
> 64 bytes from 81.3.27.45: icmp_seq=4 ttl=57 time=20.0 ms
> 64 bytes from 81.3.27.45: icmp_seq=5 ttl=57 time=20.1 ms
> 64 bytes from 81.3.27.45: icmp_seq=6 ttl=57 time=20.7 ms
> 64 bytes from 81.3.27.45: icmp_seq=7 ttl=57 time=20.1 ms
> ^C
> --- git.ipfire.org ping statistics ---
> 7 packets transmitted, 7 received, 0% packet loss, time 6008ms
> rtt min/avg/max/mdev = 20.006/20.330/20.718/0.290 ms
> ...
>
> Nothing was changed, nothing is blocked, but SSH-connections won't
> work.
>
> Bug or Feature or my fault!?
>
> Best,
> Matthias
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-03-05 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 12:40 Matthias Fischer
2017-03-05 12:41 ` Michael Tremer [this message]
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=1488717680.2451.2.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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