Discuss

discuss@lists.centos.org

34753 discussions

route question
by Jerry Geis 17 May '10

17 May '10

My current route for a box shows this: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 24.123.23.168 0.0.0.0 255.255.255.248 U 0 0 0 eth2 74.223.8.176 0.0.0.0 255.255.255.240 U 0 0 0 eth1 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2 0.0.0.0 24.123.23.169 0.0.0.0 UG 0 0 0 eth2 How do I setup the 74.223.8.176 route so on boot the gateway will automatically be set to 74.223.8.177 Thanks, Jerry

9 15

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

decent WMS on CentOS?
by dnk 17 May '10

17 May '10

Can anyone recommend a decent WMS (Warehouse Management System) that runs on CentOS decently? Thank you. DNK

2 1

upgrading to a minor release 4.1 to 4.2
by sheraz naz 17 May '10

17 May '10

Hi, I need to upgrade a system running 4.1 to 4.2, but before I do I want to list out all the packages that will be updated/installed/removed. I can run up2date -l to get a list of updates but does that show packages that need to be installed and removed as well or just the updates? Second, how would I go about upgrading 4.1 to 4.2 instead of 4.8 (i.e. latest update). Unfortunately I don't have access to centos 4.x at the moment.and googling just centos 4.1 to 4.2 is not bringing up relevant information. Thanks Sheraz

7 12

release of 5.5? (filesystem troubles)
by Rainer Fuegenstein 17 May '10

17 May '10

hi guys, is there an estimate when centos 5.5 will be released? I'm sitting on needles here, because since I moved my 4*1.5TB raid5 from an asus to an intel D510 mainboard I encounter bug the described here: https://bugzilla.redhat.com/show_bug.cgi?id=512552 short version: running xfs on top of a raid5 under heavy load causes corrupted data to be read and the filesystem shutting down occasionally. version 5.5 should solve this problem. if 5.5 is just a few days away I'll keep waiting, but if it takes much longer I'll need to work around this problem like going back to the old mainboard, compiling the kernel myself, switching to ext3 - none of which I'm eager to do. cu

9 12

Free and Robust Hotspot Management Software ?
by Roberto HT 17 May '10

17 May '10

Dear all, Could anybody give me some recommended open source software for wifi management? What I am looking for is a simple and basic tools, for example the software will have these kind of features : - user connect to the wifi network - user got IP from DHCP but he can't browse to anywhere at first. Instead he will redirected to a "login page" - administrator will set the username and password (e.g : user1, password ; user2, password2) - if needed, the username will be enabled and be given to the user - if unused, the username will simply be disabled so no authenticated user could connect eventhough they remember the password. - I don't need the billing system just the administration tools. I already googled and found chillispot, but it seemed to be an overkill software. Are there anything simpler than chillispot? Thanks. Roberto

6 6

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

bluetooth mouse
by Roger K. Wells 17 May '10

17 May '10

Hello, I believe that it is well known that the scroll wheel on the Microsoft Bluetooth Mouse 5000 does not work on CentOS 5.4. It does, however, work as expected on Fedora 12 & Ubuntu 9.10 & 10.04. Does anyone know if there is a driver upgrade path for CentOS that will fix this problem? Thanks, roger wells -- Roger Wells, P.E. SAIC 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.wells(a)saic.com

1 0

centos release 5.5 issue
by Philip Manuel 17 May '10

17 May '10

Hi One of our developers has come across an issue with the new release. He provided this piece of code to show the problem:- cat failure.c #include </usr/include/asm-x86_64/msr.h> int main( int argc, char* argv[] ) { return 0; } gcc failure.c /usr/include/asm-x86_64/msr.h:169: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h:169: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h:169: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h: In function ‘rdmsr_on_cpu’: /usr/include/asm-x86_64/msr.h:171: error: ‘l’ undeclared (first use in this function) /usr/include/asm-x86_64/msr.h:171: error: (Each undeclared identifier is reported only once /usr/include/asm-x86_64/msr.h:171: error: for each function it appears in.) /usr/include/asm-x86_64/msr.h:171: error: ‘h’ undeclared (first use in this function) /usr/include/asm-x86_64/msr.h:171: error: ‘msr_no’ undeclared (first use in this function) /usr/include/asm-x86_64/msr.h:171: error: invalid lvalue in asm output 0 /usr/include/asm-x86_64/msr.h:171: error: invalid lvalue in asm output 1 /usr/include/asm-x86_64/msr.h: At top level: /usr/include/asm-x86_64/msr.h:173: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h:173: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h:173: error: expected declaration specifiers or ‘...’ before ‘u32’ /usr/include/asm-x86_64/msr.h: In function ‘wrmsr_on_cpu’: /usr/include/asm-x86_64/msr.h:175: error: ‘msr_no’ undeclared (first use in this function) /usr/include/asm-x86_64/msr.h:175: error: ‘l’ undeclared (first use in this function) /usr/include/asm-x86_64/msr.h:175: error: ‘h’ undeclared (first use in this function) Anyone else seen this or found a bug with these function definitions ? Thanks Phil

2 1

Re: [CentOS] Yum segmentation fault when updating to CentOS v5.5
by Sorin Srbu 17 May '10

17 May '10

>-----Original Message----- >From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf >Of Sorin Srbu >Sent: Monday, May 17, 2010 11:22 AM >To: 'CentOS mailing list' >Subject: Re: [CentOS] Yum segmentation fault when updating to CentOS v5.5 > >>-----Original Message----- >>From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On >Behalf >>Of cornel panceac >>Sent: Monday, May 17, 2010 10:59 AM >>To: CentOS mailing list >>Subject: Re: [CentOS] Yum segmentation fault when updating to CentOS v5.5 >> >> I'm getting a segmentation fault with yum when I try to update a >>CentOS v5.4 >> install to v5.5. >> >> >> >>try updating only some of the packages. if there's one package which can >not be >>updated with yum, rpm -Uvh > >Tried with yum update kernel*, yum update kernel-headers, yum update *lib* >and yum update httpd. Still gives me the seg fault error. 8-/ Never mind this problem. Just tried to start httpd and it gave me a segmentation fault as well. Something is not right with this particular machine and I think it's for the best to do a complete reinstall anyway. Thanks all. -- /Sorin

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss