Re: Bind 9.3.0 on FreeBSD 5.2.1
Try using rndc -s server ip status In Bind9 all controls have been turned over to the r/ndc system. On Thu, 23 Sep 2004 02:04:30 -0500, Kyle S. Allender [EMAIL PROTECTED] wrote: Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named is not running. bsd# ps x | grep named 11342 ?? SLs0:00.51 /usr/sbin/named -c /etc/namedb/named.conf 11596 p0 RL+0:00.00 grep named bsd# and bsd# ./named start [: /usr/sbin/named: unexpected operator Starting named. bsd# ps x | grep named 11603 ?? SLs0:00.05 /usr/sbin/named -c /etc/namedb/named.conf 11605 p0 RL+0:00.00 grep named bsd# I had originally set up this system with the Linux compatibility layer enabled which also resulted in complaints about ELF processing. These errors occur with bind 9.3.0rc4 (source install) and with 9.2.3 (ports install). I'm very confused and have stepped through /etc/defaults/rc.conf /etc/rc.d/named trying to trace the error to no avail. Any assistance would be greatly appreciated. This is not running in a chroot. Kyle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Bind 9.3.0 on FreeBSD 5.2.1
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named is not running. bsd# ps x | grep named 11342 ?? SLs0:00.51 /usr/sbin/named -c /etc/namedb/named.conf 11596 p0 RL+0:00.00 grep named bsd# and bsd# ./named start [: /usr/sbin/named: unexpected operator Starting named. bsd# ps x | grep named 11603 ?? SLs0:00.05 /usr/sbin/named -c /etc/namedb/named.conf 11605 p0 RL+0:00.00 grep named bsd# I had originally set up this system with the Linux compatibility layer enabled which also resulted in complaints about ELF processing. These errors occur with bind 9.3.0rc4 (source install) and with 9.2.3 (ports install). I'm very confused and have stepped through /etc/defaults/rc.conf /etc/rc.d/named trying to trace the error to no avail. Any assistance would be greatly appreciated. This is not running in a chroot. Kyle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Bind 9.3.0 on FreeBSD 5.2.1 startup problem
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named is not running. bsd# ps x | grep named 11342 ?? SLs0:00.51 /usr/sbin/named -c /etc/namedb/named.conf 11596 p0 RL+0:00.00 grep named bsd# and bsd# ./named start [: /usr/sbin/named: unexpected operator Starting named. bsd# ps x | grep named 11603 ?? SLs0:00.05 /usr/sbin/named -c /etc/namedb/named.conf 11605 p0 RL+0:00.00 grep named bsd# I had originally set up this system with the Linux compatibility layer enabled which also resulted in complaints about ELF processing. These errors occur with bind 9.3.0rc4 (source install) and with 9.2.3 (ports install). I'm very confused and have stepped through /etc/defaults/rc.conf /etc/rc.d/named trying to trace the error to no avail. Any assistance would be greatly appreciated. This is not running in a chroot. Kyle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Bind 9.3.0 on FreeBSD 5.2.1
[EMAIL PROTECTED] writes: This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? I think you are looking for something which doesn't exist. The only script involved with controlling named (that I know of) is /etc/rc. What I think you want in /usr/local/sbin/rndc. root@ /usr/local/sbin/rndc status number of zones: 8 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind 9.3.0 on FreeBSD 5.2.1
I installed Bind 9.3.0 on the machine using the information on this page: http://ezine.daemonnews.org/200303/bind9.html to completely replace the binary that is in the base OS install. It looks like there's a problem with the location of some of the installed pieces (support tools) of Bind 9.3.0. I haven't tried the final release version as yet, nor have I tried a pkg_delete on the base package. I suppose I can do that and see what happens, but would prefer to really understand the new rc command structure - it's different than the 4.x format that I'm used to. Do you have any other ideas? Manually using rndc returns the status (regardless of which rndc binary I call - original or copy), but it's still not picking up the status correctly. That doesn't work either: bsd# /usr/local/sbin/rndc status /usr/local/sbin/rndc: Command not found. bsd# which rndc /usr/sbin/rndc bsd# cp /usr/sbin/rndc /usr/local/sbin/rndc bsd# ls -ld /usr/local/sbin/rndc -r-xr-xr-x 1 root wheel 210024 Sep 23 09:57 /usr/local/sbin/rndc bsd# /usr/local/sbin/rndc status number of zones: 4 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running bsd# /etc/rc.d/named status named is not running. bsd# ps x | grep named 11603 ?? SLs0:00.65 /usr/sbin/named -c /etc/namedb/named.conf 12860 p0 RL+0:00.00 grep named bsd# If I kill named, the startup script, which if called thus: /etc/rc.d/named start should start named, doesn't start it. Instead I get this: bsd# killall named bsd# /etc/rc.d/named status named is not running. bsd# /etc/rc.d/named start [: /usr/sbin/named: unexpected operator Starting named. bsd# I can then manually issue: named which starts it running, but the status still doesn't get picked up. Is it possible that installing the Linux compatibility layer on initial install changed something? FYI, named didn't want to start up after the base install either - that was before I made any changes to the named binaries. Thx. [EMAIL PROTECTED] writes: This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? I think you are looking for something which doesn't exist. The only script involved with controlling named (that I know of) is /etc/rc. What I think you want in /usr/local/sbin/rndc. root@ /usr/local/sbin/rndc status number of zones: 8 debug level: 0 xfers running: 0 xfers deferred: 0 soa queries in progress: 0 query logging is OFF server is up and running Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Bind 9.3.0 on FreeBSD 5.2.1
Hello. This is potentially a stupid question, but is there a known issue with the rc script which controls named under FreeBSD 5.2.1? Running on an internal-only network where queries are received from machines I control on a home network, I get spurios errors such as: bsd# ./named status named is not running. bsd# ps x | grep named 11342 ?? SLs0:00.51 /usr/sbin/named -c /etc/namedb/named.conf 11596 p0 RL+0:00.00 grep named bsd# and bsd# ./named start [: /usr/sbin/named: unexpected operator Starting named. bsd# ps x | grep named 11603 ?? SLs0:00.05 /usr/sbin/named -c /etc/namedb/named.conf 11605 p0 RL+0:00.00 grep named bsd# I had originally set up this system with the Linux compatibility layer enabled which also resulted in complaints about ELF processing. These errors occur with bind 9.3.0rc4 (source install) and with 9.2.3 (ports install). I'm very confused and have stepped through /etc/defaults/rc.conf /etc/rc.d/named trying to trace the error to no avail. Any assistance would be greatly appreciated. This is not running in a chroot. Kyle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bind 9.3.0 on FreeBSD 5.2.1 followup
I performed a pkg_delete of bind9, then did a clean install of bind 9.3.0 (final release) from source on the 5.2.1 machine. On reboot, I get these messages on console: login: Sep 23 10:44:00 bsd named[506]: could not listen on UDP socket: permission denied Sep 23 10:44:00 bsd named[506]: creating IPv4 interface de0 failed; interface ignored followed by similar messages for the other interfaces. It appears that there are multiple issues here - including problems with named trying to start before the interfaces are created? After logging in, a manual start of named from the prompt fails - same errors as above. But a ps x | grep named returns two running instances of named... I'm getting more and more confused. Perhaps I should just re-install before this gets too weird? Kyle ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
