| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: Known Issues [read only]
Thread: Outage |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges: 
|
We are experiencing an outage on the grid server side of the site. Thus many agents will not be able to return/get new work units until it is resolved. No action is needed on your part. We will post something when the problem is resolved. Thanks for your patience.
|
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges:
|
The servers have been working OK for several hours now, although we don't know if the problem is totally cured. The agent software on member machines behaved as it should with pauses and backoff wait times before trying to connect again. We have several things we are trying to help avoid the network related problem in the future. Thanks to the members who alerted us and noted what they saw on their agents. And, thanks for your patience.
|
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges:
|
Some of the network problems we saw last week are back. This will only affect some of your agents when they try to return a result. Please take no special action because the agents will retry automatically and should eventually reconnect. Meanwhile we will be determining the source of the problem. We have some measures in place which will let some agents connect and continue to operate. Thanks for your patience.
|
||
|
|
Viktors
Former World Community Grid Tech Joined: Sep 20, 2004 Post Count: 653 Status: Offline Project Badges:
|
The servers have been running smoothly for the last several hours. We have tuned our scripts so that the impact should be now minimized if this happens again. The cause seems to have been some sort of network glitch which is being further investigated.
|
||
|
|
|