http://www.ncsu.edu

BYE

9/15/2008 1:06:47 PM

THE SYSTEM IS DOWN

9/15/2008 1:07:24 PM

PWNT

STAY HOME

9/15/2008 1:07:44 PM

Quote :

"OIT - Service - Degradation OIT is investigating issues accessing the http://www.ncsu.edu website and NCSU web services are currently offline due to a system failure. Access to client's web mail (webmail.ncsu.edu) may also be affected with this outage. More information will be posted as it becomes available. Last Update: 2008-09-15 12:59:34 by fpfinch Original post date: 2008-09-15 12:59:34"

9/15/2008 1:07:56 PM

Quote :

"NCSU web services are offline NCSU web services are currently offline due to a systems failure. Please try your request again later. "

PWNT, STAY HOME

9/15/2008 1:09:39 PM

patience. we're working on it.

9/15/2008 1:15:39 PM

patience holmes...we are not all computer wizzes

9/15/2008 1:21:34 PM

also, the website is back online. we're investigating the cause right now.

9/15/2008 1:22:40 PM

Quote :

"also, the website is back online"

false

9/15/2008 1:53:03 PM

k it's up now lol

[Edited on September 15, 2008 at 1:54 PM. Reason : asf]

9/15/2008 1:54:34 PM

Quote :

""also, the website is back online" false"

um, it's up.

9/15/2008 1:56:48 PM

it didnt work for me either when he posted that. working fine now though

9/15/2008 1:57:18 PM

server hax?

9/15/2008 2:03:38 PM

Quote :

"OIT - Service - Degradation --- FOLLOWUP POST: 2008-09-15 14:06:12 --- All services have been restored and should be functioning normally at this time. We apologize for any inconvenience this may have caused. If you continue to have problems, please contact the Help Desk at help@ncu.edu or 515-HELP. --- FOLLOWUP POST: 2008-09-15 13:40:56 --- We are still experiencing issues with web services; however, all mail services have been restored and should be functioning normally. Additional information will be posted once it is available. --- ORIGINAL POST: 2008-09-15 12:59:34 --- OIT is investigating issues accessing the http://www.ncsu.edu website and NCSU web services are currently offline due to a system failure. Access to client's web mail (webmail.ncsu.edu) may also be affected with this outage. More information will be posted as it becomes available. --- FOLLOWUP POST: 2008-09-15 14:06:12 --- Two IMAP servers, uni22map and uni26map, and one AFS server, uni04f, became unresponsive due to IO wait. This typically indicates loss of connectivity to the SMS. Staff were able to resolve the issue, but are still investigating what caused it to begin with. --- ORIGINAL POST: 2008-09-15 13:40:56 --- Last Update: 2008-09-15 14:06:12 by nngenzel Original post date: 2008-09-15 12:59:34"

9/15/2008 2:08:19 PM

i'm using resnet and it's still offline for me

nevermind, once i reloaded it came up, weird

[Edited on September 15, 2008 at 2:20 PM. Reason : .]

9/15/2008 2:19:31 PM

OH JESUS OH GOD

THIS CALLS FOR A SPINNING PHONEBOOTH HACK ASAP

9/15/2008 2:24:13 PM

bttt, anybody else having problems with the homepage? Some of the other ncsu sites work.

10/23/2008 1:55:40 AM

check a few other sites, espn.com seems to be down as well as nytimes.com

I think either RoadRunner is fuckin' up or something awesome is happening

[Edited on October 23, 2008 at 1:57 AM. Reason : well nytimes is back but espn.com is still bouncing for me]

10/23/2008 1:56:56 AM

it works.

10/23/2008 1:57:09 AM

espn, nytimes, and the ncsu page are working fine for me

i'm on roadrunner

10/23/2008 1:57:39 AM

most peculiar

10/23/2008 1:58:23 AM

Open the MyPack Portal, Hal. Hal?

10/23/2008 1:59:28 AM

espn and nytimes worked for me. NCSU still a no go, along with mypack.ncsu.edu. webmail loads, and so does sysnews.

I'm also on RR, in Cary.

10/23/2008 1:59:36 AM

^^ EPIC!

two peeps randomly mentioned RR issues in the last hour to me, one in Charlotte, one in Chape Hill, and the "espn.go.com" site "espn.com" seems to forward to indeed doesn't load for me

I was kind of hoping it was another Warhol worm or something awesome like that

[Edited on October 23, 2008 at 2:01 AM. Reason : *]

