| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | thomas(at)pgsql(dot)com |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: cvsup trouble |
| Date: | 2001-09-21 14:41:34 |
| Message-ID: | 28143.1001083294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
> Thanks for fixing it. Now of course the machine does not seem to be
> visible. That was the case yesterday too; are these planned outages, is
> it still bouncing up and down as it is configured, or is it flakey?
Looks fine from here:
$ ping cvsup.postgresql.org
PING rs.postgresql.org: 64 byte packets
64 bytes from 64.39.15.238: icmp_seq=0. time=57. ms
64 bytes from 64.39.15.238: icmp_seq=1. time=70. ms
Perhaps there is a routing problem somewhere between you and 64.39.15.238?
That machine is not physically at hub (looks like it's a Rackspace site)
so there might be connectivity issues that are different from hub's.
What do you get from tracerouting to cvsup.postgresql.org?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-09-21 15:49:03 | Re: cvsup trouble |
| Previous Message | Jean-Michel POURE | 2001-09-21 14:40:12 | int4eq (xid, int4) |