Due to a problem with our spam filtering system, some customers received blank incoming messages between 11:35 and 11:53 AM (Pacific time) this morning.
A non-blank copy of these messages was also properly delivered (although with a delay), so no mail is missing.
We have permanently fixed the underlying cause of the problem, and we apologize for the concern and annoyance this caused.
We’ve updated rsync to version 3 on our servers. (We’re using Debian version 3.0.3-2, which includes patches from rsync 3.0.4.)
Rsync 3 is significantly faster than previous versions for recursive file transfers (which we use in our backup system). However, the new version is backward compatible with rsync 2.x, so users shouldn’t notice any changes or problems, even if you haven’t updated your own copy of rsync.
At approximately 11:00 PM Pacific time this Saturday night (September 20), all Tiger Technologies servers will be restarted. As a result, customer Web sites and e-mail service will be unavailable for three to five minutes.
No e-mail will be lost, of course; incoming mail will just be delayed for a few minutes.
This brief maintenance is necessary to upgrade the operating system “Linux kernel” to a newer version for security reasons. We apologize for the inconvenience this causes.
Update: the maintenance was completed with less than three minutes “downtime” per server.
If you have a Ruby on Rails application that originally used Rails 1.1.6 or earlier, you might have trouble after yesterday’s Rails update (which also updated several other Ruby “gems”, including the “RubyGems” gem itself).
The network interface on the “farnsworth” Web server stopped responding at 6:38 AM Pacific time today, and the server needed to be manually restarted by our data center staff. The server was unavailable for 17 minutes, causing an interruption of service for Web sites on that server. It also prevented users of that server from reading incoming e-mail (such e-mail was delayed and delivered after the outage).
Other servers were not affected.
We sincerely apologize to anyone affected by this problem.
We’ve updated the default version of Ruby on Rails on our servers to version 2.1.1.
