Re: ntpd problems since upgrading to 5.3 - found the problem!
On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. Cheers, -- Ian Moore GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpaXjoKVcfku.pgp Description: PGP signature
Re: ntpd problems since upgrading to 5.3 - found the problem!
Ian Moore [EMAIL PROTECTED] writes: On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. What about ntpq -pn? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote: Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] Thanks, I hadn't thought of using a non-existant top level domain. I've changed the hostname to daemon.foo.lan and now localhost.foo.lan resolves to 127.0.0.1 as it should. Unfortunately, I still get the same response form ntpq: daemon:~ % sudo ntpq -p ntpq: write to localhost.foo.lan failed: Permission denied Even with my firewall disabled I get this response. What about ntpq -pn? No, I get the same response from that too. Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpjGfhWMjOdi.pgp Description: PGP signature
Re: ntpd problems since upgrading to 5.3 - found the problem!
Ian Moore [EMAIL PROTECTED] writes: I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Make sure to switch to using domain names that aren't in use by other people... [A common convention is to use .lan or .local as the top-level domain if you are using non-public domain names.] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
On Tue, 18 Jan 2005 12:50, Christian Hiris wrote: On Tuesday 18 January 2005 01:09, John wrote: On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote: On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote: On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote: Ian Moore wrote: Hi, Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the following error on boot: ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1 ::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: :: Can't assign requested address ntpd seems to be working from what I can see in it's log file, but I can't do anything with ntpq to check it. Wether I run it as my normal user or as root, running ntpq -p always gives: ntpq: write to localhost.foo.com failed: Permission denied Try to add disable auth to your ntp.conf. I tried that, sadly it made no difference. However, I think I've found the problem - the error message I get with ntpq is write to localhost.foo.com failed: Permission denied. My machine's hostname is daemon.foo.com, something I assumed was safe to use. Well it turns out that localhost.foo.com actually exists, it resolves to 216.234.246.150, as do lots of others like localhost.foo.org, foobar.org, example.org etc. So ntpq must do a reverse name lookup for localhost.whatever the host's domain name is and in my case it doesn't reslove to 127.0.0.1 but to 216.234.246.150, to which ntpq has no access - hence the Permission denied error! Now I'm not sure what the best way to get around this would be. I run a caching name server on the machine, so I guess I can tweak it to force localhost.foo.com resolve to 127.0.0.1 Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpNlb5tuOeDC.pgp Description: PGP signature
Re: ntpd problems since upgrading to 5.3 - found the problem!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 18 January 2005 07:19, Ian Moore wrote: Now I'm not sure what the best way to get around this would be. I run a caching name server on the machine, so I guess I can tweak it to force localhost.foo.com resolve to 127.0.0.1 I'm running ntpd and a caching nameserver on one machine, too. The external IP is only referenced by /etc/hosts. My bind holds only the internal networks, including it's own localhost. There also could be some influence from your /etc/resolv.conf, but I'm not sure about. # dig localhost.matrix.net ; DiG 9.3.0 localhost.matrix.net ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 47348 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;localhost.matrix.net. IN A ;; ANSWER SECTION: localhost.matrix.net. 3600IN A 127.0.0.1 ;; AUTHORITY SECTION: matrix.net. 3600IN NS ns.matrix.net. ;; ADDITIONAL SECTION: ns.matrix.net. 3600IN A 192.168.123.1 ;; Query time: 1 msec ;; SERVER: 192.168.123.1#53(192.168.123.1) ;; WHEN: Tue Jan 18 07:27:54 2005 ;; MSG SIZE rcvd: 87 # cat /etc/resolv.conf search matrix.net nameserver 127.0.0.1 - -- Christian Hiris [EMAIL PROTECTED] | OpenPGP KeyID 0x3BCA53BE OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB7LAC09WjGjvKU74RAkZjAKCC6C+33mjGMf3tK36/36KV0yUrlgCdGpr8 6RVG2fKYma3/+tJbdPrx3YI= =pwmk -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntpd problems since upgrading to 5.3 - found the problem!
On Tue, 18 Jan 2005 17:13, Christian Hiris wrote: On Tuesday 18 January 2005 07:19, Ian Moore wrote: Now I'm not sure what the best way to get around this would be. I run a caching name server on the machine, so I guess I can tweak it to force localhost.foo.com resolve to 127.0.0.1 I'm running ntpd and a caching nameserver on one machine, too. The external IP is only referenced by /etc/hosts. My bind holds only the internal networks, including it's own localhost. There also could be some influence from your /etc/resolv.conf, but I'm not sure about. # dig localhost.matrix.net ; DiG 9.3.0 localhost.matrix.net ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 47348 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;localhost.matrix.net. IN A ;; ANSWER SECTION: localhost.matrix.net. 3600IN A 127.0.0.1 ;; AUTHORITY SECTION: matrix.net. 3600IN NS ns.matrix.net. ;; ADDITIONAL SECTION: ns.matrix.net. 3600IN A 192.168.123.1 ;; Query time: 1 msec ;; SERVER: 192.168.123.1#53(192.168.123.1) ;; WHEN: Tue Jan 18 07:27:54 2005 ;; MSG SIZE rcvd: 87 # cat /etc/resolv.conf search matrix.net nameserver 127.0.0.1 Oops, I've just realised I'm not running a name server at all on my 5.3 system. I have 4.9 installed on this computer too I'd set up the caching server on it, I guess I forgot that step when I installed 5.3. I'll set it up see that makes any difference. Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpSR9uAmIFYt.pgp Description: PGP signature
