From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: git.ipfire.org - no route to host
Date: Mon, 01 Oct 2018 12:18:44 +0100 [thread overview]
Message-ID: <4e24a80b00ec12ac934b77cfc24b4b1e48f296e9.camel@ipfire.org> (raw)
In-Reply-To: <06ca8e98-2d4b-2148-5430-00c303caedc2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
Hello,
that was me. The VM was paused by the hypervisor because of a storage issue.
I just rebooted it and it is up again.
-Michael
On Mon, 2018-10-01 at 12:27 +0200, Matthias Fischer wrote:
> On 01.10.2018 07:51, Matthias Fischer wrote:
> > Hi,
> >
> > while trying to push - or pull - something to 'git.ipfire.org' through
> > SSH I suddenly always get:
> >
> > ***SNIP***
> > root(a)Devel: /home/matz/ipfire-2.x # git push mfischer squid_4
> > ssh: connect to host git.ipfire.org port 22: No route to host
> > fatal: Could not read from remote repository.
> >
> > Please make sure you have the correct access rights
> > and the repository exists.
> > ***SNAP***
> > ...
>
> Working again...
>
> Whoever solved this: thanks! ;-)
>
> Best,
> Matthias
prev parent reply other threads:[~2018-10-01 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 5:51 Matthias Fischer
2018-10-01 10:27 ` Matthias Fischer
2018-10-01 11:18 ` 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=4e24a80b00ec12ac934b77cfc24b4b1e48f296e9.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