joshua353 / update-engine

Automatically exported from code.google.com/p/update-engine
Apache License 2.0
0 stars 0 forks source link

failed with error - timed out #7

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. I try the EngineRunner  from 2 folders local on my desktop, when i try the 
example
everything works fine. When i try my own .dmg that is 300 MB i get the error 
below.

2. I have doublechecked, the size and hash, cant see any weird there, could it 
be the filesize thats too large.

3. The dryrun command says it want to update, does dryrun check the filesize 
and hash
so everything is in order?

What is the expected output? What do you see instead?
2008-12-22 15:17:58.440 ksurl[1488:10b] Download (<NSURLDownload: 0x10c540>) 
failed with error - timed 
out file:///Users/myname/Desktop/new/my.dmg
finished update of com.myname.myfile:  Failure

What version of the product are you using? On what operating system?
EngineRunner-R3.5, Mac OS X 10.5.6 on a MacPro

Please provide any additional information below.

Original issue reported on code.google.com by i.am.mik...@gmail.com on 22 Dec 2008 at 2:31

GoogleCodeExporter commented 8 years ago
Hi,

It looks like you're hitting the 60-second time we're setting for the 
NSURLRequest in ksurl-main.m.  Try 
bumping up that value and see if it helps.  If it does, we can increase the 
default timeout.

The DryRun just gets the plist and sees if an update is necessary.  It doesn't 
actually download anything.

Original comment by borkwareLLC on 22 Dec 2008 at 2:59

GoogleCodeExporter commented 8 years ago
"If during a connection attempt the request remains idle for longer than the 
timeout interval, the request is 
considered to have timed out." 

(http://developer.apple.com/documentation/Cocoa/Reference/Foundation/Classes/NSU
RLRequest_Class/Ref
erence/Reference.html#//apple_ref/occ/instm/NSURLRequest/timeoutInterval)

The 60 timeout for NSURLRequests should only apply to idle periods, not the 
overall download time. If the 
download is going idle for more than 60 seconds, I'd suspect something else is 
wrong. For example, perhaps 
there's a network or proxy issue involved here. I think it's reasonable to 
consider a connection that's gone idle 
for more than 60 seconds to be an error.

Try downloading the 300 MB file directly from the command line using curl to 
help diagnose where the 
problem is.

Original comment by dev...@gmail.com on 28 Dec 2008 at 5:04

GoogleCodeExporter commented 8 years ago
ping. Any further comments on this bug? Otherwise, we'll assume there is no bug 
here and close this issue.

Original comment by dev...@gmail.com on 23 Feb 2009 at 7:09

GoogleCodeExporter commented 8 years ago
WIthout further information, we can't verify whether this is or is not an 
Update Engine issue. Closing this for now. 
Re-open if more info becomes avail.

Original comment by dev...@gmail.com on 27 Feb 2009 at 12:14

GoogleCodeExporter commented 8 years ago
Sorry i havent got time to look in this problem, did some more testing today,
and get it to work with a 10 mb dmg, the first problem was that my .dmg was not 
READ-ONLY. 

When i try a bigger .dmg (250 MB) i get this error "ksurl[43620:10b] Download 
(<NSURLDownload: 0x10cea0>) 
failed with error - timed out".

I dont know how to change that value in the ksurl-main.m, but you got some more 
input anyway! =)

Original comment by i.am.mik...@gmail.com on 26 Aug 2009 at 1:04