solarbird: (molly-content)

Today Anna and I upgraded all the servers in the servercore with MST3K in the background and had some pizza made by Paul and some pie made by a grocery store.

And it was a really nice day.

I am so pleased that (with the help of the Mastodon discord on that server) we got all the server OSes upgraded and back up and running and cleaned up some stuff while we were at it.

Just being able to… get some stuff done without it being a goddamn nightmare or a huge fight or anything. Just mostly sitting around and chatting some while upgrading stuff and getting things that broke working again without too much of a fuss.

could use days like this more often, not gonna lie

how was your day?

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (gaz)

HEY TEAM WE’RE BACK

actually got power back yesterday but while a bomb cyclone is not a real bomb it can make a real mess just the same

I’ve got a lot of catch-up to do but we’re getting there. Kinda had to move some network and UPS bits around after coming back up and some parts honestly I’m not sure why. But everything’s behaving today so I think we’re good.

How’s your Friday been?

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (molly-thats-not-good-green)

Massive windstorm this evening in Cascadia has taken out our power; we lasted, honestly, longer than I thought we would. But we are definitely now out. This should federate out to most of our followers, though, since we have like an hour of battery backup that we’re chewing through right now..

We’ll come back when power does. If you’re local, well, good luck out there.

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (molly-thats-not-good-green)

So, uh… if you use polyfill dot io to help power your websites, are you aware of the bad shit going down?

You should be, because it’s very bad. Malware injection bad. Details here.

(Renaud – the author of this post set – is one of the dev team at the Mastodon nonprofit. He’s not the only one talking about this, I just trust him.)

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (molly-computer-all-lit-up)

I haven’t seen this mentioned here but if you haven’t updated Windows this week, DO THAT NOW

Like seriously, right now.

no

right now

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (pingsearch)

Now that we have substantially more users than just ourselves again – this was a thing back in the day, we had a peak of like 40 users – we kind of need a status page so we can warn people about nontrivial shit or that we’re going offline for some reason like losing power.

So:

  1. Our mail server already has web services on it for list management
  2. Add a local wordpress instance there, which means it’s not on the main web or mastodon servers
  3. Federate that with an address something like at status at status dot murkworks dot net)
  4. Have the mastodon.murkworks.net librarian account follow it
  5. Have posts to it also go to the various mailing lists we host so they know directly

Which means:

  1. If our mastodon server goes down, people could check status dot murkworks dot net and see the wordpress version
  2. If the main web server goes down that wouldn’t affect status
  3. If status itself needs to go down, since it’ll be federated and followed (by the librarian) on mastodon.murkworks.net, people can check the status account there to see what was last posted, which – if we take it down in a controlled manner for things like a major upgrade – they would still be able see, and therefore, they could read the last status message
  4. If anyone not on our instance follows the status user (and I would ask someone to do that for this purpose) then people would be able to do the same thing checking on that system’s server. I think. (As would anyone following it themselves of course.)

This is me using caching to bridge downtime to keep status information available under as many circumstances as possible, basically.

(Well, without having to hire some sort of off-site hosting which we can’t afford right now anyway or using some rando account someplace which is kind of what we’ve been doing and which I’d prefer not to do.)

It’s the “federated wordpress blog” part that makes this viable.

Am I missing anything important?

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (tracer)

2024/2/14 10:13am: I’m so glad that worked. We’re back. And we also have a security update to apply. I can handle that, as long as we are, as they say, _back online_.

2024/2/14 4:09am: It’s not a great overnight here at the mighty mighty murkworks. Our mastodon server, mastodon.murkworks.net, has been taken down by FUCKING SanDisk; the drive went from “Everything’s fine!” to “lol fucked” in 0.0 seconds, panicked the kernel, marked itself “24 hours good luck” and closed off the top of the well.

The good news is the drive is responding to queries and I’m currently ripping the important partitions. If this doesn’t work, yes, of course we have backups, but that’s a lot more hands-on and I can’t sleep through it like I can this. If things go very, very well, we’ll be back up… maybe 10am Cascadian/Pacific time Wednesday morning? Probably closer to 11.

