Date: Wed, 26 May 2004 22:29:48 -0700 From: Gary Kline <kline@thought.org> To: Eric Crist <ecrist@secure-computing.net> Cc: 'FreeBSD Mailing List' <freebsd-questions@freebsd.org> Subject: Re: DHCP is down.. Message-ID: <20040527052948.GA38459@tao.thought.org> In-Reply-To: <001e01c4438a$dbc14200$6601a8c0@Nomad> References: <20040527010836.GA977@tao.thought.org> <001e01c4438a$dbc14200$6601a8c0@Nomad>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 26, 2004 at 08:35:13PM -0500, Eric Crist wrote: > > -----Original Message----- > > From: owner-freebsd-questions@freebsd.org > > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Gary Kline > > Sent: Wednesday, May 26, 2004 8:09 PM > > To: Gary Kline > > Cc: FreeBSD Mailing List > > Subject: Re: DHCP is down.. > > > > > > On Wed, May 26, 2004 at 01:51:46PM -0700, Gary Kline wrote: > > > > > > well, severe troubles on my primary server.. dhcp > > > won't start. it looks like troble with bpf... > > > at least when i try to start dhcp by hand, it complains > > > that it can't find a bfp and quit. > > > > > > can anybody help me here? --i am currently rebuilding > > > my kernel with more bfp's in my KERNCONF file-- > > > > > > > People, > > > > Well, sorry if it is bad-form to reply to my eaelier post. > > MAKEDEV'ing bfp16 may have beenn part of it. I have a > > more important question; does anybody have any insights > > into *why* when I typed > > > > # sh /usr/local/etc/rc.d/isc-dhcpd.sh status|stop|start > > > > did I get a truckload of errors from named[`pid`]??!! > > Nothing I did got the daemon working... . > > > > I am uusing bind-9 which is installed in /usr/local/sbin/. > > The default bind stuff is in /usr/sbin. Was part of the > > isc-dhcp* stuff called the contrib named? > > > > I blew away 5+ hours with my network down.... I sure hope > > someone can de-idiotize me. > > > > gary > > Gary, > > Please tell me you didn't type the following, verbatim: > > # sh /usr/local/etc/rc.d/isc-dhcpd.sh status|stop|start > No, I typed the args separately, of course. After I added the packet filter pseudo-devices the dhcpd binary began to behave. Here is the last /var/log/console.log before I decided to take a break. Do you know where these errors are coming from? May 26 17:58:41 sage /kernel: May 26 17:58:41 sage su: kline to root on /dev/ttyp0 May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: creating IPv4 interface dc0 failed; interface ignored May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: creating IPv4 interface dc1 failed; interface ignored May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: creating IPv4 interface faith0 failed; interface ignored May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: creating IPv4 interface lo0 failed; interface ignored May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: could not get query source dispatcher (0.0.0.0#53) May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: loading configuration: address in use May 26 17:59:29 sage /kernel: May 26 17:59:29 sage named[2542]: exiting (due to fatal error) Here is from /var/log/messages: May 26 17:58:41 sage su: kline to root on /dev/ttyp0 May 26 17:59:29 sage named[2542]: starting BIND 9.2.3 -c /etc/namedb/named.conf May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage named[2542]: creating IPv4 interface dc0 failed; interface ignored May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage named[2542]: creating IPv4 interface dc1 failed; interface ignored May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage named[2542]: creating IPv4 interface faith0 failed; interface ignored May 26 17:59:29 sage named[2542]: could not listen on UDP socket: address in use May 26 17:59:29 sage named[2542]: creating IPv4 interface lo0 failed; interface ignored May 26 17:59:29 sage named[2542]: not listening on any interfaces May 26 17:59:29 sage named[2542]: zone 'thought.org' allows updates by IP address, which is insecure May 26 17:59:29 sage named[2542]: could not get query source dispatcher (0.0.0.0#53) May 26 17:59:29 sage named[2542]: loading configuration: address in use May 26 17:59:29 sage named[2542]: exiting (due to fatal error) May 26 18:16:03 sage ftpd[2618]: ANONYMOUS FTP LOGIN REFUSED FROM modemcable143.63-131-66.mc.videotron.ca May 26 18:16:12 sage ftpd[2617]: ANONYMOUS FTP LOGIN REFUSED FROM modemcable143.63-131-66.mc.videotron.ca May 26 20:05:35 sage ntpd[1705]: time reset 0.584034 s May 26 20:05:35 sage ntpd[1705]: kernel time discipline status change 6041 May 26 20:08:57 sage ntpd[1705]: kernel time discipline status change 2041 May 26 22:03:24 sage su: kline to root on /dev/ttyp0 May 26 22:13:25 sage named[3007]: starting BIND 9.2.3 -c /etc/namedb/named.conf May 26 22:13:25 sage named[3007]: command channel listening on 127.0.0.1#953 (Plese excuse the line wraps.) This has worked without any problems for many months; all of a sudden, <<something>> blew up. Is there a way of tracing where the "sage named[`pid`] output comes from--or what causes it? I've moved /usr/scin/named. gary > If this _is_ indeed the case, you need to try: > > #sh /usr/local/etc/rc.d/isc-dhcpd.sh start > > If that completes without errors, try: > > #sh /usr/local/etc/rc.d/isc-dhcpd.sh status > > Once you do this, please respond to the list so we know how it turned > out. > > HTH > > Eric F Crist > > -- Gary Kline kline@thought.org www.thought.org Public service Unix
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040527052948.GA38459>