LittleBITS: Why You Got Multiple Copies Last Week

Originally published at: LittleBITS: Why You Got Multiple Copies Last Week - TidBITS

My apologies to those who received multiple copies of last week’s TidBITS issue! As-yet-unexplained problems overwhelmed our server early in the initial send, causing it to reject all connections for 5 or 10 minutes. When it recovered, only 3,600 copies of the 23,427 total had been sent, and Sendy, our email distribution software, wasn’t automatically retrying as it’s supposed to. You can imagine my distress.

When our developer was able to take a look several hours later, he couldn’t see any reason for the problem, so we created a duplicate campaign in Sendy, added a short parenthetical in the issue blurb apologizing for the resend to those who had already received it, and resent.

Then I watched Sendy work through the sending process while keeping an eye on our server’s load average (a measure of how busy it is; it had been sky-high when connections were being rejected earlier). Although the load average went uncomfortably high while sending (up to 11, when it should ideally stay below 2 on a 2-core server), Sendy chugged through until it had sent 23,427 issues. I assumed it was done and went to bed.

Unfortunately, something else had gone wrong, and the server kept pushing out copies of the issue—shades of “The Sorcerer’s Apprentice”—so some people received as many as 10. By the time I got up in the morning, it had stopped, and everything seemed back to normal, apart from all the reader messages alerting me to the problem. As much as I appreciate the effort, rest assured that someone else will undoubtedly have notified us. If you notice something weird like this in the future, check TidBITS Talk to see if I’ve commented on it yet.

Throughout the rest of the week, our smaller email distributions—articles sent to TidBITS members and the Japanese and Dutch translations—went out correctly, except for one Watchlist item that’s still trying to send to the last 61 users after three days. I just restarted the server to see if that helps.

I hope this issue sends properly, with everyone receiving just a single copy, but if not, you’ll know the gremlin plaguing the server is still up to its mischief. Just delete any extras.

1 Like

No worries! Technology is great until it isnt’t.

2 Likes

As much as I appreciate the effort, rest assured that someone else will undoubtedly have notified us.

Except… if we all took that to heart undoubtedly nobody would have notified you. :slight_smile:

Here are the steps to take when you notice a problem on the site:

  1. Check to see if anyone else has reported the issue.
  2. If not, report it.
  3. Check the previous reports; if you have something significant to add, then post.
  4. If not, live your life.
2 Likes

Thanks Adam. IIWII. I appreciate TIDBITS!

David Tuma
Captain, USN, Retired

Your verbiage of the problem, the timing and inability to see a cause points to an issue triggered by the change to DST.

As in:
Time since last DST PROBLEM = -1 hrs.

I’m confident that with tens of thousands of readers, someone will say something, and of course, Tonya and Lauri and many other close friends receive TidBITS too. :slight_smile:

Not inconceivable, but our server has gone through many DST changes with no issues, so I’m not sure what would have been different with this situation, which was also more than 24 hours later.

That said, count me firmly in the camp that would like to see DST-related time changes relegated to the slag heap of history.

Server software should work entirely in the realm of UTC timestamps, in order to avoid the mess of DST. Especially since the transition dates and intervals vary around the world, according to both location and year and change based on political decisions, which are inherently unpredictable.

Yep. Standard time, all year 'round. Minimize the number of days where I’m forced to wake up before dawn. And many groups are claiming that it’s healthier as well (but I’ll leave that argument to others - I just want to wake up after sunrise every day).

2 Likes