I do see replies to this post and can reply to those replies. Ironically, the only people who can’t see this are the people who need to see it most, our users. Lol.

This post will be updated as events warrant.

@moira

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (zoe-and-doctor-and-brig)

Yes, this is a startup syslog on a debian machine wherein DHCPD is reporting that it can’t come up because eth1 isn’t set up with a subnet getting interrupted by the kernel informing us that eth1 has been set up with a subnet followed by DHCPD going back to telling us how it can’t come up because eth1 isn’t set up with a subnet.

goddammit debian

Posted via Solarbird{y|z|yz}, Collected.

solarbird: Brigitte Lindholm from Overwatch (brigitte)

BEST THING: when your networked ancient but non-DRM laserprinter has been crashing on certain PDFs for months so you think there must be something new in PDFs and maybe it’s replacement time BUT

you discover your printer has room for RAM expansion so you check and it’s at minimum configuration so maybe it’s just running out of RAM so you buy some old compatible RAM off eBay BUT

before you install it you try to find some old PDFs that crashed the printer so you can know if new RAM actually fixed anything and you try printing them again before installing the RAM because you’re smart like that AND

…none of them crash it anymore.

goddammit printers

why

Posted via Solarbird{y|z|yz}, Collected.

solarbird: (vision)
hm hm hm I think I made a mistake setting up mastodon

so i usually set up my servers to have a separate /home partition and naturally did that here too, with a / of 30gb, which is normally totally fine, i run lean installs.

the problem of course is that postgresql is storing the local database in /var/lib, oops. so we're fine for now but not forever.

is there any reason not to create /home/postgres, clone /var/lib/postgres contents over, and softlink /var/lib/postgres to /home/postgres?

or is it better to clone then edit postgresql.conf to point to /home/postgres?

eta: another mastodon instance administration told me to clone then edit postgresql.conf because system call reasons. and it worked! very cleanly too. genuine "phew" moment lol
solarbird: (vision)
I

finally

got iOS to let go of an expired certificate that it kept insisting upon using in place of the actual cert on the server

and

finally got both the mail and mail-relay servers to use the automatically-updating certificates

and

got the auto-updating certificates to maintain usable permissions so that all of the above could actually happen.

goddamn that was a pain in the arse.
solarbird: (bubbles-is-hardcore)
here's something very slightly funny:

so amongst comcast business's many failures, the cherry on top was breaking our phone line for weeks so we couldn't get incoming calls, yeh? and we didn't know.

we discovered it when their dispute office couldn't call us and had to email.

