Thanks for the post h)`mps.....Just got home from work and saw that they are still down....wonder how soon they can get the AC repairman to get the chill on again.One rig out of Cuda work....sigh.
Weird coincidence. I had my first ever overheat on my main cruncher yesterday (Tuesday). Took me a few minutes to figure out that it was an overheat and not my 21" CRT going out. Was weird, I could ping the rig, and access the shares and read/write data to the disks, but it wouldn't respond to a momentary press of the power button, nor the keyboard sequence for a reboot/shutdown. Ended up having to pull the plug.Booted back up and both CPUs were over 60C, and that was after 3 minutes of nearly idle to boot back up. I have all the settings set for an automatic shutdown at 65A, apparently it didn't do that.So for the time being, I had to scale back to 50% of CPUs and put a box fan in the window since it is 30F outside. Seems kind of...wrong to use a window A/C when it is 30F outside, you know?
I wouldn't mind if there was an update on seti, it's about 13 hrs since they announced the temp shutdown.
Remember that this happened around 8 PM last night and it is just coming up on 8AM there currently.
May be a good time to clean dust bunnies...I blew my machine out yesterday with my air compressor. Running a lot cooler today.
Wish somebody could shed some light on this.
While I am moving things to the wifes Work Apartment (in and out).I have been emailing Debug Logs to the Seti Folks in an a attempt to sort what is happening. What I surmise:There is an issue with the Scheduler, not sure if it was an upgrade after the shutdown.There is an issue with Bruno, uploads. My older Boinc Core cleared first. My newer Boinc Cores are dead in the water.Somewhere in this libcurl rears its ugly head again.Off to loading for the trip in the morning.Regards