| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Next one due in >90 minutes......will see if it uploads ok or not.
![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
vaio --
Thanks for letting us know. Perhaps your system was making multiple attempts at the upload before allowing an unlock to complete. I will let knreed know that the problem has been resolved. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I probably "retried" the upload too soon perhaps, I know I repeatedly retried once I got frustrated with it.
Also was running an internet intensive app at the time but doubt that was relevant because other results went thru ok. ![]() |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
I cannot find anything wrong with the servers (and no evidence of a generalized problem). What happens is that when you start uploading the file is created on the file system and then locked by the process handling the upload. If the upload is interrupted, then the process handling the upload will hang around for several minutes (I would need to check the exact timeout) and then when apache decides the process is stale and more data is not coming it will then kill the process. At that time the lock on the file is released. If in the meantime, you attempt an upload again while the file is still locked, then you will see that message.
I believe that we have the timeout set to 5 minutes right now so it would take 5 minutes for the lock on the file to be released. If you attempted to force another update before that timeout then you would get that lock message. However, after that 5 minutes, you should be able to upload find. The BOINC backoff mechanism will probably jump to higher values during the meantime. Let us know if it happens again. If it does, then there might be some network problems somewhere that is breaking the connection and causing this to occur. We also might consider lowering this timeout value as well to reduce the number of stale connections. thanks, Kevin |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well as I said I retried numerous times.......but there were many spells well over 5 mins where it was uninterrupted during the 5 hours or so it sat here.
Yes, will report any further developments......internet intensive app is shut down for now. Next result due in 73 mins. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Addendum:
Problem seems specific to my machine as I have 4 online and this is the only one showing said behaviour. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
15/09/2007 21:28:13|World Community Grid|Reporting 1 tasks
![]() |
||
|
|
|