FreeBSD website unreliable

[Chris_H]

Greetings, all.
Hope this is the right place to post this. The FreeBSD ports search is down again, as are the man pages. I host the same man page web search, and as a result, my sites are swamped with requests now that FreeBSD is offline. Nothing I can't handle, and for that matter, I love the additional attention. I've become increasingly frustrated with the availability of the FreeBSD ports search reliability. Sure, I could install one of the many ports index ports, or cobble up my own local search script to find what I want locally. But it just doesn't seem right, that FreeBSD should look so unreliable. So I've decided to host the ports search here, as well, and was wondering where I could get the ports search script. It used to be available back when FreeBSD used CVS. But now that FreeBSD uses subversion, I'm not able to locate it.

Thank you for all your time, and consideration.

--Chris

P.S. Forgot to mention; while FreshPorts has a lot of nice additions, they too, aren't reachable. Their BGP has been buggered for a week (v100.colo2.aus.datafoundry.net). It has no idea where to go, to find http://www.freshports.org.

 

[drhowarddrfine]

Things can change in a heart beat but the man pages and freshports have both been working for me when I've looked at them for the past several days on and off.

 

[Beastie]

I used both http://www.freebsd.org/ports/ and http://www.freshports.org/ yesterday in the evening, and have just tried them and the man pages now. Everything is working fine here.

In fact I use these almost every day and I can't remember them being down in recent memory, so it could well be your ISP/DNS cache/etc.

When I encounter problems connecting to a website I always check them with services like http://www.downforeveryoneorjustme.com/ or try to connect through a web proxy.

 

[Chris_H]

@@drhowarddrfine, @@Beastie.
Thanks for your replies.
Regarding the ability to reach the FreeBSD ports ( http://www.freebsd.org/ports/ ); I could easily reach the page(s). But they had no value

Error 503 The bugs backend is currently offline. It will be back ASAP. No current ETA. You can get help with bug reports via regular email to freebsd-bugs@freebsd.org. There is no need to report this as a bug.

The bugs backend is currently offline. It will be back ASAP. No current ETA. You can get help with bug reports via regular email to freebsd-bugs@freebsd.org. There is no need to report this as a bug.

Guru Meditation:

XID: 1364729157

Varnish cache server

These were the contents of every page for several hours. The past errors emitted similar pages.
Regarding FreshPorts;
I had already done some research prior to making this post. In doing so, I was able to determine that my upstream was not to blame, as using other parts of the globe to test the availability, also revealed unreachability. Redundancy is the key to overcoming this. Having a single point of failure, ensures problems in this regard. It is for this same reason, that the DNS RFC's insist that one have a minimum of two NS entries (Name Servers) per domain, and on different network segments.
While both of your responses were appreciated, neither provided an answer to my question -- does anyone know where I might find the ports search perl script that FreeBSD uses at http://www.freebsd.org/ports/ ?

Thanks again, for taking the time to respond.

--Chris

P.S.
I hope FreeBSD's outage didn't have anything to do with:
http://www.vuxml.org/freebsd/d9dbe6e8-8 ... 2d077.html ( ports/www/varnish/ )

 

[cpm@]

Maybe you are looking for ports-mgmt/psearch tool. Also, it's worth to take a look to the FreshPorts.org development blog which provides a very useful information.

 

[tzoi516]

I sometimes use a VPN service, and one of the IPs used is blocked by freebsd.org. When I grab a different IP then I'm able to get to freebsd.org sites.