Thread: Broken link to 8.2 release notes

Broken link to 8.2 release notes

From
Jeff Davis
Date:
The page here, which is linked from the press kit:

http://www.postgresql.org/docs/current/static/release.html

contains a broken link to both the 8.2 release notes and 8.1.5.

After a few minutes, the link to the 8.2 notes disappeared, and then
reappeared (still a broken link).

I think something is wrong, or I am hitting various mirror sites or
something.

Regards,
    Jeff Davis


Re: Broken link to 8.2 release notes

From
"Joshua D. Drake"
Date:
On Tue, 2006-12-05 at 15:01 -0800, Jeff Davis wrote:
> The page here, which is linked from the press kit:
>
> http://www.postgresql.org/docs/current/static/release.html
>
> contains a broken link to both the 8.2 release notes and 8.1.5.
>
> After a few minutes, the link to the 8.2 notes disappeared, and then
> reappeared (still a broken link).
>
> I think something is wrong, or I am hitting various mirror sites or
> something.

You are probably hitting different mirrors.

J


>
> Regards,
>     Jeff Davis
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly
>
--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate




Re: Broken link to 8.2 release notes

From
Jeff Davis
Date:
On Tue, 2006-12-05 at 15:06 -0800, Joshua D. Drake wrote:
> On Tue, 2006-12-05 at 15:01 -0800, Jeff Davis wrote:
> > The page here, which is linked from the press kit:
> >
> > http://www.postgresql.org/docs/current/static/release.html
> >
> > contains a broken link to both the 8.2 release notes and 8.1.5.
> >
> > After a few minutes, the link to the 8.2 notes disappeared, and then
> > reappeared (still a broken link).
> >
> > I think something is wrong, or I am hitting various mirror sites or
> > something.
>
> You are probably hitting different mirrors.
>

Are you saying the problem will fix itself? A 404 seems undesirable to
me.

Regards,
    Jeff Davis


Re: Broken link to 8.2 release notes

From
"Joshua D. Drake"
Date:
> > > I think something is wrong, or I am hitting various mirror sites or
> > > something.
> >
> > You are probably hitting different mirrors.
> >
>
> 217.196.146.201
> 66.98.251.159
>
> These are the two mirrors that have apparently not updated. Will they
> update automatically, or is there a problem?

Honestly, I can't answer that. We need dpage, magnus, devrim (all who
are likley asleep now) or Rob Treat who is likely at the show.

>
> Regards,
>     Jeff Davis
>
--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate




Re: Broken link to 8.2 release notes

From
"Joshua D. Drake"
Date:
On Tue, 2006-12-05 at 15:32 -0800, Jeff Davis wrote:
> On Tue, 2006-12-05 at 15:06 -0800, Joshua D. Drake wrote:
> > On Tue, 2006-12-05 at 15:01 -0800, Jeff Davis wrote:
> > > The page here, which is linked from the press kit:
> > >
> > > http://www.postgresql.org/docs/current/static/release.html
> > >
> > > contains a broken link to both the 8.2 release notes and 8.1.5.
> > >
> > > After a few minutes, the link to the 8.2 notes disappeared, and then
> > > reappeared (still a broken link).
> > >
> > > I think something is wrong, or I am hitting various mirror sites or
> > > something.
> >
> > You are probably hitting different mirrors.
> >
>
> 217.196.146.201
> 66.98.251.159
>

The 66. number is ftp. which is the what all the mirrors feed off of.
Have you tried clearning your cache ? :)

J



> These are the two mirrors that have apparently not updated. Will they
> update automatically, or is there a problem?
>
> Regards,
>     Jeff Davis
>
--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate




Re: Broken link to 8.2 release notes

From
Jeff Davis
Date:
On Tue, 2006-12-05 at 15:49 -0800, Joshua D. Drake wrote:
> On Tue, 2006-12-05 at 15:32 -0800, Jeff Davis wrote:
> > On Tue, 2006-12-05 at 15:06 -0800, Joshua D. Drake wrote:
> > > On Tue, 2006-12-05 at 15:01 -0800, Jeff Davis wrote:
> > > > The page here, which is linked from the press kit:
> > > >
> > > > http://www.postgresql.org/docs/current/static/release.html
> > > >
> > > > contains a broken link to both the 8.2 release notes and 8.1.5.
> > > >
> > > > After a few minutes, the link to the 8.2 notes disappeared, and then
> > > > reappeared (still a broken link).
> > > >
> > > > I think something is wrong, or I am hitting various mirror sites or
> > > > something.
> > >
> > > You are probably hitting different mirrors.
> > >
> >
> > 217.196.146.201
> > 66.98.251.159
> >
>
> The 66. number is ftp. which is the what all the mirrors feed off of.
> Have you tried clearning your cache ? :)
>

The problem is fixed now. What I did was a "host www.postgresql.org" and
4 IPs were returned:

www.postgresql.org is an alias for static.mirrors.postgresql.org.
static.mirrors.postgresql.org has address 217.196.146.201
static.mirrors.postgresql.org has address 66.98.251.159
static.mirrors.postgresql.org has address 80.179.151.210
static.mirrors.postgresql.org has address 212.247.200.180

I did a telnet to each one and an HTTP request to see if the document
existed on that box. For those two I listed in the previous email, no
document existed which was causing a 404 for some people (like me).

Now the document exists on all those 4 IPs. It just took a while for
them to sync up I guess.

Regards,
    Jeff Davis


Re: Broken link to 8.2 release notes

From
Jim Nasby
Date:
On Dec 5, 2006, at 3:44 PM, Joshua D. Drake wrote:
>> These are the two mirrors that have apparently not updated. Will they
>> update automatically, or is there a problem?
>
> Honestly, I can't answer that. We need dpage, magnus, devrim (all who
> are likley asleep now) or Rob Treat who is likely at the show.

Do we need better coverage on those mirrors?
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



Re: Broken link to 8.2 release notes

From
Stefan Kaltenbrunner
Date:
Jim Nasby wrote:
> On Dec 5, 2006, at 3:44 PM, Joshua D. Drake wrote:
>>> These are the two mirrors that have apparently not updated. Will they
>>> update automatically, or is there a problem?
>>
>> Honestly, I can't answer that. We need dpage, magnus, devrim (all who
>> are likley asleep now) or Rob Treat who is likely at the show.
>
> Do we need better coverage on those mirrors?

hmm - the mirrors itself were fine - iirc it's just that we only sync
them every hour(which normally seems like a reasonable timespan).

So I'm not even convinced we actually have a problem to solve here ...


Stefan

Re: Broken link to 8.2 release notes

From
Dave Page
Date:
Stefan Kaltenbrunner wrote:
> Jim Nasby wrote:
>> On Dec 5, 2006, at 3:44 PM, Joshua D. Drake wrote:
>>>> These are the two mirrors that have apparently not updated. Will they
>>>> update automatically, or is there a problem?
>>> Honestly, I can't answer that. We need dpage, magnus, devrim (all who
>>> are likley asleep now) or Rob Treat who is likely at the show.
>> Do we need better coverage on those mirrors?
>
> hmm - the mirrors itself were fine - iirc it's just that we only sync
> them every hour(which normally seems like a reasonable timespan).
>
> So I'm not even convinced we actually have a problem to solve here ...

Agreed - I looked at this at the time and couldn't see anything wrong.
Besides, we do monitor them as well, so if one falls too far out of sync
it automatically gets removed from active duty until it catches up again.

Regards, Dave.