10/23/2008 2:00:07 AM

espn.com down for me too

10/23/2008 2:02:42 AM

>ping http://www.ncsu.edu

Pinging uni200v.unity.ncsu.edu [152.1.226.10] with 32 bytes of data:

Reply from 24.93.64.142: TTL expired in transit.
Reply from 24.93.64.22: TTL expired in transit.
Reply from 24.93.64.142: TTL expired in transit.
Reply from 24.93.64.22: TTL expired in transit.

Ping statistics for 152.1.226.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

Ping 152.1.226.10

[uni200v.unity.ncsu.edu]

Round trip time to 152.1.226.10: 50 ms
Round trip time to 152.1.226.10: 49 ms
Round trip time to 152.1.226.10: 50 ms
Round trip time to 152.1.226.10: 50 ms
Round trip time to 152.1.226.10: 58 ms
Round trip time to 152.1.226.10: 52 ms
Round trip time to 152.1.226.10: 50 ms
Round trip time to 152.1.226.10: 53 ms
Round trip time to 152.1.226.10: 50 ms
Round trip time to 152.1.226.10: 51 ms

Average time over 10 pings: 51.3 ms

10/23/2008 2:04:31 AM

do a traceroute and see where it's expiring

10/23/2008 2:05:39 AM

In progress...

10/23/2008 2:06:21 AM

some part of roadrunner's nameserver infrastructure is shitting itself it looks like



[Edited on October 23, 2008 at 2:07 AM. Reason : I am getting bounced lookups for any sites that are "failing to load"]

