On Tue, Apr 17, 2007 at 09:49:45PM +0100, Mário Gamito wrote:

Hi,

...

Seriously though, how about details? What are you trying to do? Error messages, changes to the config file, CentOS version, etc. etc.

The CentOS version is in the Subject.

There's no error messages. It just hangs.

Then please do an strace of yum and tcpdump port 53 and send the logs here.

Mário Gamito wrote:

Luciano Miguel Ferreira Rocha wrote:

...

Then please do an strace of yum and tcpdump port 53 and send the logs here.

strace: write(2, "Cannot find a valid baseurl for "..., 45Cannot find a valid baseurl for repo: update ) = 45 write(2, "Error: Cannot find a valid baseu"..., 52Error: Cannot find a valid baseurl for repo: update

Maybe your yum config files are wrong?

On 18/04/07, Mário Gamito mgamito@telbit.pt wrote:

Hi,

...

Maybe your yum config files are wrong?

Don't think so, because if i use the companie's DNS server it works fine.

Maybe it's the caching server then? You say everything works fine, have you tried 'dig'-ing @localhost for the addresses used in your Yum configuration?

Is the system firewalled for outgoing connections? Are yum's DNS queries possibly generating either TCP or UDP packets being dropped by the firewall?

Is the system running SELinux? Could it be that there's no valid SELinux policy/context for DJBDNS cache? Is your DJBDNS compiled from source or from a package?

Have you tried upping the yum log level with -d99 or similar?

Will.

On Tue, Apr 17, 2007 at 10:55:19PM +0100, Mário Gamito wrote:

Luciano Miguel Ferreira Rocha wrote:

...

Then please do an strace of yum and tcpdump port 53 and send the logs here.

strace: write(2, "Cannot find a valid baseurl for "..., 45Cannot find a valid baseurl for repo: update ) = 45 write(2, "Error: Cannot find a valid baseu"..., 52Error: Cannot find a valid baseurl for repo: update

An strace of the resolving process, not of error output, please.

[root@mail new]# tcpdump -vv port 53 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 22:55:01.978953 IP (tos 0x0, ttl 64, id 16651, offset 0, flags [DF], proto 17, length: 72) mail.telbit.pt.61225 > eth0-0.b.rbl-auth.sr.sonic.net.domain: [bad udp cksum 4532!] 42121 A? python.org.multi.surbl.org. (44) 22:55:02.526241 IP (tos 0x0, ttl 64, id 16651, offset 0, flags [DF], proto 17, length: 72) mail.telbit.pt.33261 > spamrbl2.mcafee.com.domain: [bad udp cksum ce00!] 51135 A? python.org.multi.uribl.com. (44) 22:55:03.104622 IP (tos 0x0, ttl 64, id 16651, offset 0, flags [DF], proto 17, length: 74) mail.telbit.pt.50508 > spamrbl2.mcafee.com.domain: [bad udp cksum ecfb!] 9692 A? virginia.edu.multi.surbl.org. (46) 22:55:03.104645 IP (tos 0x0, ttl 64, id 16656, offset 0, flags [DF], proto 17, length: 74) mail.telbit.pt.22097 > dnsbl.blacknight.ie.domain: [bad udp cksum f533!] 20583 A? virginia.edu.multi.uribl.com. (46) 22:55:01.983398 IP (tos 0x0, ttl 64, id 16661, offset 0, flags [DF], proto 17, length: 58) mail.telbit.pt.19802 > figwort.arin.net.domain: [bad udp cksum 7a97!] 40306 NS? virginia.edu. (30) 22:55:01.983600 IP (tos 0x0, ttl 64, id 16661, offset 0, flags [DF], proto 17, length: 86) mail.telbit.pt.56866 > xlns3.returnpath.net.domain: 42634[|domain] 22:55:01.983759 IP (tos 0x0, ttl 64, id 16661, offset 0, flags [DF], proto 17, length: 87) mail.telbit.pt.6123 > spns3.returnpath.net.domain: 63864[|domain] 22:55:01.998373 IP (tos 0x0, ttl 64, id 16676, offset 0, flags [DF], proto 17, length: 86) mail.telbit.pt.25387 > xlns1.returnpath.net.domain: 56267[|domain] 22:55:01.998596 IP (tos 0x0, ttl 64, id 16676, offset 0, flags [DF], proto 17, length: 78) mail.telbit.pt.1285 > ns6.njabl.org.domain: [bad udp cksum 71ed!] 28273 A? 33.24.109.194.combined.njabl.org. (50)

I don't see any reply, but these queries are for black lists only.