dhcp 4.3.2 with ldap backend

[Peter Rathlev]

On Mon, 2015-05-11 at 13:07 +0000, Kristof Van Doorsselaere wrote:
> The fact I’m always getting: configuration file errors encountered, make me think this is a new bug, isn’t it?

It sure does sound something like that. A few other possible ideas:

You mentioned that tcpdump on the LDAP server shows nothing. What about
a local tcpdump on the DHCP server, using the "any" interface?

Does the daemon start and release the PTY, just logging the errors to
syslog? Or does it not release the PTY and dump the syntax error to
STDERR? I would expect the latter for an actual configuration syntax
error. I'm not sure how systemd's systemctl starts a daemon and if you
would actually see the STDERR output.

You could also try starting the daemon in the foreground (-f) in an
"strace" session and look at what actually happens. Like if the daemon
actually creates a socket ("socket(PF_INET, SOCK_STREAM, IPPROTO_TCP)")
and what the "connect" returns.

I'm afraid we don't use the LDAP backend and I try to avoid Windows RHEL
2007 like the plague. Not a fan of systemd on servers. :-)

-- 
Peter