Discuss April 2010

discuss@lists.centos.org

265 participants
237 discussions

Start a nNew thread

[Fwd: Re: iptables]
by Niki Kovacs 19 May '10

19 May '10

7 10

Apparent BIND problem doing RBL lookups for Postfix
by listserv.traffic＠sloop.net 17 May '10

17 May '10

My apologies if I'm posting the wrong place, or am asking a common question. All my looking so far hasn't turned up anything very useful in knowing what to look at, or what to modify. --- CentOS 5, running BIND 9.3.6 i386 Hardware: P4, 2.8Ghz, 1G memory Sata drives - non mirrored etc. Load is light, usually under 0.1 -- This box is running Postfix as our mail server. BIND (9.3.6) [Latest.] -- Problem: Postfix is doing RBL lookups on zen.spamhaus.org. Everything goes along groovy - but then lookups start failing. Early in the process, we get stuff like this: [We have a "successful" lookup, and then a failure...] --- Apr 14 14:25:05 mail postfix/smtpd[22281]: NOQUEUE: reject: RCPT from bzq-79-183-5-119.red.bezeqint.net[79.183.5.119]: 554 5.7.1 Service unavailable; Client host [79.183.5.119] blocked using zen.spamhaus.org; from=<contriveclaudia(a)royalmoore.com> to=<contriveclaudia(a)royalmoore.com> proto=SMTP helo=<bzq-79-183-5-119.red.bezeqint.net> Apr 14 14:25:07 mail postfix/smtpd[22804]: warning: 33.229.242.205.zen.spamhaus.org: RBL lookup error: Host or domain name not found. Name service error for name=33.229.242.205.zen.spamhaus.org type=A: Host not found, try again --- As you can see, we had a lookup succeed and then just right after, one fail - claiming it got no answer from BIND. I get others after this that SUCCEED - so it's not in 100% failure mode yet. After time [how much, I don't know] eventually all the zen queries [or most all] fail. A bind restart fixes the problem. [Hmmm...] --- I do some logging in bind, and I don't see any reason for them to fail. Here's a bind debug log of 5 on that failure above. --- 14-Apr-2010 14:24:57.654 queries: info: client 127.0.0.1#42018: query: 33.229.242.205.zen.spamhaus.org IN A + 14-Apr-2010 14:24:57.654 security: debug 3: client 127.0.0.1#42018: query (cache) '33.229.242.205.zen.spamhaus.org/A/IN' approved 14-Apr-2010 14:24:57.654 resolver: debug 1: createfetch: 33.229.242.205.zen.spamhaus.org A 14-Apr-2010 14:24:57.654 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): create 14-Apr-2010 14:24:57.654 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): join 14-Apr-2010 14:24:57.654 resolver: debug 3: fetch 0x94a0b20 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): created 14-Apr-2010 14:24:57.655 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): start 14-Apr-2010 14:24:57.655 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:24:57.655 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelqueries 14-Apr-2010 14:24:57.655 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): getaddresses 14-Apr-2010 14:24:57.655 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:24:57.655 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:24:57.655 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:24:57.655 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:24:57.655 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:24:59.657 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:24:59.657 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:24:59.657 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:24:59.657 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:24:59.657 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:24:59.657 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:24:59.657 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:24:59.657 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:01.658 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:01.658 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:01.658 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:01.658 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:01.658 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:01.659 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:01.659 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:01.659 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:02.653 queries: info: client 127.0.0.1#42018: query: 33.229.242.205.zen.spamhaus.org IN A + 14-Apr-2010 14:25:02.653 security: debug 3: client 127.0.0.1#42018: query (cache) '33.229.242.205.zen.spamhaus.org/A/IN' approved 14-Apr-2010 14:25:02.654 resolver: debug 1: createfetch: 33.229.242.205.zen.spamhaus.org A 14-Apr-2010 14:25:02.654 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): join 14-Apr-2010 14:25:02.654 resolver: debug 3: fetch 0x94d54c8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): created 14-Apr-2010 14:25:03.660 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:03.660 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:03.660 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:03.660 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:03.660 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:03.660 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:03.660 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:03.660 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:03.660 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:05.663 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:05.663 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:05.663 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:05.663 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:05.663 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:05.663 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:05.663 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:05.663 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:05.663 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:07.664 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:07.664 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:07.664 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:07.664 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:07.664 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:07.664 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:07.665 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:07.665 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:07.665 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:08.393 queries: info: client 127.0.0.1#50896: query: 33.229.242.205.zen.spamhaus.org IN A + 14-Apr-2010 14:25:08.393 security: debug 3: client 127.0.0.1#50896: query (cache) '33.229.242.205.zen.spamhaus.org/A/IN' approved 14-Apr-2010 14:25:08.393 resolver: debug 1: createfetch: 33.229.242.205.zen.spamhaus.org A 14-Apr-2010 14:25:08.393 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): join 14-Apr-2010 14:25:08.393 resolver: debug 3: fetch 0x94ad9c8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): created 14-Apr-2010 14:25:09.666 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:09.666 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:09.666 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:09.666 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:09.666 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:09.666 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:09.666 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:09.666 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:09.666 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:11.668 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:11.668 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:11.668 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:11.668 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:11.668 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:11.668 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:11.668 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:11.668 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:11.668 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:13.669 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:13.669 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:13.669 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:13.669 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:13.669 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:13.669 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:13.670 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:13.670 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:13.670 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:15.671 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:15.671 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:15.671 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:15.671 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:15.671 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:15.671 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:15.671 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:15.671 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:15.671 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:17.673 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:17.673 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:17.673 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:17.673 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:17.673 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:17.673 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:17.673 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:17.673 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:17.673 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:19.674 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:19.674 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:19.674 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:19.674 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:19.674 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:19.674 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:19.675 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:19.675 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:19.675 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:21.676 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:21.676 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:21.676 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:21.676 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:21.676 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:21.676 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:21.676 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:21.676 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:21.676 resolver: debug 3: resquery 0x940ec38 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:23.677 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): timeout 14-Apr-2010 14:25:23.678 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:23.678 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): try 14-Apr-2010 14:25:23.678 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): query 14-Apr-2010 14:25:23.678 resolver: debug 3: resquery 0x94ae7b8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): send 14-Apr-2010 14:25:23.678 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): too many timeouts, disabling EDNS0 14-Apr-2010 14:25:23.678 resolver: debug 3: resquery 0x94ae7b8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): sent 14-Apr-2010 14:25:23.678 resolver: debug 3: resquery 0x94ae7b8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): udpconnected 14-Apr-2010 14:25:23.678 resolver: debug 3: resquery 0x94ae7b8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): senddone 14-Apr-2010 14:25:23.912 resolver: debug 3: resquery 0x94ae7b8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): response 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): noanswer_response 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): ncache_message 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): clone_results 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelquery 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): done 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): stopeverything 14-Apr-2010 14:25:23.912 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelqueries 14-Apr-2010 14:25:23.913 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): sendevents 14-Apr-2010 14:25:23.913 resolver: debug 3: fetch 0x94a0b20 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): destroyfetch 14-Apr-2010 14:25:23.913 resolver: debug 3: fetch 0x94d54c8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): destroyfetch 14-Apr-2010 14:25:23.913 resolver: debug 3: fetch 0x94ad9c8 (fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A)): destroyfetch 14-Apr-2010 14:25:23.914 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): shutdown 14-Apr-2010 14:25:23.914 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): doshutdown 14-Apr-2010 14:25:23.914 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): stopeverything 14-Apr-2010 14:25:23.914 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): cancelqueries 14-Apr-2010 14:25:23.914 resolver: debug 3: fctx 0x932e140(33.229.242.205.zen.spamhaus.org/A'): destroy --- As far as I can see, the BIND query simply didn't get a response - but no errors? --- First, someone's going to ask - perhaps Zen's blocking you. I don't think so. Here's why. -We're non-commercial, using the definition set my spamhaus, -mail connects TOTAL are well less than 100K a day. (Less than 10K in actuality) -and thus having more than 300K queries is pretty unlikely. -Also, let me remind you that a restart of the bind service seems to make the failures go away for a while, so if zen were blocking our queries, I'd think that wouldn't make a difference. --- I certainly suspect a problem with BIND, but I can't find it, and have no idea where to go from here. I simply don't know where to look any more. If BIND were having a problem, say allocating memory, or something, shouldn't it be in a debug level 5 log? HELP! -Greg [Cross posted from elsewhere, but I'm at a dead-end right now, so looking for a steer in where to ask, or direct help! TIA]

