374768 - Incorrect timestamps when creating bugs or adding additional comments

Status: RESOLVED WORKSFORME

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Martijn Ras]

Heya Folks,

One of my users noticed that the timestamps in my bugzilla installation are incorrect when creating bugs or adding additional comments.

The server's clock is set correctly (actually it's using ntp), so that's not causing the problem, the timestamp generated at the top of the results returned by buglist.cgi is correct.

When creating bugs or adding additional comments the timestamp is offset by 5 hours. For example, in this comment that i added as a test:

------- Comment  #1 From Martijn Ras  2007-03-21 10:20:45  [reply] -------
Additional comment on: 2007-03-21 15:20

Mazzel,

Martijn.

Comment 1

[Dave Miller [:justdave]]

your timezone is probably set incorrectly in the params.  I think that's on the required settings panel.  If that's not the case go ahead and reopen this.

Comment 2

[Martijn Ras]

I've never set the timezone in the params. I reset the timezone parameter to the factory setting (which is empty, c.q. not set) and added a comment for which the timestamp is still offset by 5 hours. Then i set the timezone parameter to CET and added a comment. The only change was that now all timestamps where ended by the name of the timezone.

Comment 3

[Olav Vitters]

Look at your database server.

Comment 4

[Max Kanat-Alexander]

Yeah, it's probably something with your database. See if the timestamps are correct in the database.

Bugzilla doesn't modify timestamps at *all* on the way into the database, it just uses the NOW() function in your DB. So if that's somehow wrong, then something could be up.

Comment 5

[Martijn Ras]

Haven't been able to locate what exaclty made the time offset by 5 hours in Bugzilla, while all other MySQL databases set their timestamps correctly.

Eventually i gave up and restarted both my webserver and MySQL, the problem seems to have disappeared for now ...

Comment 6

[Frédéric Buclin]

This bug is not fixed but wfm.