Thursday, August 28, 2014

phone line chopped - DSL once again hosed

Or at least, that's my guess given that
  1. The gas people dug a hole in our front lawn this afternoon (presumably either in preparation for or as the start of running the horizontal augur-thingie to dig a tunnel from there to the side of our house where the new internal gas pipe exits and where there are fittings for the new meter).
  2. The phone currently has no dialtone, and unlike last time, it's apparently a clean break, as if the phone is not even plugged into the wall); DSL light on the modem is just staying off.
  3. Everybody other than me on LambdaMOO has been idle for 2 hours, so I'm going to guess whatever it was happened around 2:30 or so.

This is, of course, after they did the elaborate survey to figure out where all of the various lines were underneath our front lawn, which was also, like, a month ago, and there have been at least a couple rainstorms since then so all of the markings have faded. Yay.

Century Link ticket now open. Website says to expect someone by 7pm Saturday. Bleah.

Update: (9pm) Got through to a live person. Appointment is now for Saturday morning.

Update: (1:30pm, Sat.) Phone tech still hasn't showed. New ETA: 4pm. Crap.

Update: (3:30pm, Sat.) Phone tech arrived and confirmed that, yes, indeed, there is a clean break somewhere under the front lawn. The gas people, who presumably know where their mole/augur thingie is, will need to dig a hole to expose the ends, and nothing can happen on that front until at least Tuesday. Fortunately it was possible to rig a temporary line via one of the neighbors, so we've got our network back for now.

But I'm guessing this is going to be a fun week.

Thursday, July 31, 2014

DSL hosed

DSL line went down at around 5am. phone company thinks it's an ISP problem, but we've also had no dial tone for the last 12 hours, so I'm dubious about that. On the other hand, if the gas company digging in our cul-de-sac had cut through the phone line 12 hours ago, presumably that would have taken everything out at the same time. Now talking to ISP folks. Well okay, I was talking to ISP folks. Now the chat window is filled with Java exceptionbarf. Time to resort to older tech. Whee.

Update:(7am) Got through to an actual human voice. Ticket actually opened this time; the matter has been referred to "the back office" (hmm). They're supposed to call back within 4 hours.

Update: (1:40pm) Megapath "back office" evidently hasn't gotten to it yet. Escalated. Supposed to call back in 4 hours. In other news, Centurylink is coming tomorrow morning to fix the dial tone.

Update: (5:45pm) Automated call from Centurylink confirms appointment for tomorrow (no time given, just a promise that "all work will be completed by 5pm"). Still no word from Megapath; result of 2nd escalation attempt is that 1st level support guy is thus far unable to reach anyone in the level 2 office to find out what's going on, supposed to call back as soon as he manages it...

Update: (6:30pm) A Comcast salesman randomly stopped by. (I swear I am not making this up.) "I notice you don't get our service", "Yeah, we don't really watch much TV these days", "What about Internet?" "Our needs are kind of specialized" "You need static IP?" "Um, yeah, actually. Multiple." "Well, that's kinda beyond my pay-grade, but here's my card; I can relay stuff to my bosses." "Ok."

Update: (9:45am, Friday) Centurylink tech arrives, notes weird humming noise on the line, guesses that the line is half-broken, thus explaining the lack of dial-tone but allows for at least the possibility of DSL to get through (but almost certainly not at full capacity). ("Um, you know we do fiber that's much faster." "Can you do static IP with no server restrictions?" "<bluescreen>") Goes to look at the junction box at the cul-de-sac, which apparently someone has backed into and is a mess, but apparently the actual problem is farther out (somewhere between there and the junction on Island Crest), so he's gone off to check that out.

Update: (10:30am, Friday) Found the break. Fixed it. We have dialtone. Modem found DSL signal and we are back on the air. Whee.

Sunday, July 28, 2013

more weirdness

went down again yesterday, and of course we were on the road at the time. I think I'm about this close to putting in an auto-restart cron job — bleah.

Tuesday, June 18, 2013

Yeah, there's something weird going on

No PANIC message in the log or anything, it just dies. This has now happened twice in two weeks. I am suitably mystified. Sorry it took me a day and a half to notice this time.

Sunday, June 09, 2013

Is it down?

It feels like LambdaMOO's down now.  I can't get there.  However, our host Rog has a birthday in his household today, so he's got better things to do.  I'm hopeful he'll bring us back soon.

Friday, May 10, 2013

Upgrading to wheezy (Debian 7.0)

I decided to start the upgrade after all. And it looks like I need to do a couple of reboots in the process, so I think I'll just bring Lambda back up when I'm done. ETA 7am (PDT) ?

Update: Well okay, make that 6:10am PDT. We booted successfully with the new kernel. The rest of the upgrade is evidently going to take another 3 hours and since I don't want to be putting you all through withdrawal, the server is back up -- and it's possible I won't actually need to reboot at the end of this anyway, so... enjoy. If we go down again, it'll be around 9-10am, if not then yay.

UpdateUpdate: Did I say 9-10? I meant more like 10-12noon. Sorry. Anyway, it's done; I even got in one more reboot at the end to make sure everything is in a known state, so hopefully we're done with this for a while. @version has been suitably updated.

Saturday, March 23, 2013

Network reconfigured

Ok, the new firewall and new IPs are in place. And the various new IP addresses appear to have propagated through DNS Land. The one beginning with 64 is the one you want.

It may be that some of you are currently connected via the old IP (the 69... one); all this means is that the next time we have a firewall restart and your connection drops there is a remote possibility you'll need to either flush the local DNS cache to grab the new address (ipconfig /flushdns on Windows boxes), or restart your client, or reboot your machine (in which case you might want to consider upgrading to a modern OS) -- but most likely everything that's needed to happen has happened already and a simple reconnect should Just Work.

There's still at least one more server reboot to do once I finish reshuffling the various websites and services. That will probably happen later this week.