You know when grown-ups tell you everything's going to be fine, and you think they're probably lying to make you feel better?
Everything's going to be fine.

Wednesday, May 08


Performance Update

I banned about 700 blogs trying to sell counterfeit sports jerseys and FIFA tchotchkes, and everything is running a lot better all of a sudden.

Posted by: Pixy Misa at 11:20 AM | Comments (2) | Add Comment | Trackbacks (Suck)
Post contains 27 words, total size 1 kb.

Monday, April 29


Question For Users

Anyone else having trouble with the edit functions, like trying to edit a post and it takes you to the post rather than the editor?

I think it was limited to just this site where I'm testing the always-HTTPS changes.  I turned off my custom header template and it fixed the problem.

Posted by: Pixy Misa at 02:20 AM | Comments (4) | Add Comment | Trackbacks (Suck)
Post contains 56 words, total size 1 kb.

Monday, April 15


Site Blorkage

Had some bots scanning the whole of for WordPress vulnerabilities.  No blogs are running on WordPress, so this was an entirely futile pursuit, but the attempt was putting a lot of load on the server.

So I blocked the bastards at the firewall.

Posted by: Pixy Misa at 11:43 AM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 47 words, total size 1 kb.

Wednesday, March 27


The New Bitchute Tag

This is a test post, please ignore the fireworks.

Update: Well, that was easy.



[bitchute=RBnjHfyejg0 size=640x360]

[bitchute=RBnjHfyejg0 size=720x]

Posted by: Pixy Misa at 05:36 PM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 18 words, total size 1 kb.


The New Twitter Tag

It's lazy and doesn't attempt to preserve the tweet details (which I can't do without the Twitter API, and my account is disabled) so if the tweet gets deleted it just ends up blank.  But it's very easy to use: Just paste in the link.

One other note: Firefox's tracker blocker feature breaks this, and there's no easy way around it that I can see.

[twitter=link media=yes|no parent=no|yes]


[twitter= media=no]

[twitter= parent=yes]

[twitter= parent=no]

Posted by: Pixy Misa at 11:46 AM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 69 words, total size 2 kb.

Monday, January 28


Work In Progress

You can see it live here.

Posted by: Pixy Misa at 03:40 PM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 9 words, total size 1 kb.

Tuesday, December 11


Some People Have All The Leak

That memory leak came back and took the site down again.

Why didn't the monitoring system send me an email....  Oh, it did?  Like, an hour ago?  Ugh.  Never mind.

I've increased the server size to 16GB (way more than it really needs, once I track down the leak) and added a daily restart of the application, which will take about three seconds.  Three years of that will equal what just happened, so that's a reasonable tradeoff.  Actually, I think with 16GB of RAM it might not be possible for it to run out; even with the leak it should only ever reach 12GB.

We'll should be moving over to the new server at Christmas, which won't do this.

Posted by: Pixy Misa at 11:11 PM | Comments (6) | Add Comment | Trackbacks (Suck)
Post contains 125 words, total size 1 kb.

Monday, October 22


The Great Undespamming

It looks like about 62,000 comments from earlier this year got caught up in a post-hoc spam filter and vanished.  I've unvanished them, but that leaves us with a secondary problem that some of the comments that got caught by the spam filter were actually spam

And now they're back, and we'll have to de-spam them again.

Exclusive Video Footage of Comments Being Despammed and Undespammed Again

Posted by: Pixy Misa at 01:57 PM | Comments (2) | Add Comment | Trackbacks (Suck)
Post contains 70 words, total size 1 kb.

Sunday, September 16


Performance Glitches

I've noticed some performance hiccups on the site recently, and users might have as well.  I think it's tied to web spiders over-enthusiastically indexing our sites.  

I've updated our logging to try to trap the culprits; I'm not planning to throttle Google or Bing, but if it's Yandex or Baidu causing problems I will stomp on them.

Posted by: Pixy Misa at 12:34 AM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 59 words, total size 1 kb.

Friday, September 07


Speaking Of Servers

I cancelled the server I ordered by mistake and the new server is up and running.  It has the same basic specs with two differences: Instead of 8 x 1TB disk drives on the old server (I misread the specs and thought it was SSDs) it has 6 x 2TB SSDs.  Really real SSDs this time; I've tested the array at 300,000 IOPS, the equivalent of 2500 regular 7200 RPM disk drives.

And instead of 200TB of monthly bandwidth, it's 1Gbit unmetered.  Which doesn't actually make much difference, because 200TB is close to saturating 1Gbit outbound and I don't do much inbound traffic.

Oh, and it's software RAID rather than hardware.

Reinstalling it now, configuring RAID-5 and LVM, so I can take consistent snapshots of the entire server without having to worry about managing clean database dumps of MySQL and MongoDB and Elasticsearch and and and...

Then I install KVM and LXC, then I start migrating systems across into their own neat little virtualised containers.

Update 1: Manually configured RAID-1 for boot and RAID-5 for LVM, splotted swap volumes everywhere, and installing Ubuntu 18.04.1 right now.  The auto-install script unhelpfully assigns 100% of the default volume group to / meaning you have no room left to take snapshots.  I hope I got it right, but at least the partitioning is right so it will be a lot easier if I have to reinstall again.

Update 2: The secret is to use the autoinstall to bring up the server quickly, then use fdisk to create your custom partitioning scheme, then use the Ubuntu expert install mode to install on those partitions.  Much much quicker than fiddling about with the partitioning tool in the installer.

Also, don't install to a huge software RAID-5 or 6 array, even on fast SSDs.  It takes at least five times longer than normal because the sync will be running the entire time.  Create a RAID-1 array for the OS and you'll be done that much faster.

Update 3: Whee!  That was so much faster.  Let's see if the network config works this time...

Update 4: Yep, that worked perfectly.

Update 5: Well, I messed that up slightly.  I think I'll just go with LXC here, and leave KVM alone.

Posted by: Pixy Misa at 06:12 PM | No Comments | Add Comment | Trackbacks (Suck)
Post contains 376 words, total size 3 kb.

<< Page 1 of 42 >>
56kb generated in CPU 0.09, elapsed 0.2638 seconds.
53 queries taking 0.2152 seconds, 201 records returned.
Powered by Minx 1.1.6c-pink.
Using https / / 199