11 20

RHEL 6 Beta available for public download
by Timo Schoeler 17 May '10

17 May '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://press.redhat.com/2010/04/21/red-hat-enterprise-linux-6-beta-availabl… ...says it all. Have phun! Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFLzuMEfg746kcGBOwRAgjYAJ9QkJvm40sOVAOcUk4edQ98bM5CKgCgomte W8RuS+4FvyB/54jUnP+bT+A= =m6zn -----END PGP SIGNATURE-----

16 22

Simplifying making a USB install key
by m.roth＠5-cent.us 13 May '10

13 May '10

Ok, where/how do I submit this to the CentOS project? Here's a complete script - anyone, *please* feel free to test it, and let me know if I've missed anything. Thanks in advance. mark #!/bin/bash # ################################### # Author: mark roth # Date: 30 Apr. 2010 # Purpose: to create a working, bootable CentOS install on a USB key ##################################### if [[ $# < 2 ]]; then echo "usage: $0 <devname> <path/to/install.iso>" echo " Example: $0 sdb /scratch/CentOS-5.4-bin-DVD.iso" echo " Note: you must install livecd-tools before running this." exit fi /sbin/sfdisk -n -uM /dev/$1 << EOF ,10,b,* ,,83 ; ; EOF mkfs -t vfat /dev/${1}1 mkfs /dev/${1}2 /usr/bin/livecd-iso-to-disk /scratch/CentOS-5.4-i386-LiveCD.iso /dev/${1}1 mount /dev/${1}2 /mnt cp $2 /mnt/ # end

