From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: HTTPError: HTTP Error 502: Bad Gateway - http://checkip4.dns.lightningwirelabs.com/
Date: Fri, 13 Oct 2017 17:41:03 +0200 [thread overview]
Message-ID: <956bbc20-b282-e2b5-82f2-599ff1e2857f@ipfire.org> (raw)
In-Reply-To: <1507900582.19915.2.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi,
On 13.10.2017 15:16, Michael Tremer wrote:
> I had some severe server woes yesterday that affected the whole infrastructure.
Trying to build current 'net' with 'snort 2.9.11' ( ;-) ) gives me:
***SNIP***
...
Oct 13 15:32:45: Building ipfire-netboot -e ipfire-netboot Download: https://source.ipfire.org/releases/ipfire-netboot//ipfire-netboot-v2.0.tar.gz
failed: No route to host.
failed: Cannot assign requested address.
ipfire-netboot:65: recipe for target '/home/matz/ipfire-2.x/cache/ipfire-netboot-v2.0.tar.gz' failed
make: *** [/home/matz/ipfire-2.x/cache/ipfire-netboot-v2.0.tar.gz] Error 4
ERROR: Download error in ipfire-netboot
Check /home/matz/ipfire-2.x/log/_build.ipfire.log for errors if applicable
...
***SNAP***
Can't find this on 'git.ipfire.org:/pub/sources/source-2.x', either.
Missing sources?
Best,
Matthias
next prev parent reply other threads:[~2017-10-13 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <542330051.14192.1507879222393@office.mailbox.org>
2017-10-13 13:16 ` Michael Tremer
2017-10-13 15:41 ` Matthias Fischer [this message]
2017-10-13 20:03 ` Michael Tremer
2017-10-13 20:39 ` Matthias Fischer
2017-10-16 19:39 ` Michael Tremer
2017-10-16 19:46 ` ummeegge
2017-10-17 16:19 ` Matthias Fischer
2017-10-18 11:08 ` Michael Tremer
2017-10-18 14:03 ` Matthias Fischer
2017-10-18 14:31 ` Matthias Fischer
2017-10-13 16:05 ` Matthias Fischer
2017-10-13 20:04 ` Michael Tremer
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=956bbc20-b282-e2b5-82f2-599ff1e2857f@ipfire.org \
--to=matthias.fischer@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