Error 416 from dl.google.com

628 views
Skip to first unread message

Tim

unread,
Mar 26, 2010, 5:44:25 PM3/26/10
to Google Linux Repositories Help - Google Linux Repositories Basics
I've just started getting Error 416 when trying to access
dl.google.com. How can I fix this ?

$ yum list
Loaded plugins: refresh-packagekit
http://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz:
[Errno 14] HTTP Error 416 : http://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz
Trying other mirror.
Error: failure: repodata/primary.xml.gz from google-chrome: [Errno
256] No more mirrors to try.
$

I'm running Fedora 12

Suki

unread,
Mar 26, 2010, 9:16:23 PM3/26/10
to Google Linux Repositories Help - Google Linux Repositories Basics
I'm by NO means an expert but, Google Chrome is probably helping. They
do a lot of debugging. If you are using it with a Gmail, try to enable
http settings @ the bottom of your pc Gmail acct. I had 2 do that 1ce
when I password reset. Sorry if I'm not more help. Kinda new 2
Linux....

On Mar 26, 5:44 pm, Tim wrote:
> I've just started getting Error 416 when trying to access
> dl.google.com. How can I fix this ?
>
> $ yum list

> Loaded plugins: refresh-packagekithttp://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz:

ocosta

unread,
Mar 30, 2010, 8:16:56 AM3/30/10
to Google Linux Repositories Help - Google Linux Repositories Basics
On Mar 26, 6:44 pm, Tim wrote:
> I've just started getting Error 416 when trying to access
> dl.google.com. How can I fix this ?
>
> $ yum list
> Loaded plugins: refresh-packagekithttp://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz:

> [Errno 14] HTTP Error 416 :http://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz
> Trying other mirror.
> Error: failure: repodata/primary.xml.gz from google-chrome: [Errno
> 256] No more mirrors to try.
> $
>
> I'm running Fedora 12

I've been seeing this too. This HTTP error 416 is really weird:
http://www.checkupdown.com/status/E416.html .

Also, if I disable google-chrome repo, virtualbox repo also gives the
same error:

yum --disablerepo=google-chrome list
Loaded plugins: presto, refresh-packagekit
http://download.virtualbox.org/virtualbox/rpm/fedora/12/x86_64/repodata/primary.xml.gz:
[Errno 14] HTTP Error 416 : http://download.virtualbox.org/virtualbox/rpm/fedora/12/x86_64/repodata/primary.xml.gz
Trying other mirror.
Error: failure: repodata/primary.xml.gz from virtualbox: [Errno 256]


No more mirrors to try.

Disabling both repos is a workaround, but there's something wrong
either with the repos or with yum, or both. BTW: PackageKit runs fine,
no workarounds needed.

ocosta

unread,
Apr 6, 2010, 9:01:21 PM4/6/10
to Google Linux Repositories Help - Google Linux Repositories Basics
On Mar 30, 9:16 am, ocosta wrote:
> On Mar 26, 6:44 pm, Tim wrote:
>
> > I've just started getting Error 416 when trying to access
> > dl.google.com. How can I fix this ?
>
> > $ yum list
> > Loaded plugins: refresh-packagekithttp://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz:
> > [Errno 14] HTTP Error 416 :http://dl.google.com/linux/rpm/stable/x86_64/repodata/primary.xml.gz
> > Trying other mirror.
> > Error: failure: repodata/primary.xml.gz from google-chrome: [Errno
> > 256] No more mirrors to try.
> > $
>
> > I'm running Fedora 12
>
> I've been seeing this too. This HTTP error 416 is really weird:http://www.checkupdown.com/status/E416.html.
>
> Also, if I disable google-chrome repo, virtualbox repo also gives the
> same error:
>
> yum --disablerepo=google-chrome list
> Loaded plugins: presto, refresh-packagekithttp://download.virtualbox.org/virtualbox/rpm/fedora/12/x86_64/repoda...
> [Errno 14] HTTP Error 416 :http://download.virtualbox.org/virtualbox/rpm/fedora/12/x86_64/repoda...

> Trying other mirror.
> Error: failure: repodata/primary.xml.gz from virtualbox: [Errno 256]
> No more mirrors to try.
>
> Disabling both repos is a workaround, but there's something wrong
> either with the repos or with yum, or both. BTW: PackageKit runs fine,
> no workarounds needed.

The problem is not on the repo side, but instead on yum: the patch
proposed for bug #577947 [https://bugzilla.redhat.com/show_bug.cgi?
id=577497] fixes the problem. Also, cleaning metadata *as the same
user running yum* also works (I was trying the cleanup with sudo).

Reply all
Reply to author
Forward
0 new messages