| 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: 26
|
|
| Author |
|
|
widdershins
Veteran Cruncher Scotland Joined: Apr 30, 2007 Post Count: 677 Status: Offline Project Badges:
|
Things should start flowing soon. I'm looking into the root cause now. Thanks, -Uplinger The answer is User Error If users didn't try to actually use it there wouldn't be a problem. The best solution is to reboot the users. This is usually accomplished by pushing them down a large flight of stairs. (Guidance provided by the BOFH IT sys admin handbook) ![]() [Edit 1 times, last edit by widdershins at Jul 14, 2017 10:30:59 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Getting work now -- many thanks!
|
||
|
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 286 Status: Offline Project Badges:
|
My Pending uploads all just went and downloads flowing again... Thanks
----------------------------------------
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 2173 Status: Offline Project Badges:
|
My Pending uploads all just went and downloads flowing again... Thanks Was out and about for a few hours, all seemed to have been settled by now...thanks again for looking into this, hope you find the root cause, preventing this from happening again. Ralf |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges:
|
So, the root cause was self inflicted. It appears a line of code made it into a script I was updating that caused the scheduler to not have proper access. I have fixed this and all seems to be operating as usual. I am sorry for this and thank you for your patience.
Thanks, -Uplinger |
||
|
|
Warped@RSA
Senior Cruncher South Africa Joined: Jan 15, 2006 Post Count: 440 Status: Offline Project Badges:
|
So, the root cause was self inflicted. It appears a line of code made it into a script I was updating that caused the scheduler to not have proper access. I have fixed this and all seems to be operating as usual. I am sorry for this and thank you for your patience. Thanks, -Uplinger Thanks for the hard work, Keith. It's a relief to know that the cause was found. I was worried about FAH2 trickles getting out of wack again, but all have been reported as valid.
Dave
|
||
|
|
|