date() misinterpreting timestamp?

ByteTraveler

A large application that operates correctly on our development server has been doing screwy things with timestamps when published to our live server.

To eliminate all other possibilities, I wrote a one line test script:

[INDENT]echo (date('g:i:s a', '1124845200'));[/INDENT]

(BTW - The timestamp should be August 23, 2005 @ 6:00pm)

On our development server, and several desktops we've tried, the line of code properly executes, and displays:

[INDENT]6:00:00 pm[/INDENT]

However, on the live server, the output is:

[INDENT]5:59:38 pm[/INDENT]

It's correct here under several versions of PHP 4.3.x & on V5.x.

The live (troublesome) server is PHP 4.3.11

Thanks in advance for any suggestions!!

phphp

???
in my country[China]
it displays 9:00:00 am
start time is different?

Weedpacket

Works for me: "1:00:00 pm"

Is it always 22 seconds out? Not that I know what that would mean if it was...

ByteTraveler

As a matter of fact, it's been narrowed-down, and yes - It's EXACTLY 22 seconds off, which screws-up the display off all our data.

The "Leap Second Thing," No?

Now here's the problem (besides having tons of correct data).... We can't really adjust in in the code (adding 22 seconds, for example) since the code runs on several boxes, and all but this one don't do the 22 second thing.

The hosting company thinks I'm nuts, and doesn't seem to even know what I'm talking about when I asked them to shut - off the leap-second adjustment because their box is adding 22 seconds to all timestamps it creates, and subtracting 22 seconds from all of the timestamps it displays.

The real bummer is that this is driven by a shared database in which all the machines don't add the 22 seconds, save for this one (web host) that does!?

Weedpacket

Um, come back next year and see if it's off by 23 seconds (there's to be a leap second inserted at the end of this year - making the total offset from TAI 33 seconds). Sounds like a red herring.

It does sound like something's out of whack with the server (especially since it's just that one). What does it return for a timestamp of 0? Get the time down to the second and see what that says. But there is no justification for it to act like it's in a weird timezone that's 22 seconds offset from its next-door neighbour. I can't even see how having a mis-set clock could do it - that wouldn't change its timezone configuration.