ssi-addnode doesn't work if dhcp server logs to wrong place
Brought to you by:
brucewalker,
rogertsang
Menu
▾
▴
#195 ssi-addnode doesn't work if dhcp server logs to wrong place
Debian lenny 5.0.4 "DISC 1" (not netinst) and OpenSSI 1.9.6 preview for x86.
I tried a few other systems, making sure everyone has link lights, before plugging one ethernet port into the other and running dhclient eth1 while tail -f'ing /var/log/daemon.log. Nothing. Especially nothing matching 'DHCPDISCOVER'. Running dhcpd3 -d, DHCPDISCOVER's do go to stdout or stderr, so it's probably a log level problem. rsyslog.conf looks like it's configured to send daemon.* to /var/log/daemon.log (but with these wonky hacked up flavor of the week quasi-drop in replacements, it's impossible to tell what's going on). Aha! /etc/dhcpd3/dhcpd.info has a line specifying "log-facility: local7". Changing that to "daemon" and re-running mkdhcpd.conf gets ssi-addnode rolling again. By the way, my email is scott@slowass.net. Last go, I expected this bug tracker to ask me more info in a next screen but instead it accepted a half-arsed bug report with no contact info or version info and wouldn't let me edit it. Sorry about that.
I don't understand. What exactly is your complaint?
What are you trying to do? If you are installing the OpenSSI preview on Debian Lenny how far have you got?
(from submitter - wrong logging location was specified in dhcpd.proto).
ssi-addnode assumes that dhcp server is logging into /var/log/daemon.log (Debian) or /var/log/messages (redhat), no checking is done.
Question - who put the wrong logging facility into dhcpd.proto?
On OpenSSI install we move current dhcpd.conf to dhcpd.proto, so if existing dhcpd.conf has "wrong" logging parameters we're in trouble.
dhcp3-server package (since at least version 3.1.1-6+lenny4) ships with a config that sets log-facility to local7.
Maybe we should check log-facility on install, or not use existing dhcpd.conf as dhcpd.proto.
Thought I'd just pipe in here in regards to this issue - We have had the same issue with the Debian install of OpenSSI. We solved it by simply specifying the correct log file thusly: ssi-addnode --varlogfile=/var/log/messages