[Edited on October 23, 2008 at 2:07 AM. Reason : ^ / ^^ / other people: I don't know what ur problem is sry]

10/23/2008 2:06:33 AM

i don't think it's nameservers, it resolved ncsu fine


dig a couple of sites and see what records you get back

10/23/2008 2:07:28 AM

ya I don't think this is related to the ncsu.edu issue

I am easing out of the thread and washing my hands of this because all of the sites I want to browse right now are cached locally and working fine

since I already have the terminal open:

tiberius@shell2 ~/projects/spider-proxy/htdocs $ dig go.com

; <<>> DiG 9.4.2-P2 <<>> go.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;go.com. IN A

;; Query time: 1235 msec
;; SERVER: 24.25.5.148#53(24.25.5.148)
;; WHEN: Thu Oct 23 02:11:18 2008
;; MSG SIZE rcvd: 24


[Edited on October 23, 2008 at 2:11 AM. Reason : .]

10/23/2008 2:09:28 AM

>tracert http://www.ncsu.edu

Tracing route to uni200v.unity.ncsu.edu [152.1.226.10]
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  192.168.1.10
  2    12 ms    17 ms    13 ms  cpe-065-190-128-001.nc.res.rr.com [65.190.128.1]
  3    10 ms     9 ms    12 ms  gig2-3.rlghncj-rtr1.nc.rr.com [24.25.1.149]
  4    12 ms    11 ms    17 ms  pos1-3.rlghnca-rtr1.nc.rr.com [24.25.0.92]
  5     *        *        *     Request timed out.
  6    15 ms    18 ms    17 ms  gig5-0-0.chrlncsa-rtr2.carolina.rr.com [24.93.64.22]
  7     *        *        *     Request timed out.
  8    16 ms    16 ms    20 ms  ge4-0-0.chrlncsa-rtr2.southeast.rr.com [24.93.64.142]
  9     *        *        *     Request timed out.
 10    86 ms    17 ms    41 ms  ge4-0-0.chrlncsa-rtr2.southeast.rr.com [24.93.64.142]
 11     *        *        *     Request timed out.
 12    18 ms    17 ms    14 ms  gig5-0-0.chrlncsa-rtr2.carolina.rr.com [24.93.64.22]
 13     *        *        *     Request timed out.
 14    21 ms    17 ms    20 ms  gig5-0-0.chrlncsa-rtr2.carolina.rr.com [24.93.64.22]
 15     *        *        *     Request timed out.
 16    18 ms    19 ms    18 ms  ge4-0-0.chrlncsa-rtr2.southeast.rr.com [24.93.64.142]
 17     *        *        *     Request timed out.
 18    18 ms    22 ms    17 ms  ge4-0-0.chrlncsa-rtr2.southeast.rr.com [24.93.64.142]
 19     *        *        *     Request timed out.
 20    16 ms    17 ms    17 ms  gig5-0-0.chrlncsa-rtr2.carolina.rr.com [24.93.64.22]
 21     *        *        *     Request timed out.
 22    18 ms    15 ms    16 ms  gig5-0-0.chrlncsa-rtr2.carolina.rr.com [24.93.64.22]
 23  ^C

10/23/2008 2:10:34 AM

LOL EPIC ROUTING LOOP

10/23/2008 2:11:36 AM

Quote :

";; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37759"

lawl

seems like you could fix this if you switched to opendns
208.67.222.222
208.67.220.220


^^lmfao time warner's done got yer packets goin round in circles, boy
thank god for TTL

[Edited on October 23, 2008 at 2:13 AM. Reason : tiberius beat me to it ]

10/23/2008 2:12:41 AM

WTG TIME WARNER

I'm already using openDNS, unless my router is killing it. dd-wrt, with the opendns servers set in the setup page, and also set in the tcp/ip properties on my laptop.

[Edited on October 23, 2008 at 2:15 AM. Reason : openDNS]

10/23/2008 2:12:49 AM

it's not affecting anything I want to use, just shit people I'm talkin' to are trying to use, so my apathy is overwhelming

10/23/2008 2:13:55 AM

plz to explain that gibberish in english?

10/23/2008 2:14:38 AM

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Router A is trying to send your packet to Router B

Router B is trying to send your packet to Router A

Your packet's TTL ("Time To Live") reaches 0 and Router A decides to give up.

10/23/2008 2:16:29 AM

basically time warner's routers don't have a link out (a link to teh intarwebz is down) and haven't yet figured out that the other routers don't either (ripv1 ftl) so they're routing the packets to the other routers thinking that they still have a link out... who have the same problem and route them back to the first router...

and it goes on forever*

*forever = ttl of 0


this is why mesh networks are awesome but can also fail miserably if done incorrectly (which time warner seems to have failed miserably)

[Edited on October 23, 2008 at 2:16 AM. Reason : lol tiberius you're too fast son]

10/23/2008 2:16:36 AM

ping http://www.ncsu.edu

Pinging uni200v.unity.ncsu.edu [152.1.226.10] with 32 bytes of data:

Reply from 152.1.226.10: bytes=32 time=91ms TTL=39
Reply from 152.1.226.10: bytes=32 time=90ms TTL=39
Reply from 152.1.226.10: bytes=32 time=90ms TTL=39
Reply from 152.1.226.10: bytes=32 time=90ms TTL=39

Ping statistics for 152.1.226.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum = 91ms, Average = 90ms

10/23/2008 2:17:49 AM

Quote :

"I'm already using openDNS, unless my router is killing it. dd-wrt, with the opendns servers set in the setup page, and also set in the tcp/ip properties on my laptop."

your problem isn't with DNS - see my explanation ^^

10/23/2008 2:19:13 AM

Yeah, I saw that after I posted. It's a strange issue, you and I are both on RR and in Cary, but mine's busted.

10/23/2008 2:20:39 AM

^^ You EMT and CSC/IT or what?

[Edited on October 23, 2008 at 2:21 AM. Reason : .]

10/23/2008 2:20:46 AM

Just out of curiosity, but can any of you guys get to ESPN.com right now, or facebook? I can't get to any of this shit, and it makes me think the outage is larger than just NCSU.

10/23/2008 2:21:34 AM

I'm just pissed this isn't SQL Slammer : Round 2

10/23/2008 2:21:56 AM

^^^lmao, that's what everyone says.

i'm a volunteer medic and i'm pre-med, going to med school in a year or two
i'm also a systems administrator at sas

i couldn't do things with computers/networks as a career... too boring. for some reason i happen to be good at it, and sas pays well... so, yeah. that's where i am right now.

craaaazy.

10/23/2008 2:22:09 AM

^^A lot of websites will appear down because TWC has problems. I'm able to load fark.com, but can't run a decent tracert.

[Edited on October 23, 2008 at 2:23 AM. Reason : and facebook works for me]

10/23/2008 2:22:36 AM

Oh ok, I was curious why some stuff would load and other stuff wouldn't. I'm on TWC too, damn bastards.

10/23/2008 2:23:34 AM

^^^ Not too shabby. [no homo]

BTW, the Internet isn't the only thing TWC sucks at:

message_topic.aspx?topic=521231



[Edited on October 23, 2008 at 2:25 AM. Reason : .]

10/23/2008 2:23:34 AM

Thankfully TWW still works!

and

set em up

10/23/2008 2:25:41 AM