Hi all.

I haven't been able to to load reseller.opensrs.net for two days, this is
the error I get:

Cannot find server or DNS Error
Internet Explorer

OpenSRS says every thing is fine, what's up, anyone know?

Dennis ...

------------------->

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of lance
> Sent: Monday, November 13, 2000 10:58 AM
> To: Frank Lemire
> Cc: [EMAIL PROTECTED]
> Subject: Re: FW: Is the live environment down?
>
>
>
>
> When it fails to connect, the address left in the browser window is
> https://tor.opensrs.net/resellers
>
> ???
>
> rr-n1-tor.opensrs.net/~vpop/resellers/ works (thanks) so I think that
> there may be something wrong with your re-direct ;(
>
> Regards
> Lance
>
> On Mon, 13 Nov 2000, Frank Lemire wrote:
>
> >
> > tor.opensrs.net ?  where did you get that from ?
> >
> > it's rr-n1-tor.opensrs.net - and it is up and fully reachable from my
> > testing.
> >
> > resellers.opensrs.net is an invisible redirect to
> > rr-n1-tor.opensrs.net/~vpop/resellers/  for your reference.
> >
> >
> > On Mon, 13 Nov 2000, lance wrote:
> >
> > >
> > > I havent been able to get on to it all day.
> > >
> > > Can get on to http://resellers.opensrs.net
> > >
> > > Then it fails to connect to https://tor.opensrs.net/resellers
> > >
> > > traceroute to tor.opensrs.net (216.40.33.44), 30 hops max, 40
> byte packets
> > >  1  chel-access-1-fma.router.telinco.net (212.1.130.254)
> 0.517 ms  0.452
> > > ms  0.443 ms
> > >  2  chel-border-2-g4-0-0.router.telinco.net (212.1.133.211)  0.727 ms
> > > 0.597 ms  0.584 ms
> > >  3  212.74.111.142 (212.74.111.142)  1.343 ms  1.529 ms  1.317 ms
> > >  4  212.74.111.138 (212.74.111.138)  7.331 ms  7.345 ms  7.519 ms
> > >  5  nyc3.wol-uk.nacamar.net (194.162.254.228)  87.643 ms  85.261 ms
> > > 86.114 ms
> > >  6  chi1.nacamar.net (194.112.31.86)  90.031 ms  101.903 ms  93.328 ms
> > >  7  206.220.243.157 (206.220.243.157)  114.607 ms  120.795 ms
>  112.430 ms
> > >  8  bbr02-g1-0.okbr01.exodus.net (216.34.183.66)  110.981 ms
> 111.185 ms
> > > 114.087 ms
> > >  9  bbr02-s0-0.trnt01.exodus.net (209.1.169.62)  129.098 ms
> > > bbr02-s3-1.trnt01.exodus.net (216.32.173.245)  128.801 ms
> > > bbr02-s0-0.trnt01.exodus.net (209.1.169.62)  125.887 ms
> > > 10  64.39.64.65 (64.39.64.65)  131.153 ms  130.268 ms  131.566 ms
> > > 11  64.39.64.18 (64.39.64.18)  132.888 ms  167.569 ms  137.310 ms
> > > 12  64.39.68.242 (64.39.68.242)  144.279 ms  137.431 ms  133.071 ms
> > > 13  * * *
> > > 14  * * *
> > > 15  * * *
> > > 16  * * *
> > > 17  * * *
> > > 18  * * *
> > > 19  * * *
> > > 20  * * *
> > > 21  * * *
> > > 22  * * *
> > >
> > > contrast with :-
> > >
> > > traceroute to resellers.opensrs.net (216.40.33.39), 30 hops
> max, 40 byte
> > > packets
> > >  1  chel-access-1-fma.router.telinco.net (212.1.130.254)
> 0.539 ms  0.459
> > > ms  0.449 ms
> > >  2  chel-border-2-g4-0-0.router.telinco.net (212.1.133.211)  1.004 ms
> > > 0.651 ms  0.603 ms
> > >  3  212.74.111.142 (212.74.111.142)  1.505 ms  1.351 ms  1.402 ms
> > >  4  212.74.111.138 (212.74.111.138)  7.514 ms  7.515 ms  7.808 ms
> > >  5  nyc3.wol-uk.nacamar.net (194.162.254.228)  126.955 ms  126.845 ms
> > > 130.185 ms
> > >  6  chi1.nacamar.net (194.112.31.86)  184.833 ms  179.771 ms
> 184.358 ms
> > >  7  206.220.243.157 (206.220.243.157)  199.363 ms  194.417 ms
>  184.123 ms
> > >  8  bbr02-g1-0.okbr01.exodus.net (216.34.183.66)  183.897 ms
> 185.639 ms
> > > 188.144 ms
> > >  9  bbr02-s0-0.trnt01.exodus.net (209.1.169.62)  210.364 ms
> > > bbr02-s3-1.trnt01.exodus.net (216.32.173.245)  209.358 ms
> > > bbr02-s0-0.trnt01.exodus.net (209.1.169.62)  220.791 ms
> > > 10  64.39.64.65 (64.39.64.65)  232.566 ms  235.446 ms  237.390 ms
> > > 11  64.39.64.18 (64.39.64.18)  241.626 ms  231.987 ms  226.522 ms
> > > 12  64.39.68.242 (64.39.68.242)  240.452 ms  240.842 ms  233.722 ms
> > > 13  216.40.33.70 (216.40.33.70)  245.029 ms  339.230 ms  288.134 ms
> > > 14  rr-n1-tor.opensrs.net (216.40.33.39)  286.363 ms  284.637
> ms  265.822
> > > ms
> > >
> > >
> > >
> > >
> > > On Mon, 13 Nov 2000, Robert Rivers wrote:
> > >
> > > > The system is working normally. Please report any troubles to
> > > > [EMAIL PROTECTED]
> > > >
> > > > Please include your diagnostics. Traceroutes, etc..
> > > >
> > > > Please don't reply to me directly. I'll just bounce it to
> Support so no one
> > > > can jump the queue.
> > > >
> > > > Thanks
> > > >
> > > > On Mon, 13 Nov 2000, Dennis L. Shreve wrote: >
> > > > > Is anyone having trouble this morning?
> > > > >
> > > > > -----Original Message-----
> > > > > From: Dennis L. Shreve [mailto:[EMAIL PROTECTED]]
> > > > > Sent: Monday, November 13, 2000 9:45 AM
> > > > > To: rrivers
> > > > > Subject: RE: Is the live environment down?
> > > > >
> > > > >
> > > > > Still down from here!
> > > > >   -----Original Message-----
> > > > >   From: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of rrivers
> > > > >   Sent: Sunday, November 12, 2000 4:34 PM
> > > > >   To: [EMAIL PROTECTED]
> > > > >   Subject: RE: Is the live environment down?
> > > > >
> > > > >
> > > > >   Hello,
> > > > >
> > > > >   Apparently there was a high load issue for a few hours.
> > > > >
> > > > >   Thanks to Chuck who told Emergency Support and got
> people working on the
> > > > > issue!
> > > > >
> > > > >   Works for me now. Let us know if you're still having trouble.
> > > > >
> > > > >   At 01:38 PM 12/11/00 -0800, Dennis L. Shreve wrote:
> > > > >
> > > > >     Same here!
> > > > >
> > > > >       -----Original Message-----
> > > > >       From: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Philip Clever
> > > > >       Sent: Sunday, November 12, 2000 11:30 AM
> > > > >       To: [EMAIL PROTECTED]
> > > > >       Subject: Is the live environment down?
> > > > >
> > > > >       I cant get the login page to load.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >   Robert Rivers
> > > > >
> > > >
> > > > ----------------------------------------
> > > > Content-Type: text/html; name="unnamed"
> > > > Content-Transfer-Encoding: quoted-printable
> > > > Content-Description:
> > > > ----------------------------------------
> > > >
> > > >
> > >
> > >
> > >
> >
> >
>

Reply via email to