Posts by EG

1) Message boards : Number crunching : MW@H DBase problems (Message 67090) Posted 15 Feb 2018 by EG Post: Hey Everyone, I implemented something that might fix this today. The problem seems to be too many open connections on the database. I've made some configuration changed to help improve connection turnover and increase the connection limit. Jake I don't know what you did, but everything seems to be working fine now. Carrying a full load on everything with full cache's And good traffic relay also no delay in d'loading or uploading.... Now if they validate we are Good to GO!
2) Message boards : Number crunching : MW@H DBase problems (Message 67087) Posted 15 Feb 2018 by EG Post: Hey Everyone, I implemented something that might fix this today. The problem seems to be too many open connections on the database. I've made some configuration changed to help improve connection turnover and increase the connection limit. Jake Didn't solve my problem and now it's effecting Blackhawk 3 Hasn't effected either 1 or 4 yet (they are dual xeons while 2+3 are 8350's if that makes a difference) I've set the boinc manager project priority to 100 and Collatz priority to 1 so at least they don't run idle anymore. But seriously, this has gone to a very reliable project to a hit or miss proposition.... Don't know how much longer this can go....
3) Message boards : News : Changing Workunit Priority to 1 from 0 (Message 67081) Posted 14 Feb 2018 by EG Post: Hi Everyone, In order to use the "Use Reliable Host" feature built into the BOINC server software, we must change our workunit priority to 1 from 0. I am implementing this now and will check in over the weekend to make sure everything is running well. If you have any questions or see any issues, please let me know. Jake How about this one..... My Blackhawk 2 which has run the project off and on for a number of years in various configurations not reliably getting any work..... computer 736434 https://milkyway.cs.rpi.edu/milkyway/results.php?hostid=736434&offset=0&show_names=0&state=3&appid= Not only shows a massive number of invalid and inconclusive WU's to only 19 errored WU's, it's not receiving any WU's on any regular basis now.... Are you sure your modifications and adjustments aren't turning good crunchers into bad ones? I will not leave my machine sitting idle much longer..... Update: I've switched the machine back to Collatz, it's running a full load without problem..... I also tested it on Moo of which it runs there without problem also.... Seems to me like in chasing one problem you've created another even worse problem.