Re: Archive Server Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/06/2010 18:35:39, Andrew Wright wrote: > On Mon, 14 Jun 2010, A. Wright wrote: > >> Not a cache issue; clearing/restarting has no effect, and I have >> seen the issue on several machines/browsers (FBSD/links, Mac/Firefox, >> Mac/Safari). I'm wondering about firewall/proxy -- I'll give it >> a whirl when off-site later today. > > Still nothing when checking from home. > > I'm wondering about network topology -- it is dead when > viewed from my server (138.73.29.51). > > Traceroute returns this: > traceroute to wwwdyn.freebsd.org (69.147.83.38), 64 hops max, 52 > byte packets > 1 138.73.29.254 (138.73.29.254) 0.618 ms 0.555 ms 0.541 ms > 2 bfg-6506.mta.ca (138.73.101.254) 0.801 ms 0.311 ms 0.323 ms > 3 198.164.29.73 (198.164.29.73) 0.855 ms 0.792 ms 0.507 ms > 4 198.164.29.65 (198.164.29.65) 8.464 ms 8.194 ms 8.109 ms > 5 142.166.176.1 (142.166.176.1) 124.732 ms 124.961 ms 114.841 ms > 6 xe-1-0-0-200.dr02.fctn.nb.aliant.net (142.166.209.194) 129.638 > ms 117.374 ms 117.979 ms > 7 so-1-3-0.cr02.stjh.nb.aliant.net (142.166.185.145) 126.063 ms > 123.422 ms 130.776 ms > 8 te-0-2-5-0.cr01.hlfx.ns.aliant.net (142.166.181.137) 126.243 > ms 130.194 ms 123.887 ms > 9 xe-3-0-0.bx01.asbn.va.aliant.net (207.231.227.6) 144.084 ms > 148.291 ms 146.069 ms > 10 yho1.asbn.va.aliant.net (207.231.227.26) 146.966 ms 143.405 > ms 144.975 ms > 11 ae-6.pat1.dce.yahoo.com (216.115.102.172) 140.772 ms 146.617 > ms 166.540 ms > 12 as-0.pat2.che.yahoo.com (216.115.101.145) 166.338 ms 201.429 > ms 172.191 ms > 13 as-1.pat2.dnx.yahoo.com (216.115.96.55) 206.685 ms 212.076 ms > 212.919 ms > 14 as-0.pat1.pao.yahoo.com (216.115.101.128) 221.059 ms 220.649 > ms 222.264 ms > 15 ae-1-d140.msr1.sp1.yahoo.com (216.115.107.53) 230.591 ms > ae-0-d140.msr1.sp1.yahoo.com (216.115.107.49) 235.904 ms > UNKNOWN-216-115-107-73.yahoo.com (216.115.107.73) 229.977 ms > 16 * * gi-1-39.bas-b1.sp1.yahoo.com (98.136.16.61) 661.870 ms > 17 wwwdyn.freebsd.org (69.147.83.38) 235.035 ms 238.288 ms > 229.476 ms > > Could there be some bad cacheing on the server? I'm guessing that > "wwdyn" indicates some load balancing? Possibly. I get subtly a different traceroute to yours once the traffic gets into Yahoo's network. lucid-nonsense:~:% traceroute lists.freebsd.org traceroute to wwwdyn.freebsd.org (69.147.83.38), 64 hops max, 52 byte packets 1 gate (81.187.76.161) 1.221 ms 1.125 ms 1.048 ms 2 2.b.gormless.thn.aaisp.net.uk (90.155.53.112) 27.369 ms 27.692 ms 27.523 ms 3 a.armless.thn.aaisp.net.uk (90.155.53.6) 28.955 ms 27.807 ms 27.771 ms 4 lvl3gw.thn.packetexchange.net (212.187.197.193) 28.535 ms 28.301 ms 28.761 ms 5 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 28.824 ms 29.236 ms 28.486 ms 6 ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66) 97.785 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 97.880 ms 97.654 ms 7 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 102.875 ms ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 98.293 ms ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 104.146 ms 8 ae-94-94.ebr4.NewYork1.Level3.net (4.69.134.125) 98.448 ms ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117) 110.459 ms ae-84-84.ebr4.NewYork1.Level3.net (4.69.134.121) 98.013 ms 9 ae-2-2.ebr4.SanJose1.Level3.net (4.69.135.185) 170.752 ms 167.141 ms 178.554 ms 10 ae-94-94.csw4.SanJose1.Level3.net (4.69.134.254) 166.887 ms ae-64-64.csw1.SanJose1.Level3.net (4.69.134.242) 166.901 ms 167.271 ms 11 ae-13-69.car3.SanJose1.Level3.net (4.68.18.5) 168.587 ms 351.785 ms 220.689 ms 12 4.71.112.14 (4.71.112.14) 176.247 ms 176.649 ms 175.371 ms 13 ae-0-d161.msr1.sp1.yahoo.com (216.115.107.59) 167.602 ms ae-1-d161.msr1.sp1.yahoo.com (216.115.107.63) 168.532 ms ae-1-d171.msr2.sp1.yahoo.com (216.115.107.87) 168.556 ms 14 gi-1-41.bas-b2.sp1.yahoo.com (209.131.32.33) 169.761 ms UNKNOWN-98-136-16-47.yahoo.com (98.136.16.47) 168.770 ms UNKNOWN-98-136-16-57.yahoo.com (98.136.16.57) 168.393 ms 15 wwwdyn.freebsd.org (69.147.83.38) 168.668 ms 168.849 ms 169.531 ms Of course, this could very well be the reason why I get different results to you. I have IPv6 connectivity. lucid-nonsense:~:% traceroute6 lists.freebsd.org traceroute6 to wwwdyn.freebsd.org (2001:4f8:fff6::26) from 2001:8b0:151:1::1, 64 hops max, 12 byte packets 1 b.gormless.thn.aaisp.net.uk 27.407 ms 26.967 ms 26.968 ms 2 2001:7f8:4::50e8:1 26.974 ms 26.678 ms 27.100 ms 3 10gigabitethernet1-1.core1.lon1.he.net 27.534 ms 27.328 ms 27.568 ms 4 10gigabitethernet2-3.core1.ny4.ipv6.he.net 98.253 ms 96.154 ms 95.826 ms 5 10gigabitethernet2-3.core1.ash1.ipv6.he.net 100.939 ms 101.851 ms 105.118 ms 6 10gigabitethernet1-2.core1.atl1.he.net 121.391 ms 122.689 ms 123.839 ms 7 2001:470:0
Re: Archive Server Error
On Mon, 14 Jun 2010, A. Wright wrote: Not a cache issue; clearing/restarting has no effect, and I have seen the issue on several machines/browsers (FBSD/links, Mac/Firefox, Mac/Safari). I'm wondering about firewall/proxy -- I'll give it a whirl when off-site later today. Still nothing when checking from home. I'm wondering about network topology -- it is dead when viewed from my server (138.73.29.51). Traceroute returns this: traceroute to wwwdyn.freebsd.org (69.147.83.38), 64 hops max, 52 byte packets 1 138.73.29.254 (138.73.29.254) 0.618 ms 0.555 ms 0.541 ms 2 bfg-6506.mta.ca (138.73.101.254) 0.801 ms 0.311 ms 0.323 ms 3 198.164.29.73 (198.164.29.73) 0.855 ms 0.792 ms 0.507 ms 4 198.164.29.65 (198.164.29.65) 8.464 ms 8.194 ms 8.109 ms 5 142.166.176.1 (142.166.176.1) 124.732 ms 124.961 ms 114.841 ms 6 xe-1-0-0-200.dr02.fctn.nb.aliant.net (142.166.209.194) 129.638 ms 117.374 ms 117.979 ms 7 so-1-3-0.cr02.stjh.nb.aliant.net (142.166.185.145) 126.063 ms 123.422 ms 130.776 ms 8 te-0-2-5-0.cr01.hlfx.ns.aliant.net (142.166.181.137) 126.243 ms 130.194 ms 123.887 ms 9 xe-3-0-0.bx01.asbn.va.aliant.net (207.231.227.6) 144.084 ms 148.291 ms 146.069 ms 10 yho1.asbn.va.aliant.net (207.231.227.26) 146.966 ms 143.405 ms 144.975 ms 11 ae-6.pat1.dce.yahoo.com (216.115.102.172) 140.772 ms 146.617 ms 166.540 ms 12 as-0.pat2.che.yahoo.com (216.115.101.145) 166.338 ms 201.429 ms 172.191 ms 13 as-1.pat2.dnx.yahoo.com (216.115.96.55) 206.685 ms 212.076 ms 212.919 ms 14 as-0.pat1.pao.yahoo.com (216.115.101.128) 221.059 ms 220.649 ms 222.264 ms 15 ae-1-d140.msr1.sp1.yahoo.com (216.115.107.53) 230.591 ms ae-0-d140.msr1.sp1.yahoo.com (216.115.107.49) 235.904 ms UNKNOWN-216-115-107-73.yahoo.com (216.115.107.73) 229.977 ms 16 * * gi-1-39.bas-b1.sp1.yahoo.com (98.136.16.61) 661.870 ms 17 wwwdyn.freebsd.org (69.147.83.38) 235.035 ms 238.288 ms 229.476 ms Could there be some bad cacheing on the server? I'm guessing that "wwdyn" indicates some load balancing? There seems to be some strange configuration going on; if the IP is substituted: http://69.147.83.38/pipermail/freebsd-questions/ a "document not found" error results referring to a machine called "realcgi.sky.freebsd.org". A. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Archive Server Error
On Mon, 14 Jun 2010 10:46:55 -0300 (ADT) A. Wright articulated: > On Mon, 14 Jun 2010, Matthew Seaman wrote: > > > On 14/06/2010 13:21:40, Carmel wrote: > >> I am/was attempting to search the archive located at: > >> http://lists.freebsd.org/pipermail/freebsd-questions/ > >> > >> Unfortunately, I am continually greeted with this error message: > >[ error message deleted ] > > > Works for me. Try again. If you still see the problem, it's > > possible your browser has cached the error page and isn't really > > going back to the site at all. Try quitting and restarting your > > browser. > > Interesting. Archive search hasn't worked for me for weeks, > with the same 500 error returned. > > Not a cache issue; clearing/restarting has no effect, and I have > seen the issue on several machines/browsers (FBSD/links, Mac/Firefox, > Mac/Safari). I'm wondering about firewall/proxy -- I'll give it > a whirl when off-site later today. I just tried from a different computer using a different web browser with the same results. I was wondering about this notation on the page though: Note:The archive search index was last rebuilt at Thursday, 08 Feb 2007 06:16:51 UTC. Any postings after that will not be found by a search. Index rebuild is usally done once every 24 hours for this list. You can use a "View by date" link below to access more recent postings. Is there any specific reason that the archive has not been re-index in over three years? I don't remember the date of the post I wasx referring to, so that could become a rather long process. -- Carmel ✌ carmel...@hotmail.com |=== |=== |=== |=== | Spelling is a lossed art. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Archive Server Error
On Mon, 14 Jun 2010, Matthew Seaman wrote: On 14/06/2010 13:21:40, Carmel wrote: I am/was attempting to search the archive located at: http://lists.freebsd.org/pipermail/freebsd-questions/ Unfortunately, I am continually greeted with this error message: [ error message deleted ] Works for me. Try again. If you still see the problem, it's possible your browser has cached the error page and isn't really going back to the site at all. Try quitting and restarting your browser. Interesting. Archive search hasn't worked for me for weeks, with the same 500 error returned. Not a cache issue; clearing/restarting has no effect, and I have seen the issue on several machines/browsers (FBSD/links, Mac/Firefox, Mac/Safari). I'm wondering about firewall/proxy -- I'll give it a whirl when off-site later today. A. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Archive Server Error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/06/2010 13:21:40, Carmel wrote: > I am/was attempting to search the archive located at: > http://lists.freebsd.org/pipermail/freebsd-questions/ > > Unfortunately, I am continually greeted with this error message: > > > > Internal Server Error > The server encountered an internal error or misconfiguration and was unable > to complete your request. Works for me. Try again. If you still see the problem, it's possible your browser has cached the error page and isn't really going back to the site at all. Try quitting and restarting your browser. If you're using a web proxy, then the same caching problem might occur there. If the proxy isn't under your control, then probably the best thing for you to do is leave well alone for several hours, and then try again. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwWIBIACgkQ8Mjk52CukIxP0gCbB6zMeieqqok1CZ9hsUmaW2WS AScAnR7BrhCwzNQ++/DUoUDrZCekOsfJ =UNve -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
