Bug 688699 - rubygem-sunspot consistently times out
Summary: rubygem-sunspot consistently times out
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Aeolus
Classification: Retired
Component: conductor
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ian McLeod
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: ce-beta
TreeView+ depends on / blocked
 
Reported: 2011-03-17 18:38 UTC by Brian Harrington
Modified: 2014-03-04 00:33 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-25 22:48:38 UTC
Embargoed:


Attachments (Terms of Use)
Logs from attempting to install rubygem-sunspot (83.61 KB, text/plain)
2011-03-17 18:38 UTC, Brian Harrington
no flags Details

Description Brian Harrington 2011-03-17 18:38:12 UTC
Created attachment 486082 [details]
Logs from attempting to install rubygem-sunspot

Description of problem:
When attempting to install aeolus-conductor-daemons, the package rubygem-sunspot consistently times out from the repository.  All other packages download fine.

Version-Release number of selected component (if applicable):
http://repos.fedorapeople.org/repos/aeolus/packages/rhel-6/noarch/rubygem-sunspot-1.2.1-3.el6.noarch.rpm

How reproducible:
100%

Steps to Reproduce:
1. yum install aeolus-conductor-daemons
2. wait 30 seconds.... fail
3. repeat
  
Additional info:

When attempting to curl down the file, it will wait an average of two minutes before starting the download.  Once it does, the download completes quickly.

If the timeout in /etc/yum.conf is changed to 300 seconds, the install will complete.  That being said, none of the rest of the packages have this issue.  I have completed the install 4 times in a row with the same issue.

Comment 1 wes hayutin 2011-03-22 13:01:41 UTC
adding to ce-beta tracker

Comment 2 Brian Harrington 2011-03-25 22:48:38 UTC
So after a bunch of troubleshooting I figured out what the problem was....

The client uses a commercial proxy vendor.  Due to the size of the package, it was downloading it to the proxy server & attempting to scan it for viruses.  There was something in this package that was taking much longer to process than all of the rest of the RPMs for Aeolus.  Thus, the timeouts became visible.  While this could be an issue in the gem, I am more apt to chalk it up to being an issue with the proxy server.


Note You need to log in before you can comment on or make changes to this bug.