[root@localhost aaron]# dig centos.arcticnetwork.ca ; <<>> DiG 9.2.4 <<>> centos.arcticnetwork.ca ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30518 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0 ;; QUESTION SECTION: ;centos.arcticnetwork.ca. IN A ;; ANSWER SECTION: centos.arcticnetwork.ca. 3478 IN A 206.75.218.52 ;; AUTHORITY SECTION: arcticnetwork.ca. 3478 IN NS ns2.arcticnetwork.ca. arcticnetwork.ca. 3478 IN NS ns3.arcticnetwork.ca. arcticnetwork.ca. 3478 IN NS ns4.arcticnetwork.ca. arcticnetwork.ca. 3478 IN NS ns1.arcticnetwork.ca. ;; Query time: 30 msec ;; SERVER: 130.16.0.5#53(130.16.0.5) ;; WHEN: Tue Dec 12 11:36:41 2006 ;; MSG SIZE rcvd: 129 [root@localhost aaron]# ping www.google.com PING www.l.google.com (72.14.253.99) 56(84) bytes of data. 64 bytes from 72.14.253.99: icmp_seq=0 ttl=241 time=0.000 ms 64 bytes from 72.14.253.99: icmp_seq=1 ttl=241 time=38.2 ms 64 bytes from 72.14.253.99: icmp_seq=2 ttl=241 time=33.2 ms 64 bytes from 72.14.253.99: icmp_seq=3 ttl=241 time=35.8 ms 64 bytes from 72.14.253.99: icmp_seq=4 ttl=241 time=48.6 ms ^X --- www.l.google.com ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4009ms rtt min/avg/max/mdev = 0.000/31.199/48.656/16.455 ms, pipe 2 [root@localhost aaron]# wget http://centos.arcticnetwork.ca/4.4/extras/i386/RPMS/yumex-1.0.2-1.0.c4.noarc h.rpm --11:37:07-- http://centos.arcticnetwork.ca/4.4/extras/i386/RPMS/yumex-1.0.2-1.0.c4.noarc h.rpm => `yumex-1.0.2-1.0.c4.noarch.rpm' Resolving centos.arcticnetwork.ca... 206.75.218.52 Connecting to centos.arcticnetwork.ca|206.75.218.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 367,266 (359K) [application/octet-stream] 100%[============================================================>] 367,266 174.37K/s 11:37:09 (174.10 KB/s) - `yumex-1.0.2-1.0.c4.noarch.rpm' saved [367266/367266] [root@localhost aaron]# yum -d 255 install yumex ---SNIP-- --> Populating transaction set with selected packages. Please wait. Member: yumex.noarch 0-1.0.2-1.0.c4 - u ---> Downloading header for yumex to pack into transaction set. yumex-1.0.2-1.0.c4.noarch 100% |=========================| 359 kB 00:01 http://mirror.chpc.utah.edu/pub/centos/4.4/extras/i386/RPMS/yumex-1.0.2-1.0. c4.noarch.rpm: [Errno -1] Header is not complete. Trying other mirror. yumex-1.0.2-1.0.c4.noarch 100% |=========================| 359 kB 00:01 http://centos.arcticnetwork.ca/4.4/extras/i386/RPMS/yumex-1.0.2-1.0.c4.noarc h.rpm: [Errno -1] Header is not complete. --SNIP-- Trying other mirror. ftp://ftp.linux.ncsu.edu/pub/centos/4.4/extras/i386/RPMS/yumex-1.0.2-1.0.c4. noarch.rpm: [Errno 4] IOError: [Errno ftp error] [Errno ftp error] 500 Unknown command. Trying other mirror. yumex-1.0.2-1.0.c4.noarch 100% |=========================| 359 kB 00:02 http://ftp.osuosl.org/pub/centos/4.4/extras/i386/RPMS/yumex-1.0.2-1.0.c4.noa rch.rpm: [Errno -1] Header is not complete. Trying other mirror. Error: failure: RPMS/yumex-1.0.2-1.0.c4.noarch.rpm from extras: [Errno 256] No more mirrors to try. Everything network-wise works - except yum. HTTP protocols work, ftp, samba, everything. Googling produced some blather about http proxies and something about chunked byte-transfer encoding not being supported by anonymous proxies, none of which made any sense on this network as (according to my sysadmin) there is absolutely no proxy whatsoever, anonymous or otherwise. -d 255 doesn't seem to produce any useable debug info as far as the connection goes - maybe there are python scripts I can modify to produce meaningful output? I know I'm not alone in this from my googling and I know the proxy issue hasn't resolved all the problems. I can't even find a cvs repository to check out the code and modify for my own debugging needs. I'll have a look at ethereal as soon as I figure out how to make it work - I can set up servers, routers etc. But I'm really not a network back-end guy - TCP/IP stack traces give me the willies. Only lead I have so far - wget reports the size of the file as 367,266 bytes. Yum reports the size of the file as 359 kB, or 367,616 bytes. Is yum approximating size, or is the library it's using to download inserting CR/LF instead of just LF? Am I getting into "your system uses UTF-8 and it should use ISO-8859-1" territory? Me not know. It has to be network, and yet other people within the network can run yum no problem. And I have no idea why ftp servers configured to support yum would report "Command not understood" - even if Yum was passing EPSV or something silly, those servers should obviously deal with whatever yum was passing. -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of David Timms Sent: December-11-06 4:43 PM To: Yellowdog Updater, Modified Subject: Re: Yum fails spectacularly a lot - and I miss it. Michael Stenner wrote: > On Mon, Dec 11, 2006 at 01:39:10PM -0700, Aaron Hawryluk wrote: >> I assume these are similar errors - I checked the mailing lists and whatever >> I could dig up on google and tried the proxy route - no joy, no love. >> According to my sysadmin there is no proxy on this network, and HIS Fedora >> Core 4 box does a yum update fine. Can anyone tell me a) how I can get more >> detailed error information (yes, I have tried -e 10 and -d 10, they don't >> actually tell me anything about the connection, just high-level stuff) and >> b)Whether there is any workaround for these issues. I have tried going the >> route of hard-coded ftp-only repos in the CentOS box and it responds with >> this: > > I'd suggest running ethereal or some other packet sniffer and see what > you can gather from a packet log. It's almost certainly some sort of > network problem. A proxy does sound like the most likely culprit. > Hopefully, a packet trace will turn something up. Along those lines: - dig {sitename} - does it resolve ? - ping www.google.com {should answer} - does wget work for any of the urls that fail ? - yum -d 255 whatever {and post the first two failures or so, without all the blank lines, as well as the actual command being attempted.} DaveT. _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxxxxx https://lists.dulug.duke.edu/mailman/listinfo/yum
