Comment 37 for bug 932088
Revision history for this message
| Deepti B. Kalakeri (deeptik) wrote Re: [Bug 932088] Re: Ubuntu EC2 package mirror intermitent failures | #37 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
On Tue, Apr 24, 2012 at 6:30 PM, Scott Moser <email address hidden> wrote:
> On Tue, 24 Apr 2012, Deepti B. Kalakeri wrote:
>
> > According to the comments in the bug above we have been able to resolve
> the 404 Not Found error and HashSum issue by using the following 2 things.
> > 1) sudo sed -i.dist 's,archive.
> archive.
> > 2) echo "Acquire:
> /etc/apt/
> >
> > I see on ci.linaro.org init for precise instance ami-b5ea34dc has been
> updated to use all the above.
> > But, even after applying those changes I still I got the 404 file not
> found, though not the HashSum mismatch errors this morning continuously.
> > With this the builds started to be queue in for longer time.
> > Finally I had to change the ami instance used from beta2 ami-b5ea34dc
> instance to beta1 ami-2061b349 instance and was able to proceed with the
> builds.
>
> I can't come up with an explanation for this.
> This doesn't really make any sense to me.
>
> I just launched an instance of ami-b5ea34dc, and ran the same 2 commands
> above and cannot replicate the issues. After doing so, I also did:
> apt-get dist-upgrade
> which downloaded 86M in 142 packages, and then
> apt-get --download-only --assume-yes install ubuntu-desktop^
> which downloaded 454M in 1009 packages
>
>
Well I have logs for the slave that used ami instance ami-b5ea34dc and
failed to start with the 404 failure in the morning.
Now the same slaves using ami-b5ea34dc instance are able to start without
the problem.
I am not an EC2 expert so am not sure why that failure occurred when I
tried earlier.
Anyways will keep a watch and inform if I see the problem again.
> Also, I see the following http URL in the error slave logs:
> > W: Failed to fetch
> http://
>
> This is a very confusing error indeed. The fact is that 'Packages', as
> opposed to Packages.gz or Packages.bz2 does not really exist anywhere.
> The error you're seeing is because the apt did not like the content it
> got for Packages.gz or Packages.bz2 (likely both of them) , and fell back
> to trying Packages, which resulted in a 404.
>
> Its annoying that apt basically hides the original error.
>
> --
> You received this bug notification because you are subscribed to Linaro
> CI.
> https:/
>
> Title:
> Ubuntu EC2 package mirror intermitent failures
>
> Status in Linaro Android Infrastructure:
> In Progress
> Status in Linaro Continuous Integration:
> New
> Status in Ubuntu:
> Confirmed
>
> Bug description:
> Not too frequent, but regularly (say, once a month) https:/
> build.linaro.org/ service, which is Jenkins with EC2 slaves, gets
> failures when initializing EC2 instances, which involves installing
> packages.
>
> The log looks like:
> Connecting to ec2-23-
> Waiting for SSH to come up. Sleeping 5.
> Connecting to ec2-23-
> Connected via SSH.
> Authenticating as ubuntu
> Connecting to ec2-23-
> Connected via SSH.
> Executing init script
> + apt-get update
> Ign http://
> Get:1 http://
> Get:2 http://
> Ign http://
> Ign http://
> Ign http://
> Ign http://
> Ign http://
> Ign http://
> Ign http://
> Packages/DiffIndex
> Ign http://
> Packages/DiffIndex
> Ign http://
> Ign http://
> TranslationIndex
> Ign http://
> Packages/DiffIndex
> Ign http://
> Packages/DiffIndex
> Ign http://
> TranslationIndex
> Ign http://
> TranslationIndex
> Err http://
> 403 Forbidden [IP: 10.210.205.172 80]
> Err http://
> 403 Forbidden [IP: 10.210.205.172 80]
> ...
>
>
> Trying to access a specific file manually shows that there're
> interleaving 404 and 403 responses for it (the file indeed doesn't exists).
> And generally situation look like 403 is being intermittently returned for
> any url (be it 200 or 404 one).
>
> ubuntu@
> http://
> --2012-02-14 13:42:12--
> http://
> Resolving us-east-
> 10.252.111.96, 10.202.26.15, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2012-02-14 13:42:12 ERROR 404: Not Found.
>
> ubuntu@
> http://
> --2012-02-14 13:42:14--
> http://
> Resolving us-east-
> 10.250.142.223, 10.252.111.96, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 2012-02-14 13:42:14 ERROR 403: Forbidden.
>
> ubuntu@
> http://
> --2012-02-14 13:42:16--
> http://
> Resolving us-east-
> 10.210.205.172, 10.250.142.223, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2012-02-14 13:42:16 ERROR 404: Not Found.
>
> ubuntu@
> http://
> --2012-02-14 13:42:17--
> http://
> Resolving us-east-
> 10.202.26.15, 10.210.205.172, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2012-02-14 13:42:17 ERROR 404: Not Found.
>
> ubuntu@
> http://
> --2012-02-14 13:42:18--
> http://
> Resolving us-east-
> 10.252.111.96, 10.202.26.15, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2012-02-14 13:42:18 ERROR 404: Not Found.
>
> ubuntu@
> http://
> --2012-02-14 13:42:19--
> http://
> Resolving us-east-
> 10.250.142.223, 10.252.111.96, ...
> Connecting to us-east-
> connected.
> HTTP request sent, awaiting response... 403 Forbidden
> 2012-02-14 13:42:19 ERROR 403: Forbidden.
>
> To manage notifications about this bug go to:
>
> https:/
>
--
Thanks and Regards,
Deepti