From: Thomas Monjalon <thomas@monjalon.net>
To: ci@dpdk.org
Cc: Jeremy Plsek <jplsek@iol.unh.edu>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
lijuan.tu@intel.com
Subject: Re: [dpdk-ci] ci/Intel-compilation is blocked due to 502 error when running "git pull"
Date: Mon, 20 Aug 2018 11:18:27 +0200 [thread overview]
Message-ID: <4115420.tUIEntVdbm@xps> (raw)
In-Reply-To: <CA+xUZB6-dQYeyNrSUiMCBxswEJB0emewY-5KvfsgKCZvFA5ayQ@mail.gmail.com>
There was an issue on the server.
I killed everything so the HTTP access became OK,
but I forgot to restart GIT daemon access.
Everything should be OK now.
Sorry for the troubles.
17/08/2018 18:47, Jeremy Plsek:
> Running `git clone git://dpdk.org/dpdk` yields:
>
> Cloning into 'dpdk'...
> fatal: unable to connect to dpdk.org:
> dpdk.org[0: 92.243.14.124]: errno=Connection refused
>
> (Running `git clone http://dpdk.org/git/dpdk` works though)
> On Fri, Aug 17, 2018 at 12:32 PM Yigit, Ferruh <ferruh.yigit@intel.com> wrote:
> >
> > It was a server issue, it has been fixed a while ago, it should be OK now.
> >
> >
> >
> > From: Tu, Lijuan
> > Sent: Friday, August 17, 2018 10:47 AM
> > To: ci@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
> > Subject: ci/Intel-compilation is blocked due to 502 error when running "git pull"
> >
> >
> >
> > Hi,
> >
> >
> >
> > CI/Intel-compilation system is blocked due to unable to access 'http://dpdk.org/git/dpdk/ in PRC
> >
> > Get error “fatal: unable to access 'http://dpdk.org/git/dpdk/': The requested URL returned error: 502”
> >
> > url = http://dpdk.org/git/dpdk
> >
> >
> >
> > Could you please look into this ?
> >
> >
> >
> > BR,
> >
> > Lijuan
next prev parent reply other threads:[~2018-08-20 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 9:47 Tu, Lijuan
2018-08-17 16:31 ` Yigit, Ferruh
2018-08-17 16:47 ` Jeremy Plsek
2018-08-20 9:18 ` Thomas Monjalon [this message]
2018-08-20 9:20 ` Tu, Lijuan
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=4115420.tUIEntVdbm@xps \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jplsek@iol.unh.edu \
--cc=lijuan.tu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).