Hi,
I'm in the process of upgrading a 2.3.41 directory up to the 2.4 branch. I've got a few virtual machines with which I've been testing and running syncrepl.
I've successfully 'pulled' all the data out from the old server (2.3) and that's now in database 1 on my new server.
However, having installed openLDAP on another new server.. the date that logs are reporting is an hour earlier than the system time.
Is there a configurable run-time option in slapd, to get the date? I've currently not got monitoring setup.
Regards,
Andy
andylockran wrote:
Hi,
I'm in the process of upgrading a 2.3.41 directory up to the 2.4 branch. I've got a few virtual machines with which I've been testing and running syncrepl.
I've successfully 'pulled' all the data out from the old server (2.3) and that's now in database 1 on my new server.
However, having installed openLDAP on another new server.. the date that logs are reporting is an hour earlier than the system time.
Is there a configurable run-time option in slapd, to get the date? I've currently not got monitoring setup.
No, there's nothing in slapd that messes with the system clock. Probably you have an incorrect TZ or other environment variable when slapd starts.
Howard Chu wrote:
andylockran wrote:
Hi,
I'm in the process of upgrading a 2.3.41 directory up to the 2.4 branch. I've got a few virtual machines with which I've been testing and running syncrepl.
I've successfully 'pulled' all the data out from the old server (2.3) and that's now in database 1 on my new server.
However, having installed openLDAP on another new server.. the date that logs are reporting is an hour earlier than the system time.
Is there a configurable run-time option in slapd, to get the date? I've currently not got monitoring setup.
No, there's nothing in slapd that messes with the system clock. Probably you have an incorrect TZ or other environment variable when slapd starts.
TZ="Europe/London"; export TZ
that's in /etc/profile, and the date shows up correctly as:
Fri Aug 29 11:09:34 BST 2008
Does openldap pull its timezone data from elsewhere.
Regards,
Andy
andylockran wrote:
Howard Chu wrote:
andylockran wrote:
Hi,
I'm in the process of upgrading a 2.3.41 directory up to the 2.4 branch. I've got a few virtual machines with which I've been testing and running syncrepl.
I've successfully 'pulled' all the data out from the old server (2.3) and that's now in database 1 on my new server.
However, having installed openLDAP on another new server.. the date that logs are reporting is an hour earlier than the system time.
Is there a configurable run-time option in slapd, to get the date? I've currently not got monitoring setup.
No, there's nothing in slapd that messes with the system clock. Probably you have an incorrect TZ or other environment variable when slapd starts.
TZ="Europe/London"; export TZ
that's in /etc/profile, and the date shows up correctly as:
Fri Aug 29 11:09:34 BST 2008
Does openldap pull its timezone data from elsewhere.
What does syslog honour?
On Fri, 29 Aug 2008, andylockran wrote: ...
TZ="Europe/London"; export TZ
that's in /etc/profile, and the date shows up correctly as:
Fri Aug 29 11:09:34 BST 2008
On the systems that I'm familiar with, /etc/profile is only read by interactive shells and not by shells that are running scripts. If that's the case on your system, then the slapd started from a boot-time script would not see that setting, because there's no interactive shell in its process ancestry.
For Solaris, the TZ variable is set for 'init' via the /etc/TIMEZONE file and processes inherit it from init.
For Linux, you normally leave TZ unset and instead make /etc/localtime a symlink to the correct file under /usr/share/zoneinfo/. If you run something chrooted then you may need to set up an /etc/localtime file inside the chroot if you care about the timezone it uses.
Does openldap pull its timezone data from elsewhere.
Nope.
Philip Guenther
openldap-software@openldap.org
-
andylockran -
Gavin Henry -
Howard Chu -
Philip Guenther