(as always, let me take a moment to say: friends don't let friends do comcast business)

as near as I can tell, we were not receiving calls for most of march. we were getting calls in february, but not after that.

that's where the accidental favour comes in.

the line is back up, on another provider. but we're getting a lot, and I mean a _lot_, fewer spam calls. and i'm kind of wondering if by breaking incoming calls for a month they triggered a lot of line-disconnected routines and took us off a bunch of illegal spam lists.

(i say illegal because they are; we're on the do-not-call registry but there's a whole class of fuckwits who don't give a rat's ass about that.)

but we've literally not got a single spam call since coming back up. not one.

it used to be something by which we could set a clock.

i mean, obviously, it'll build back up over time as robocallers and spammers explore working numbers, and i've almost certainly jinxed it and there'll be a call any second now.

but still. they kind of hit the reset button for us. accidentally. while blocking all calls.

in this case, honestly?

i'm okay if we lost a couple of babies.

we got rid of a _lot_ of bathwater.

eta: yes, this means we won.
solarbird: (korra-on-the-air)
From Twitter, as usual for these rants where I'm trying to get a company's attention.

So today's @ComcastBusiness adventure is they want to charge us over a thousand dollars (>$1000) to disconnect service.

That'd be the service they kept breaking on their end, taking us offline 2-6 days at a time, four times between October and January.

https://solarbird.dreamwidth.org/tag/murknet

The link points to writeups of their failures.

I must note that we did sign a term contract at a time when we had no other options, but still: we sign up, @ComcastBusiness starts taking us down over and over again for days each time.

Without compensation, if that matters.

Now to me, that sounds like breach of contract, failure to provide service.

I mean, sure, service is there the _majority_ of the time, but @ComcastBusiness really did make that "nine fives of service" joke into reality, and that's unacceptable business internet service.

The cherry on top of all the other cherries on top - ignoring us, closing trouble tickets, telling the woman who ran a division-level mail server room at microsoft to "talk to [my] local IT about this," and so on - was trying to charge us $100 to fix their mistake the last time.

We _were_ able to make @ComcastBusiness reverse the $100 charge for fixing the latest mistake _they made on their end_, but now that we're finally set up on another provider, they want $1000 to go away.

We're considering our options.

Now, I'm not saying I'm asking for a legal opinion, but I am wondering whether @ComcastBusiness's repeated failure to provide service on this scale without compensation does in fact breach contract sufficiently to void the contract.

@KathrynTewson for no reason in particular ^_^

I also know we're not the only ones @comcastbusiness have treated like this. I've talked to others who just gave up and walked away. Maybe we'll end up doing that. This has been a several-month nightmare, and I'm an individual, not a corporate monstrosity, with other work to do.

And @ComcastBusiness pays people at scale to do this sort of customer-screwing, it's their jobs.

Mind you, we were even willing to keep the associated phone service. We wanted to move it consumer since it's not actually a business line, but we were willing to keep it, because basic POTS? That, apparently, @ComcastBusiness can manage.

But internet with fixed IP? Hoo boy no.

And that's when @ComcastBusiness said "Pay us $1000 to go away."

What an absolute trainwreck of a company.

Anyway, like I said: we're considering our options.

But I know this much:

Friends don't let friends do @ComcastBusiness.

eta later:

I just thought of something vaguely amazing about this $1000 BS.

We said we'd keep phone service, albeit moved to residential. (It's not really a business line.) That works out to $1500 in their pocket over the contract.

$1500>$1000.

@ComcastBusiness can't even chisel right.
solarbird: (Default)
We got a visit, finally, from a technician bringing a new modem.

He verified everything I'd reported, started pinging our modem from the corporate side, and when it powered off... he kept getting responses.

Another modem had our modem's fixed IP address.

They hadn't reset it before redeploying it last Thursday.



Obviously, this is infuriating. Fourth major outage since October, this one another five day clusterfuck, ALL caused by Comcast Business, but the _most_ infuriating part has been being ignored, lied to, and told over and over again it was our problem and to talk to my "local IT."

Hands up for the on-site tech, who gave me no bullshit or pushback, who agreed the modem was behaving bizarrely and was speculating about possible problems with the modem when he saw that he could still ping an unplugged device and knew what had happened immediately. Good job.

The _only_ "good job" I can hand out here on their side.

This has been yet another disaster.

Five days down because they didn't reset a modem they redeployed.

Five days of insulting, dismissive, infuriating "support" from Comcast Business, blaming it on us.

Again.

I'm not tagging Comcast Business directly on this because I honestly don't know if they'd blame the on-site tech or some other bullshit. I just don't. Who even knows? They're this horrible to their customers, what are they like to their employees?

So anyway, yeah.

We're back up.

Five days later.

Because Comcast Business fucked us again.

Ziply put in a temporary fibre cable for us today, btw. Wasn't expecting that. It's on the ground, which isn't great, but not where anybody will hit it, so... it's fine.

We should get actual installation on Thursday, then they'll come back later and put in the final cable.

Looking forward to that.

A _lot_.
solarbird: (Default)
This is long past being funny.

Dear @ComcastBusiness, regarding your latest blowing off our 3 days and counting of complete lack of IPv4 connectivity and your several closed tickets, the latest of which being CR020322088:

"I have verified that all of your Comcast internet services are working correctly."

Your gateway is moving ZERO IPv4 PACKETS. NONE. IPv6 moves fine. IPv4 does not.

I have told you this, repeatedly.

"I am able to login to your Comcast gateway and reach websites from within your gateway."

Yes, I know.

Do you know, @comcastbusiness, who told you that IPv4 could communicate with the gateway?

I DID.

I. TOLD. YOU.

The problem is IPv4 can't _cross_ the modem from the LAN.

"I am getting solid pings/signal from your Gateway Static IP and all signal levels are in the green."