5 7

ibmasm service
by Janez Kosmrlj 10 May '10

10 May '10

Does someone have any info on this service. It's supposed to configure and have the tools to communicate with the ibm RSA. I am looking for a procedure to configure the RSA without using the bios and when possible set a access password. Is this the right tool to do this or am i misunderstanding something. Regards Janez

2 4

Aide error "Caught SIGBUS/SEGV"
by Bowie Bailey 07 May '10

07 May '10

One of my servers has recently started giving an error every time I run "aide --check". I ran it manually twice today with the same results. The second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few months. This is the error I am seeing: Caught SIGBUS/SEGV while mmapping. File was truncated while aide was running? Caught SIGBUS/SEGV. Exiting I tried Googling for it, but didn't find anything helpful. Any ideas? -- Bowie

2 2

vim and backup files
by Joseph L. Casale 05 May '10

05 May '10

None of my CentOS servers that are up to date recognize :set backup? A strace shows no mention of it, the backup never gets created, what am I missing here, anyone know if something changed that affects the backup behavior? Thanks! jlc

5 11

nfs4 help needed
by Anne Wilson 04 May '10

04 May '10

Fedora 13 is using nfs4, and there is a problem in opening files requiring OpenOffice if accessed over an nfs3 mount, so it's time to change. I found a couple of tutorials, and got it *almost* working correctly. This is where I need help. Logwatch tells me /nfs4exports/Data1 and /Data1 have same filehandle for *,192.168.0.0/24,192.168.0.0/255.255.255.0, using first The tutorial I was following suggested making a root connection as ro, then the data connections as rw, so I have /nfs4exports 192.168.0.0/24 (ro,sync,insecure,root_squash,no_subtree_check,fsid=0) /nfs4exports/Data1 192.168.0.0/24(rw,insecure,no_subtree_check,nohide) /nfs4exports/home 192.168.0.0/24(rw,insecure,no_subtree_check,nohide) However, when I ls nfs4exports I get Data1 home which ties in, I think, with the logwatch report. Can someone please explain what I've misunderstood, and what I should do to put it right? Thanks Anne

2 3

Re: [CentOS] how to find out promiscuous mode
by Les Bell 03 May '10

03 May '10

Vadkan Jozsef <jozsi.avadkan(a)gmail.com> wrote: >> How can I find out that someone is using it's network card in promiscuous mode in a subnet? << http://sourceforge.net/projects/prodetect/ Best, --- Les Bell [http://www.lesbell.com.au] Tel: +61 2 9451 1144

2 1

DNSSEC
by m.roth＠5-cent.us 03 May '10

03 May '10

Well, folks, There's an article on slashdot, <http://tech.slashdot.org/article.pl?sid=10/04/30/1258234> Excerpt: ...the coming milestone of May 5, at 17:00 UTC at this time DNSSEC will be rolled out across all 13 root servers. Some Internet users, especially those inside corporations and behind smaller ISPs, may experience intermittent problems. The reason is that some older networking equipment is pre-configured to block any reply to a DNS request that exceeds 512 bytes in size. DNSSEC replies are typically four times as large. --- end excerpt --- I followed the link from the story to <https://www.dns-oarc.net/oarc/services/replysizetest>, a coordinating organization, and tried their test (as root): dig +short rs.dns-oarc.net txt And see that where I work, we're not ready. Is anyone following this, and/or have a HOWTO on enabling it for CentOS? mark (need to check this at home, too)

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss April 2010