Beta 1.30

[PCZ]

I have just lost days of work.

My windows servers upgraded to 1.30 earlier today.
I only noticed when I got home from work, all the clients were showing down.

When I restarted them they all turned red and the jobs were failed.
Most of those jobs were qm3's which had been running for days.

Not a happy bunny at the moment :bang:

[Bok]

yikes,

just checked my one windows box I have running it and it has a failed job too :( I don't think my linux clients are affected though.

Sorry PCZ, perhaps Think will credit the work later ? I'm sure there will be an uproar on the forums...

Bok

[MerePeer]

@PCZ: ouch. Does it say why the Beta bombed?

I forgot that was happening. I was fairly sure my ./fadsetup did not allow the Beta project, but I didnt bother rechecking all the boxen. I'll keep a closer eye on the job names, and a wander over to the FAD forum to see what's up.

[Fozzie]

Should have warned all of you guys to untick beta as I lost 60K last time the new beta came out.

It was HIV jobs last time and they, like QM3s, took days to finish.

:swear:

[LAURENU2]

Originally posted by Fozzie
Should have warned all of you guys to untick beta as I lost 60K last time the new beta came out.

It was HIV jobs last time and they, like QM3s, took days to finish.

:swear:
Ya first day/week beta testing should only be done by people with 1 or 2 nodes
Farming testing should come only when it looks stable

[MerePeer]

When my net was down I noticed that I was able to switch over to ./fadsetup -connect None on a system which was running the 1.30c beta: this system did not get hung up when think finished a job -- it only stalled after the queue was exhausted. Whereas the 1.25g systems wanted to talk to find-a-drug before they would acknowledge the connect change, which of course they couldnt do because my net was down, so they end up w/hung server processes which hangs Think processes that have finished their assigned job. Linux.

When net returned I let a Windows box upgrade itself to 1.30c (seems that after you turn on the Beta project I think it waits until the current job is finished and it is talking to find-a-drug anyway so it does the upgrade at that point, i.e. not instantly). I already had set this box up with a windows "service" to run FAD, but after the upgrade the new 1.30c installs its own Windows service and so the two were competing with each other and so I simply had to shut my manually-installed service off and let the new service (Called Find-a-Drug in the service dialog) take over after rebooting. I do see a checkbox in the Windows fadsetup to disable the service.

Then I let another Windows box upgrade and forgot to deinstall the manually-installed service: now I must clean it up because I think I see it running both a PCNAME and PCNAME-1 jobs.

I'm not sure if the old version did this, but when a laptop was unplugged and in battery mode, FAD stopped itself:
5-AUG-05 21:45 Starting THINK v1.30c on PCNAME
5-AUG-05 21:45 THINK stopped - battery powered

I *might* be seeing the Windows boxen with a FAD rating a couple points higher than under 1.25g -- too many variables and too early to be sure -- maybe 1.30c is more efficient?

If I remember, after the 1.30c upgrade I go back into fadsetup and shut off BETA so that I won't be surprised when the next beta comes out.

So far I like 1.30c.

[FluffyChicken]

In the next beta version the 'service' option is going to be (or so THINK says) not set by default. IT's up to the user to then change it.


The laptop operation changed (I beleive due to my constant suggestions on it ;))
It alway stopped when on DC

But 1.25 and before would
- not be started under DC (no part of the program at all), this means you
--couldn't install it properly as fadsetup/think/server would not run
--update it properly as intended (as above, loader wouldn't start them)
, let along forget to do the next bit...
...If you switched to AC you had to manually start FAD.

If you started it on AC it acted just like normal :) But THINK terminated when it dropped to DC and restarted when you went back to AC.




1.30
Now Fadsetup ALWAYS runs no matter what the powerstate.
So now its a simple
On AC = Run
On DC = Stopped


Not forgetting to start the client if you happen to boot up in DC state.
You can install it no problem in DC state, it updates fine as well.

[FluffyChicken]

Originally posted by FluffyChicken
In the next beta version the 'service' option is going to be (or so THINK says) not set by default. IT's up to the user to then change it.


The laptop operation changed (I beleive due to my constant suggestions on it ;))
It alway stopped when on DC

But 1.25 and before would
- not be started under DC (no part of the program at all), this means you
--couldn't install it properly as fadsetup/think/server would not run
--update it properly as intended (as above, loader wouldn't start them)
, let along forget to do the next bit...
...If you switched to AC you had to manually start FAD.

If you started it on AC it acted just like normal :) But THINK terminated when it dropped to DC and restarted when you went back to AC.




1.30
Now Fadsetup ALWAYS runs no matter what the powerstate.
So now its a simple
On AC = Run
On DC = Stopped


Not forgetting to start the client if you happen to boot up in DC state.
You can install it no problem in DC state, it updates fine as well.


P.S. More efficient but afaik no change to the CPU Rating code