Yes. I know. How do I know? I TOLD YOU ABOUT IT.

When I could log into the gateway.

Which, from the LAN side, I often can't. It refuses all logins.

I told you that, too.

"There is nothing I am finding that would cause the intermittency you are experiencing."

What we are experiencing, @ComcastBusiness, is COMPLETE FAILURE TO PASS IPv4 AT ALL TIMES.

Being able to pass IPv6, while cute, is not "intermittency." We have been down for THREE DAYS.

We have been down, @ComcastBusiness, for THREE DAYS, with ZERO PROGRESS ON YOUR SIDE.

This is the FOURTH MAJOR OUTAGE SINCE OCTOBER and you are STILL not LISTENING TO US.

"The best way to test your services would be to directly connect a single laptop or PC to the back of the Comcast modem... and run a speed test at http://speedtest.xfinity.com."

Hard to run an IPv4 speed test when you pass zero (0) IPv4 packets, don't you think?

"If you direct connect and are getting the correct speeds (100MBPS DOWNLOAD/15 MBPS UPLOAD) this means the issue could lie somewhere in your networking equipment or we have too many devices connected."

OUR SPEED IS ZERO.

YOU ARE PASSING NO IPv4 PACKETS FROM THE LAN SIDE.

NONE.

What's it take, @ComcastBusiness?

In the last three days you've told us our modem is broken but you won't send us a new one, that our modem is fine and that it's our fault (spoiler: it's not) and that we need to do speed test on a modem which passes NO PACKETS from the LAN.

And - and - @ComcastBusiness you have to understand - your side has managed to diagnose NONE OF THIS.

I told _you_ the modem can pass IPv4 from _itself_ to the WAN. I'm fully aware the modem can pass IPv4 from itself to the WAN!

The problem is it can't move them from the LAN.

We got the same runaround the previous 3 major outages since October too, btw, @ComcastBusiness - but this one's even more insulting because it is a _complete_ outage. The last time, we had _some_ service.

Now the only service we have is IPv6 and attacks on my blood pressure.

At this point, @ComcastBusiness, we're three (3) days into a complete outage and you're back to telling us nothing is wrong because some intern managed to get the modem to send an IPv4 ping.

Which I TOLD YOU IT COULD DO.

Here's me telling you, @ComcastBusiness, on Friday, that the modem could pass IPv6 traffic but not IPv4 from WAN to LAN, and that the modem itself could pass IPv4 traffic. Remember this? You confirmed it was added to the ticket!

Of course, you closed that ticket too.

"I would recommend that you start with basic troubleshooting, and restart all of your equipment or contact your IT professional."

I RAN A DIVISION-LEVEL MAIL SERVER ROOM AT THE MICROSOFT CORPORATION.

I AM THE LOCAL IT PROFESSIONAL.

YOU KNOW THIS. My god.

