Hello,
I'm running OpenLDAP 2.4.20 in a chroot()-ed environment on Solaris 10. I somehow don't get logging working. I don't see any logging making it's way through syslog. Nor do I get messages to an explicitly configured "logfile". "loglevel" is set to "stat".
As soon as I start slapd using "-d ..." I see the messages in the "logfile" configured.
Using "truss" I see unsuccessful tries to open "/var/run/syslog_door" until I
mount -F lofs /var/run /var/openldap/var/run
(with "/var/openldap" being my chroot-directory). Unluckily still no syslog logging. using "pfiles <PID>" I see slapd has got a file handle to "logfile" open. But there's not "write" to this handle in truss output either.
Anybody with any idea about if and how chroot-slapd and syslog (or logfile) works?
Thanks in advance.
Hello,
no one with any idea about what to look for?
On 01/13/11 9:03 pm, I wrote:
Hello,
I'm running OpenLDAP 2.4.20 in a chroot()-ed environment on Solaris 10. I somehow don't get logging working. I don't see any logging making it's way through syslog. Nor do I get messages to an explicitly configured "logfile". "loglevel" is set to "stat".
As soon as I start slapd using "-d ..." I see the messages in the "logfile" configured.
Using "truss" I see unsuccessful tries to open "/var/run/syslog_door" until I
mount -F lofs /var/run /var/openldap/var/run
(with "/var/openldap" being my chroot-directory). Unluckily still no syslog logging. using "pfiles <PID>" I see slapd has got a file handle to "logfile" open. But there's not "write" to this handle in truss output either.
Anybody with any idea about if and how chroot-slapd and syslog (or logfile) works?
Thanks in advance.
Am 26.01.2011 07:31, schrieb Peter Palmreuther:
Hello,
no one with any idea about what to look for?
On 01/13/11 9:03 pm, I wrote:
Hello,
I'm running OpenLDAP 2.4.20 in a chroot()-ed environment on Solaris 10. I somehow don't get logging working. I don't see any logging making it's way through syslog. Nor do I get messages to an explicitly configured "logfile". "loglevel" is set to "stat".
As soon as I start slapd using "-d ..." I see the messages in the "logfile" configured.
Using "truss" I see unsuccessful tries to open "/var/run/syslog_door" until I
mount -F lofs /var/run /var/openldap/var/run
(with "/var/openldap" being my chroot-directory). Unluckily still no syslog logging. using "pfiles <PID>" I see slapd has got a file handle to "logfile" open. But there's not "write" to this handle in truss output either.
Anybody with any idea about if and how chroot-slapd and syslog (or logfile) works?
Thanks in advance.
Hi,
if you are using Solaris, why don't you just put your LDAP server into a zone? Would be a more "clean" separation from the global zone and you have your own syslog deamon in that environment.
Regards, Christian Manal
Hello
On 01/26/11 08:54, Christian Manal wrote:
Am 26.01.2011 07:31, schrieb Peter Palmreuther:
no one with any idea about what to look for?
On 01/13/11 9:03 pm, I wrote:
I'm running OpenLDAP 2.4.20 in a chroot()-ed environment on Solaris 10. I somehow don't get logging working. I don't see any logging making it's way through syslog.
[...]
if you are using Solaris, why don't you just put your LDAP server into a zone? Would be a more "clean" separation from the global zone and you have your own syslog deamon in that environment.
I know. But for I don't have much influence on the Solaris configuration itself. We don't have zones available in our setup ... The operations section does not support zones yet. So I'm stuck with what I've got and luckily OpenLDAP supports chroot() itself ... Except I don't get the logging running the way I want.
Am Thu, 27 Jan 2011 00:37:26 +0100 schrieb Peter Palmreuther pitpalme+openldap@gmail.com:
Hello
On 01/26/11 08:54, Christian Manal wrote:
Am 26.01.2011 07:31, schrieb Peter Palmreuther:
no one with any idea about what to look for?
On 01/13/11 9:03 pm, I wrote:
I'm running OpenLDAP 2.4.20 in a chroot()-ed environment on Solaris 10. I somehow don't get logging working. I don't see any logging making it's way through syslog.
[...]
if you are using Solaris, why don't you just put your LDAP server into a zone? Would be a more "clean" separation from the global zone and you have your own syslog deamon in that environment.
I know. But for I don't have much influence on the Solaris configuration itself. We don't have zones available in our setup ... The operations section does not support zones yet. So I'm stuck with what I've got and luckily OpenLDAP supports chroot() itself ... Except I don't get the logging running the way I want.
slapd loggs to local4, configure syslog to listen to the chroot environment.
-Dieter
openldap-technical@openldap.org
-
Christian Manal -
Dieter Kluenter -
Peter Palmreuther