You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by "lunakid@gmail.com" <lu...@gmail.com> on 2017/09/30 00:06:49 UTC

Re: Public bloodhound down

Hello there,

Just found about the project, got excited, wanted to try an online demo, and ended up registering here to report that the service is down again (so the main project "welcome" page http://bloodhound.apache.org is full of dead links now). I don't know for how long, I've just been there for the first time today.

I'm also not sure how much the project itself is still alive (but found a question about just that from 2 years ago, and the answers then were: kinda-sorta), nevertheless, if nothing else, the nice Apache front page certainly suggests it very much is...

All the best,
Sz.

On 2017-01-18 22:44, John Chambers <ch...@apache.org> wrote: 
> https://issues.apache.org/jira/browse/INFRA-13351 has been resolved.
> https://issues.apache.org/bloodhound should now be back online.
> 
> Cheers
> 
> John
> 
> On 18 January 2017 at 11:45, John Chambers <ch...@apache.org> wrote:
> 
> > I have raised https://issues.apache.org/jira/browse/INFRA-13351.
> >
> > Our vm hosting bloodhound appears to be up and working ok. Will see what
> > INFRA have to say.
> >
> > Cheers
> >
> > John
> >
> > On 18 January 2017 at 11:12, Jason Morgan <ja...@pavegen.co.uk>
> > wrote:
> >
> >> Hi,
> >> It looks to me like somebody at Apache has removed the virtualhost for
> >> bloodhound.  The root of this server seems to indicate this:
> >> https://issues.apache.org/
> >>
> >> I have access to several VPS with decent internet connections which can
> >> host it if you can't get Apache to play ball and put it up again.
> >>
> >> Regards,
> >> Jason Morgan
> >>
> >> On 18 January 2017 at 02:02, Ryan J Ollos <rj...@apache.org> wrote:
> >>
> >> > On Mon, Jul 18, 2016 at 2:49 AM Tom Edwards <td...@t0m.me.uk> wrote:
> >> >
> >> > > Hi,
> >> > >
> >> > > The public self-hosted instance of bloodhound here:
> >> > >
> >> > > https://issues.apache.org/bloodhound/wiki/BloodhoundInstall
> >> > >
> >> > > has been down for the last few days. As most of the documentation
> >> appears
> >> > > hosted through this portal, including contact information, I've only
> >> go
> >> > > this email address to report issues.
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Tom
> >> > >
> >> >
> >> > It seems issues.apache.org/bloodhound is down again: "The requested URL
> >> > /bloodhound was not found on this server."
> >> >
> >> > I may have access to the vm, but I can't even remember anymore and don't
> >> > have time right now to go digging. Could someone with access please
> >> take a
> >> > look?
> >> >
> >> > - Ryan
> >> >
> >>
> >>
> >>
> >> --
> >>
> >> ------------------------------
> >> <http://www.pavegen.com>
> >>
> >> *Jason Morgan*
> >> Principal Engineer
> >>
> >> t: +44 1223 781555
> >> m: +44 (0) 7877 662290
> >> ddi: +44 1223 781556
> >>
> >> *Engineering*
> >> Pavegen Systems Ltd
> >> Future Business Centre
> >> Kings Hedges Road
> >> Cambridge, CB4 2HY
> >>
> >> *Head Office*
> >> 5-15 Cromer St
> >> London, WC1H 8LS
> >>
> >> t: +44 (0) 2033 977 279
> >> pavegen.com <http://www.pavegen.com>
> >> #thenextstep16 <http://www.pavegen.com/livestream>
> >>
> >> <http://www.twitter.com/pavegen>   <http://www.facebook.com/pavegen>
> >> <https://www.linkedin.com/company/pavegen-system-ltd->
> >> ------------------------------
> >>
> >> The content of this email and any attachments are confidential and may
> >> contain privileged information. If you are not the addressee it may be
> >> unlawful for you to read, copy, distribute, disclose or otherwise use the
> >> information contained herein.
> >>
> >> Company Registered no: 06980029 | Company VAT no: 996499723
> >>
> >
> >
>