Author Topic: Server Maintenance 12/31/09 (Read 297305 times)

dschwab9 · « **on:** December 30, 2009, 09:39:39 PM »

Just wanted to give everyone a heads up that I will
be at the datacenter tomorrow, 12/31/09 around 2PM EST to do a little server maintenance. The site will probably be down for 45 minutes or so.

Kill Em All · « **Reply #1 on:** December 30, 2009, 10:43:04 PM »

Good luck and have fun, let us know how it goes.

Arantor · « **Reply #2 on:** December 30, 2009, 11:10:02 PM »

We'll know it was successful when we can post again

A.SK · « **Reply #3 on:** December 31, 2009, 01:29:44 AM »

Good to know the updates @ SMF Data Center.

Do update the status as requested.

SleePy · « **Reply #4 on:** December 31, 2009, 04:58:38 AM »

Thanks for the heads up and good luck

vagrant · « **Reply #5 on:** December 31, 2009, 05:33:37 AM »

Hope the maintenance goes well at the Data Center, and would like to wish the server (and yourself) a trouble free new year

Costa · « **Reply #6 on:** December 31, 2009, 11:31:16 AM »

We'll know it was successful when we can post again

simmaster · « **Reply #7 on:** December 31, 2009, 01:49:37 PM »

We'll know it was successful when we can log in again.

We have around a good ten minutes until downtime. Brace for impact!

Mark Rose · « **Reply #8 on:** December 31, 2009, 02:21:19 PM »

That Y2K+10 problem is a pain, isn't it?

JBlaze · « **Reply #9 on:** December 31, 2009, 02:33:35 PM »

Quote from: Arantor on December 30, 2009, 11:10:02 PM

We'll know it was successful when I start spamming again

Arantor · « **Reply #10 on:** December 31, 2009, 09:37:11 PM »

Guessing this all went OK?

Mark Rose · « **Reply #11 on:** January 02, 2010, 12:56:38 AM »

Quote from: «Mark» on December 31, 2009, 02:21:19 PM

That Y2K+10 problem is a pain, isn't it?

HAHAH... turns out there is a Y2K+10 bug!

https://secure.grepular.com/blog/index.php/2010/01/01/spamassassin-2010-bug/

alexmaster · « **Reply #12 on:** January 02, 2010, 07:20:45 AM »

Have such problems at my SMF business forum - http://bfrf.ru/ sometimes, like database is corrupted or something is going wrong. I also get messages about it on my email.

P.S. Sometimes it looks like a server error.

Arantor · « **Reply #13 on:** January 02, 2010, 08:14:50 AM »

alexmaster: if you have a problem please open a support ticket; this thread is not a place for requesting any kind of help.

alexmaster · « **Reply #14 on:** January 02, 2010, 10:08:34 AM »

Ok, I'm solving this problem with my hosting provider now. Maybe it was connected to bugs with design (bye the way is it really not ordinary enough?))))

Daniel15 · « **Reply #15 on:** January 08, 2010, 07:34:28 PM »

Quote from: «Mark» on January 02, 2010, 12:56:38 AM

Quote from: «Mark» on December 31, 2009, 02:21:19 PM
That Y2K+10 problem is a pain, isn't it?

HAHAH... turns out there is a Y2K+10 bug!

https://secure.grepular.com/blog/index.php/2010/01/01/spamassassin-2010-bug/

There's actually quite a few... Some EFTPOS machines (machines for processing debit and credit cards at stores) were affected here, as well as some Windows Mobile devices, ATMs in Germany, and Symantec's corporate anti-virus. In the first three cases, the machine thought it was 2016 instead of 2010, and most credit cards were denied because "they had expired" (unless your card expires after 2016). In the last case, the anti-virus stopped getting updates on the 31st December 2009, and it sees all newer updates as "out of date"

http://www.theregister.co.uk/2010/01/04/bank_queensland/
http://www.theregister.co.uk/2010/01/05/symantec_y2k10_bug/
http://www.rte.ie/business/2010/0105/bug.html
http://www.theregister.co.uk/2010/01/05/windows_mobe_bug/

And of course, the bad SpamAssassin rule marking all emails received in 2010 as spam. Their fix? Change it from "2010" to "2020". The problem will come back in 10 years if that rule isn't rewritten by then

My question to them is, why use a regular expression to match years "in the future"? Why not do current year + 1 or something?

Arantor · « **Reply #16 on:** January 08, 2010, 07:40:18 PM »

Because it'll foul up every year coming up to midnight on Dec 31st when some users' timezones will legitmately place it beyond the current year.

Better solution - it needs to look simply at a few days, couple of weeks max, ahead - and if the date is that far ahead, it's likely spam.

青山素子 · « **Reply #17 on:** January 09, 2010, 12:48:07 AM »

Quote from: Arantor on January 08, 2010, 07:40:18 PM

Better solution - it needs to look simply at a few days, couple of weeks max, ahead - and if the date is that far ahead, it's likely spam.

The SA folks note that in the bug report and it's one of the parts under review for a rewrite. However, a simple fix was needed quickly and that rule change will hold until it can be revisited.

Ash-1993 · « **Reply #18 on:** January 09, 2010, 10:42:52 AM »

Goodluck mate. Hopefully it goes well

.

MazdaClubTR · « **Reply #19 on:** January 10, 2010, 06:13:35 AM »

Symantec finally seems to have solved the problem. Now I can get 2010 dated signatures

News:

Author Topic: Server Maintenance 12/31/09 (Read 297305 times)