[resolved] BUG: Resource Updates Resetting 6.3 b2 (OSX 10.10.3)

After I installed 6.3b2, I was notified of a large (~400MB) download. I authorized it, but it restarted after downloading nearly 70%. This morning I tried to start again. I know that the download was near the 40% range. When I checked on it after lunch (20 minutes later), the download was back to 0%. Here is a "sample" log.

I wrote about several issues including this one in this thread:

7851.20150422-124744.zip

Find more posts tagged with

Comments

Andrew Batishko

It looks like the application is trying to download a single large resource. Normally I would guess that it got to 70% (or 40%) and a download failure caused it to reset and try again. If that was happening, there should be a "Download failed" indication in the log, but I don't see that in your log. I'm also unable to think of anything else that would reset the displayed percentage to 0% without leaving some kind of indication in the log file.

With your network connection, how long would you expect it to take for a 400MB download to complete?

I'll do some checking and see if I can figure out what might be happening.

Which other thread are you referring to?

JT (alabama24)

https://community.logos.com/discussion/comment/719438#Comment_719438

Which other thread are you referring to?

Sorry, this thread: https://community.logos.com/forums/t/104078.aspx

With your network connection, how long would you expect it to take for a 400MB download to complete?

I have 3mps DSL. I would expect a 400MB download to finish between 15-60 minutes... depending upon how "slow" the internet happens to be & if others are using it at the same time. Both last night and today I was the only user, with only web browsing other than the download.

Andrew Batishko

https://community.logos.com/discussion/comment/719438#Comment_719438

I did some checking. It looks like downloading failures are dealt with in the following fashion:

If a download failure occurs, the low level download operation will be retried up to 3 times. This will reset the progress on that specific file to 0%, and no indications will be logged.
If the download exceeds the 3 time retry limit, the download job will be cleared and created again. This starts up the low level download again. Failures at this level can be retried up to 4 times, and will show up in the log.
If all of this retrying still fails, the update will be marked as failed. It will be retried the next time an update check is made.

At this point it looks to me like your application was still attempting the low-level retries.

JT (alabama24)

https://community.logos.com/discussion/comment/719454#Comment_719454

thanks Andrew.