All The Tropes Wiki Project, Part XXXI

[GethN7]

No word yet back on the Checkuser.

If we get any confirmation or if the balance of evidence confirms it's our socking friend (if they are using proxies of some sort), then no mercy. They made clear what few lenient rules we have mean nothing to them, and thus they mean nothing to us save a blight to be banished.

[MilkmanConspiracy]

Looking on Meta, the checkuser went though - They confirmed it’s a sockpuppet and are administering a global ban.

[Bob Schroeck]

Okay, then. That means all his edits in the Mod Queue get autonuked.

EDIT: Done, and just as a cherry on top tagged him as a spammer. Not that it'll do anything given that the account's globally blocked, but it makes me feel pleasantly vindictive. <grin>

[robkelk]

Okay, then. That means all his edits in the Mod Queue get autonuked.

EDIT: Done, and just as a cherry on top tagged him as a spammer. Not that it'll do anything given that the account's globally blocked, but it makes me feel pleasantly vindictive. <grin>

Don't forget to block him locally, to give his IP address a one-week block at the same time.

[Bob Schroeck]

Okay, then. That means all his edits in the Mod Queue get autonuked.

EDIT: Done, and just as a cherry on top tagged him as a spammer. Not that it'll do anything given that the account's globally blocked, but it makes me feel pleasantly vindictive. <grin>

Don't forget to block him locally, to give his IP address a one-week block at the same time.

<nod> Thanks for reminding me. Done now.

[robkelk]

Miraheze is down - I'm getting "Bad Gateway" errors on all wikis except Phorge.

Phorge ticket T13097 filed.

[robkelk]

They're back online.

I've said as much in the ticket, and pointed out that the root cause still needs to be identified and mitigated.

[Bob Schroeck]

I'd go see what you wrote, except following that link gives me:

Unhandled Exception ("AphrontQueryException")
#1021: Disk full (/tmp/#sql-temptable-109d1f-17679d6-0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")

So... yeah.

EDIT: Despite this, meta and All The Tropes are still up... <shrug>

[robkelk]

That probably explains the root cause - somebody hasn't done garbage collection and disk compression for a while.

[robkelk]

And it's happening again, almost exactly 24 hours later. Somebody's already closed the ticket - should I re-open it or open a new one?

[MilkmanConspiracy]

Can confirm I’m also experiencing issues with the site.

[MilkmanConspiracy]

Appears to be back up

[robkelk]

And it's happening again, almost exactly 24 hours later. Somebody's already closed the ticket - should I re-open it or open a new one?

Three days in a row, at the same time of day each time... I've updated the ticket but see no way to re-open it.

[robkelk]

I noticed this line in the recent changes log:

04:12:44 User rename log NotAracham talk contribs block renamed user 123miky456 (0 edits) to Iloveapples1078 ‎(Requested (Steward action))

I think we might need to watch this one, in case it's another "ilove*" ban-evasion account.

[Bob Schroeck]

I noticed this line in the recent changes log:

04:12:44 User rename log NotAracham talk contribs block renamed user 123miky456 (0 edits) to Iloveapples1078 ‎(Requested (Steward action))

I think we might need to watch this one, in case it's another "ilove*" ban-evasion account.

Another one we might want to keep an eye on is Kanchusimi -- if only because their username sounds like "Can't You See Me?"

[robkelk]

And it's happening again, almost exactly 24 hours later. Somebody's already closed the ticket - should I re-open it or open a new one?

Three days in a row, at the same time of day each time... I've updated the ticket but see no way to re-open it.

Four days in a row. I've updated the ticket... again.

Does nobody at Miraheze actually know how Incident Management is supposed to work? Re-open the God-damned ticket and keep it open until the issue has actually been confirmed to have been fixed!

[Bob Schroeck]

<sigh> At 1:15 PM EST, ATT disappeared, and any attempt to reach a page there displays "Wiki not found - We couldn't find this wiki. Check your spelling and try again."

EDIT: It came back about a minute later, but still...

[robkelk]

The upgrade to MediaWiki started at 1:00 PM and ran until c.2:05 PM. There was a big banner on every wiki all weekend.

I don't know why Miraheze is down now though...

[robkelk]

Database connection errors on all wikis that I checked, including Meta.

They didn't already have a ticket for this, so I created one. T13133.

(You know, there's noting in ITIL that says you can't create a ticket without a user report...)

[Bob Schroeck]

The upgrade to MediaWiki started at 1:00 PM and ran until c.2:05 PM. There was a big banner on every wiki all weekend.

<facepalm> Forgot entirely about that.

[robkelk]

They didn't already have a ticket for this, so I created one. T13133.

Wikis are back and ticket is closed. The database server was acting up.

[robkelk]

I noticed this line in the recent changes log:

04:12:44 User rename log NotAracham talk contribs block renamed user 123miky456 (0 edits) to Iloveapples1078 ‎(Requested (Steward action))

I think we might need to watch this one, in case it's another "ilove*" ban-evasion account.

Another one we might want to keep an eye on is Kanchusimi -- if only because their username sounds like "Can't You See Me?"

Kanchusimi has been making productive edits so far.