On Sun, Apr 4, 2010 at 3:44 AM, Balazs Scheidler <bazsi@balabit.hu> wrote:
On Thu, 2010-03-25 at 08:49 -0500, Patrick A. Green wrote:
Patrick A. Green wrote:
Balazs Scheidler wrote:
Are you sure syslog-ng's local timezone is properly set? Is syslog-ng running in a chroot? If it is, is the timezone in the chroot properly set?
We are in fact running chroot. Is there something more than /etc/localtime that needs to be put in the chroot environment?
I was able to recreate this in a lab environment.
RHEL3.9
These packages were required to make 3.0.4 run:
pkgconfig-0.18 eventlog-0.2.5 glib-2.18.4
Hi,
We've got an unrelated bug report which is similar to this one. I've ported that fix to the OSE right now, can you please test if this patch fixes the issue for you?
The time fixed itself Sunday, so it looks like syslog-ng somehow was using old timezone data. We'll give things a test in our test environment that we duplicated the problem in. chris