(It was the smallest microsoft division at the time, but nonetheless, it's still true.)

"Alternately we can schedule a technician visit to verify that your services are working properly but if it's beyond the modem the technician can charge a $99.95 service fee due to not being a Comcast issue."

@comcastbusiness why you gotta hurt me like this?

You told us last night @comcastbusiness that you could see the modem was malfunctioning and needed to be replaced.

You also told us you wouldn't send a technician and also wouldn't send us a replacement modem.

Is this @AGOWA time or what?

Are you ever going to move IPv4 packets again?

I need to know, @comcastbusiness. This is our 4th major outage since Oct, all of which you blamed on us but were your fault, & you won't even acknowledge a problem. We are 100% down for 3 full days and counting.

Is it @AGOWA time?

Because at this point, @ComcastBusiness, I kind of have to act on the idea that you're never moving another IPv4 packet again and we're just going to be down for... at least another week. Probably two.

Friends don't let friends do @ComcastBusiness.

Hey, @ZiplyFiber - are your sales offices open on Sundays? Because I got some answers from your business tech people last night without even having a business account and they were the right answers.
solarbird: (Default)
So predictably, Comcast Business Internet didn't call us as they'd scheduled, and at that point I was presuming we were fucked for at least the weekend, so I went back to trying to arrange a solution to drive our wired LAN by the shared access point on my phone.

This sounds hilariously doomed, and I described it as such on Twitter, but I'd been inching closer to pulling it off for a couple of days as I experimented with it, and then once I had my best possible shot I pulled the trigger...

...and it works. Holy hell it works. It's shaky, not gonna lie, and it's slower than even Comcast, and the latency is a bit of a mess, but... it works! We can even stream video using it, it's fast enough for that!

It's the fourth major outage since October, btw. All four their fault. But if I can get some percentage of our client machines back online, that's something, right?

Right?

We've shelled out a bunch of money to boost our wireless data quota, which sucks, but hey, if Comcast can't give us packets, we've got to get them somewhere. Our servers are all offline, but by god, we have printers!

(And also gaming and file sharing and shit. You know. Basics.)

Oh, the reason we know this latest one is also Comcast's fault is because Anna called and ripped 'em a new one while I was putting all this stuff together. Normally, I'm the bad cop... okay, I'm still the bad cop. That was Anna being the good cop, which tells you had mad they made her.

Anyway, I was listening to Anna talking to them, and found out that all our trouble tickets get keep getting closed because they've decided our modem is broken - probably correct - but they aren't willing to send us a new one to install ourselves and can't send a tech out here with a new one so we're just screwed.

Literally no one has told us this until now. Apparently the fault was detectable on Friday, so they knew even as they were telling me the modem was fine and it was our equipment's fault.

Being told that, by the way, is what got me to write the SICK OF YOUR SHIT ROLL CALL post because I damned well knew better. And apparently, so did they. But at least now we know why the problem tickets keep getting closed.

Phenomenal work. Absolutely phenomenal.

Anyway, we've been up a few hours now, and I absolutely can't believe my single-point shared-network phone to wired ethernet bullshit is staying up this long. It's like, the hard part is keeping it from exploding, and yet... so far... it's... well...

It's not actually stable?

But it's doing a pretty decent job maintaining the illusion of stability.

And I kind of respect that.
solarbird: (Default)
The photos are gone because fucking Comcast Business keeps taking us offline and can't get us online again for days every time they do it.

The photos will be back when Comcast Business takes its boot off our connectivity's neck again.
solarbird: (Default)
After a couple of hours of trying, I finally got Tier 1 support to add the current situation to the current ticket. I did have to change the ticket number because they closed the original one without telling us, so that was great. And then they opened two others, one for tier 1 and tier 2. But in theory, this is on the tier 2 ticket now. Yay!

That's nearly two hours to get this text added to a ticket though. Jesus.

-----

The modem is not passing IPv4 packets across LAN to WAN. It _may_ be able to send IPv4 packets from _itself_ to the WAN, and it _can_ pass IPv4 packets from itself to the LAN, but it DOES NOT pass IPv4 packets _across_ LAN to WAN or (as far as I can tell) vice versa.

A simple test is using my laptop connected by wire directly to the modem, configured by the modem's DHCP. If I attempt to query your nameserver via IPv4 from this laptop, it _always_ fails. If I attempt to query your nameserver via IPv6 from this same laptop, it _always_ succeeds. See attached screencap.

The reason I believe the modem can talk IPv4 over the WAN is because if I use the built-in IPv4 ping functionality via the web interface, it reports success. Since it does so without details, I cannot be sure it's actually succeeding, as the administrative software is unreliable. But I suspect it's working.

However, any otherwise-identical attempt from the LAN side of the modem to use IPv4 pings to the same servers fail, 100% of the time.

The modem is showing other signs of IPv4 routing irregularities. I will describe one now:

If a laptop is connected to the LAN side of the modem with modem-issued DHCP address, pinging our fixed-IP machines on the same (LAN) side of the modem will sometimes work normally, sometimes succeed with great delay in ping issuance but _not_ response time, sometimes succeed with routing error complaints on some but not necessarily all packets, and sometimes (but rarely) fail outright, all within a few minutes of each other with no configuration changes.

The modem is showing other signs of irregular behaviour as well. I will describe the main one now:

The modem is sometimes refusing logins when given valid login credentials. If your support team resets the password to default, the default password will also not work, regardless of the number of resets.

I have discovered today that if one is attempting to login via the fixed IP (173.160.243.46) and it does not work, it will _probably_ work if one does exactly the same login attempt on the DHCP root address (10.1.10.1).

The same is also true in reverse. If login via the DHCP root address (10.1.10.1) is failing, trying exactly the same login via the fixed IP (173.160.243.46) will _probably_ work.

If there is a reasonable explanation for this behaviour other than modem failure, I am not seeing it.

For these and other reasons, I am strongly suspecting that the modem is not taking provisioning properly, regardless of what it is reporting. The only reprovisioning from your side that I have seen have any effect at all is a full factory reset from remote. (My attempt to do a factory reset via the front panel failed - as in, didn't seem to work at all - and as this was when it was refusing all logins, I could not try via the customer administrative access panels.)

At this point we are down for just short of 24 hours and we yet again request escalation to Tier 2. Tier 1 have demonstrated yet again that they are NOT CAPABLE of solving this problem, and this is our fourth major network outage caused by your side since October, all previous lasting between 2 and 5 days, this one so far only 1 day.

The ticket number, again, is [deleted]. Please add all of the above to the ticket. Thank you.
solarbird: (Default)
Yeah. I tagged 'em. At this point, why the hell not?

SICK OF YOUR SHIT ROLL CALL:

1. "This isn't on our side, you should talk to your local IT about this."

A: It's been on your side EVERY TIME. Eventually, Tier 2 fixes it.

B: I AM THE LOCAL IT. I ran the WGA division server room at Microsoft. I HAVE SOME IDEA WHAT I'M DOING.

2. "Have you power-cycled your modem?"

Classic.

3. "Are you sure you have the right password?"

You reset it to factory default. Three times. It won't start magically working.

4. "Windows should be restarted."

My fleet of Linux servers glares at you angrily.

5. "I'll re-provision the modem. Wait five minutes and try again."

That didn't work the last four times, why is it going to work now? Oh look, it didn't.

6. "Someone will call you Monday."

[No call]

"Tuesday"

[Calls wrong number]

"Wednesday"

[Tier 2 shows up and fixes it]

(If we're lucky. I think the quickest we've been back up was two and a half days.)

7. Me: "[X] in Tier 2 told us you need to do exactly this, and can do that."

Tier 1: "We can't do that."

[tries again]

Tier 1: "All done!"

[nothing actually done]

8. [support wakes up from idle after hours of silence and apparent inactivity] “Is it fixed yet?”

No. No, as you have apparently done nothing, it is not fixed yet. The problem will not magically go away. It. Is. Not. Fixed. Yet.

Honestly, and I mean this in all sincerity, it has felt _many times_ like we've been being trolled.

Tier 2 is generally good to great and totally know what they're doing. Nice people.

Tier 1 - by phone and online - was not always a nightmare. I remember this. But it is one now.
solarbird: (Default)
Just tried to talk to Earthlink, in case they have fibre in our area yet and the evaluation services aren't aware of it.

After working my way through a _particularly_ nasty phone tree - seriously, who thinks fake typing sounds are a good idea - I reached someone.

It sounded like a Russian phishing sweatshop in there, for reals. I suppressed my laughter.

Ivan - or whoever - had to look up whether they offered fixed IP services on their business services, and came back after a reasonable period to confirm they did. So I gave him name and address and general requirements so he could look up our service location.

And he did some, and I was on hold for a couple of minutes, and he came back and said he would have to transfer me to his "Business people."

Except he answered on the "Business service" phone tree himself, and identified as that, so... that's fun. But I say okay.

Then I get a bit of hold music, and then SHARP METALLIC HORN NOISE RIGHT IN MY EAR, then more hold music, then a partial play of an recording that used the phrase "invalid transfer," and then I was abruptly disconnected.

So that went well.

We have all kinds of choices. As long as they all suck.

And again: this is the _sales_ experience.

Their support rating is _terrible_. I bet I can guess why.

April 2025

S M T W T F S
   1 2 3 45
6 78910 1112
131415 16 1718 19
20 212223242526
27282930   

Most Popular Tags

Syndicate

RSS Atom