[23rd March 2009] DB1 - Emergency Maintenance

[Karl]

Hi,

Due to the issues with the HSphere DB1 one server over the past 24 hours, we will be carrying out emergency maintenance tonight from 10pm. This means that if you have a database (MySQL or PostgreSQL) that is on the DB1 server, it will unfortunately experience some downtime whilst we move it to a new server - you won't need to change anything inside of your scripts/web site, as the name/IP address will be staying the same.

Please accept our apologies for the problems and the short notice of the works.

Thank you,

[Jasidog]

Is there any reason my site's forum software should be offline with database access issues right now? Has been since the middle of last night I believe.

Whilst the rest of my site (including a test forum.) which also relies on mysql is fine.

[Karl]

Hi,

Best thing to do, is to open a ticket with the database name, as it sounds like it may need repairing.

Thanks,

[Jasidog]

Thanks Karl!

Already sent a ticket but I'll go add that info.

Cheers!

[BenANFA]

Hi Karl,

Erm I am not sure if this is a result of the server change or if we where just slow to notice but yesterday I noticed that using the UNIX_TIMESTAMP function in a MySQL SELECT statement was having a slightly odd effect. For dates after the 1st April 2009 (or those in summer time) 1 hour is subtracted from the time retrieved. For example issuing this command on our (account for www.rondotheatre.co.uk) database

SELECT EventTime, UNIX_TIMESTAMP( EventTime )
FROM Date WHERE ID =1071 OR ID =1065;

Returns the result

EventTime UNIX_TIMESTAMP(EventTime)
2009-03-21 20:00:00 1237665600
2009-04-09 20:00:00 1239303600

where the EventTime field has type datetime.

The UNIX timestamp for 2009-03-21 20:00:00 is 1237665600 but the unix timestamp for 2009-04-09 20:00:00 is 1239307200, 3600 or 1 hour more that the SQL result.

I am sure this is not what the behaviour of the MySQL server has been up to now and wondered if some strange daylight saving time effect has been introduced?

Have you got any thoughts on this?

Cheers Ben

[Karl]

Hi,

Can you try it now for me?

Thanks,

[BenANFA]

That appears to have fixed it

SELECT EventTime, UNIX_TIMESTAMP( EventTime )
FROM Date WHERE ID =1071 OR ID =1065;

EventTime UNIX_TIMESTAMP( EventTime )
2009-03-21 20:00:00 1237665600
2009-04-09 20:00:00 1239307200

Thanks for the quick response, what was the problem?

[BenANFA]

This issue or a similar one has returned since the server change, if I run

SELECT ID, EventTime, UNIX_TIMESTAMP( EventTime )
FROM Date
WHERE ID =1370
OR ID =1330;

I get the results

ID EventTime UNIX_TIMESTAMP( EventTime )
1330 2010-03-18 20:00:00 1268942400
1370 2010-05-13 19:30:00 1273779000

The highlighted value should actually be 1273775400 it is 3600 or 1 hour too far in the future.

[Karl]

Hi,

I'm not sure why you'd be getting that from MySQL as nothing has changed with that. The only potential change is that Web2 may have been set at UTC/GMT all the time, and Web4 is set to track GMT/BST changes - but that shouldn't affect MySQL at all.

If you could open up a ticket that'd be great as I don't really want to be discussing details of how your site works in public

Thanks,

[BenANFA]

Karl,

I have had tickets open and sent various emails and been trying to get you to provide support on this issue since your post (i.e. for 4 months) and you have been steadfastly ignoring everything I send/post.

The ticket numbers are

MWU-605040
XLE-874548

Please look at them.