• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

FaD, The website isn't the only thing F*#$ed up

O

office boy

Diamond Member
I don't know what the heck is going on, but this afternoon I just had about 20 units of work go the nice red "failed" status. Then the server that holds FaD for my mini-masses decided that it didn't like FaD anymore and kept killing the connection to clients. Also the Find-a-Drug service would no longer start and i could not open the Q, nor could I close fadsetup.exe..
Pain in the ass.

Anyway, i seem to be back up, but now FaD spy says "range check error" when i try and open it.

I can't help but wonder if this is all related to the site/server problems they are having.
 
Do you have your machines set to download the beta? If so that is your problem.Current jobs failing after downloading the beta has been reported by several people on the FaD forums.
 
I bet that's because you have "beta testing" checked in your FaD setup! Today they started testing the new 1.30 beta client and it is already known to do that to the current WUs.
 
Is it possible that we got the beta downloaded even though 'beta' is turned off? I had the red 'failed' status OffBoy describes, and ever since then my systems are taking forever to finish jobs. In fact the slow down is so severe that I was starting to think that some of my P4s were throttling back due to newly arrived summer heat here (Florida) -- but upon checking it turns out that wasn't the cause. Heh, heh, I even went so far as to put an external fan on one of my systems as a test.

Now this 'beta' thing comes to my attention and fits with my slowdown problem.
 
Originally posted by: emjem
Is it possible that we got the beta downloaded even though 'beta' is turned off? I had the red 'failed' status OffBoy describes, and ever since then my systems are taking forever to finish jobs. In fact the slow down is so severe that I was starting to think that some of my P4s were throttling back due to newly arrived summer heat here (Florida) -- but upon checking it turns out that wasn't the cause. Heh, heh, I even went so far as to put an external fan on one of my systems as a test.

Now this 'beta' thing comes to my attention and fits with my slowdown problem.
Click to expand...

The beta just came out yesterday.
Was you having problems before then?
What jobs are you running?
 
Must have been this beta, things seem to have gone crazy again after I reinstalled 1.25 last night. And yes I had that beta box checked, I thought it was for beta tests on drugs they were going to be adding. Auto downloading a Beta is BAD form imo.
 
My number have been significantly down lately. A couple of the machines I checked did not have the beta option enabled....yet my production is off. WTH is going on?
 
Originally posted by: BadThad
My number have been significantly down lately. A couple of the machines I checked did not have the beta option enabled....yet my production is off. WTH is going on?
Click to expand...

Are they on some of those long jobs?
 
Originally posted by: Freewolf
Originally posted by: BadThad
My number have been significantly down lately. A couple of the machines I checked did not have the beta option enabled....yet my production is off. WTH is going on?
Click to expand...

Are they on some of those long jobs?
Click to expand...

Not really, something is just FUBAR IMO with the FaD home stats. Last night I looked and I wasn't even listed on the TeAm....neither was mondo! wth? Looks like a meltdown of their stats server more than a client issue.

They better get this crap fixed, I've had it with DC projects that are screwed-up. I left SETI early because of the outtages and you can bet I'd convert to a new project if FaD screws me with stats. :|

 
I have at least 9 machines with jobs that have been running anywhere from 2 1/2 days to 4 1/2 days now due to finish up in the next 4 to 7 hours. Of course I also had 5 machines download the beta and fail on the jobs they was running at the time. my fault I should have made sure the beta box was unchecked.
 
Originally posted by: Freewolf
I have at least 9 machines with jobs that have been running anywhere from 2 1/2 days to 4 1/2 days now due to finish up in the next 4 to 7 hours. Of course I also had 5 machines download the beta and fail on the jobs they was running at the time. my fault I should have made sure the beta box was unchecked.
Click to expand...

Too bad about the lost jobs.

Too bad FaD beta's tend to suck so bad.

Do not get me wrong. I am a huge fan of beta software. At any given time I am usually activitly involved in at least one or two beta programs. In my experience FaD beta's are considerably less stable than any other beta software I have ever experienced. I am willing to live w/ a little pain, but losing all active jobs is just unacceptable and screams of inadequate testing before releasing the product to beta. After the last FaD beta, I went around to all of my machines and unchecked the beta box and do not forsee ever checking it again.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top