Your message dated Sun, 31 Jan 2010 14:17:49 +0000
with message-id <[email protected]>
and subject line Re: Bug#315962: Timestamps in RT logs do not take timezone or
daylight savings into account
has caused the Debian Bug report #315962,
regarding Timestamps in RT logs do not take timezone or daylight savings into
account
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
315962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315962
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: request-tracker3.4
Version: 3.4.1-2
When RT generates timestamps in log messages, it does not take into
account the timezone or daylight savings time. This results in log
messages which differ from the "local" (actual) system time.
This appears in log-to-screen (Apache error log) and log-to-file log
messages. Syslog messages appear fine, as RT doesn't add date/time to
those (syslogd handles the timestamping).
In my example, the time difference is 2 hours (using timezone
"Europe/Stockholm" on the system, and having specified it in
RT_SiteConfig.pm for this RT instance):
Set($Timezone, 'Europe/Stockholm');
r...@coturnix:~# cat /etc/timezone
Europe/Stockholm
r...@coturnix:~# LC_ALL=C LANG=C date
Mon Jun 27 17:12:31 CEST 2005
I'm using Request Tracker together with FastCGI and Apache on a Debian
Sarge box.
Example Apache error log entry:
[Mon Jun 27 17:02:20 2005] [error] [client 130.238.131.190] FastCGI:
server "/usr/local/share/request-tracker3.4/support.student.uu.se/libexec/mason_handler_support.student.uu.se.fcgi" stderr: [Mon Jun 27 15:02:19 2005] [debug]: About to think about scrips for transaction #312 (/usr/share/request-tracker3.4/lib/RT/Transaction_Overlay.pm:154), referer: https://support.student.uu.se/rt/Ticket/Display.html?id=8
Example RT logfile entry:
[Mon Jun 27 15:02:19 2005] [debug]: About to think about scrips for transaction
#312 (/usr/share/request-tracker3.4/lib/RT/Transaction_Overlay.pm:154)
Example /var/log/debug entry:
Jun 27 17:02:19 coturnix RT: About to think about scrips for transaction #312
Best regards,
Björn
--- End Message ---
--- Begin Message ---
On Mon, Jun 27, 2005 at 05:18:54PM +0200, Björn Wiberg wrote:
> When RT generates timestamps in log messages, it does not take into
> account the timezone or daylight savings time. This results in log
> messages which differ from the "local" (actual) system time.
>
> This appears in log-to-screen (Apache error log) and log-to-file log
> messages. Syslog messages appear fine, as RT doesn't add date/time to
> those (syslogd handles the timestamping).
>
> In my example, the time difference is 2 hours (using timezone
> "Europe/Stockholm" on the system, and having specified it in
> RT_SiteConfig.pm for this RT instance):
>
> Set($Timezone, 'Europe/Stockholm');
>
> r...@coturnix:~# cat /etc/timezone
> Europe/Stockholm
>
> r...@coturnix:~# LC_ALL=C LANG=C date
> Mon Jun 27 17:12:31 CEST 2005
>
> I'm using Request Tracker together with FastCGI and Apache on a Debian
> Sarge box.
>
> Example Apache error log entry:
>
> [Mon Jun 27 17:02:20 2005] [error] [client 130.238.131.190] FastCGI:
> server
Hi Björn,
This very old bug report never got a response, I see :(
The time stamps that you're seeing are generated by Apache, not
Request Tracker, so it was likely that it was the way you had Apache
configured.
I'm therefore closing this bug.
Dominic.
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
