I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

---

I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

Mikey, the quota on that machine was likely reduced because of the large number of client errors it has been producing. Your quota is reduced in cases like these until the source of the problem is straightened out and you are submitting valid results again.

Hope this helps,

Dig

I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

In seti the limit is 100/day per cpu for one computer, with upper limit 4 cpu's. This means 100-400 per day for one computer.

Any error decreases this limit with 1, while any "success"-result doubles the limit, but never below 1 or above the default 100.

I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

Mikey, the quota on that machine was likely reduced because of the large number of client errors it has been producing. Your quota is reduced in cases like these until the source of the problem is straightened out and you are submitting valid results again.

Hope this helps,

Dig

But if you notice on that machine, and yes that is the one, everything was fine until today! It tried to download a ton of units today but up until today was working just fine, I did upgrade it to version 4.43 today and maybe I will have to go back and use version 4.25 or even 4.19, I have both. I will give it until tomorrow and see if it clears up...thanks for the help.

---

I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

In seti the limit is 100/day per cpu for one computer, with upper limit 4 cpu's. This means 100-400 per day for one computer.

Any error decreases this limit with 1, while any "success"-result doubles the limit, but never below 1 or above the default 100.

That is what I thought but up until today it was working just fine, today I upgraded to version 4.43 and it went haywire! I will wait until tomorrow and see if it clears up if not then I will go back to ver 4.19 or 4.25, I have both.
I will go to 4.25 first, then to 4.19 if 4.25 doesn't work.

---

I thought I last read it was upped to 100 per 24 hours, but I have one machine that is tellin me I have reached the max after 24!
That machine is running version 4.43 and is now doing more Einstein that I would like it to.

In seti the limit is 100/day per cpu for one computer, with upper limit 4 cpu's. This means 100-400 per day for one computer.

Any error decreases this limit with 1, while any "success"-result doubles the limit, but never below 1 or above the default 100.

That is what I thought but up until today it was working just fine, today I upgraded to version 4.43 and it went haywire! I will wait until tomorrow and see if it clears up if not then I will go back to ver 4.19 or 4.25, I have both.
I will go to 4.25 first, then to 4.19 if 4.25 doesn't work.

If you've just started with 4.43 there are some other factors that affect this, including the scheduler mode.

It'll sort itself out, but it might take more than a day, especially if your cache is large.

---

[/quote]
If you've just started with 4.43 there are some other factors that affect this, including the scheduler mode.

It'll sort itself out, but it might take more than a day, especially if your cache is large.[/quote]
No I have my cache set for 1 day, but thanks I may just wait it out.

---

If you've just started with 4.43 there are some other factors that affect this, including the scheduler mode.

It'll sort itself out, but it might take more than a day, especially if your cache is large.

No I have my cache set for 1 day, but thanks I may just wait it out.

What I was trying to say is that the the may affect how it allocates work for more than one day, even if you have less than one day in your cache.

So, if you decide to "give it a day" you may be switching back just as the scheduler settles in and everything gets balanced.

---

So, if you decide to "give it a day" you may be switching back just as the scheduler settles in and everything gets balanced.

I'm sure Ned is correct about the scheduler and giving 4.43 a chance to do it's balancing act, but that doesn't explain your original question/problem regarding your low quota. It looks like you installed 4.43 on 21 May 2005 15:11:24 UTC and that is also when your first client error occurred. Every work unit that 4.43 has downloaded since then has errored out as well, giving you a total of 76 client errors as of 22 May 2005 8:54:42 UTC. This explains your reduced quota of 24 (100 minus 76).

Scheduler issues aside, I think there is something else going on with that machine that may need your attention.

Dig

So, if you decide to "give it a day" you may be switching back just as the scheduler settles in and everything gets balanced.

I'm sure Ned is correct about the scheduler and giving 4.43 a chance to do it's balancing act, but that doesn't explain your original question/problem regarding your low quota. It looks like you installed 4.43 on 21 May 2005 15:11:24 UTC and that is also when your first client error occurred. Every work unit that 4.43 has downloaded since then has errored out as well, giving you a total of 76 client errors as of 22 May 2005 8:54:42 UTC. This explains your reduced quota of 24 (100 minus 76).

Scheduler issues aside, I think there is something else going on with that machine that may need your attention.

Dig

It could be, but a later message said "everything was fine until today when I loaded 4.43" so I think we're seeing how the scheduler initially handles short term debt vs. zero long term debt.

---

It could be, but a later message said "everything was fine until today when I loaded 4.43" so I think we're seeing how the scheduler initially handles short term debt vs. zero long term debt.

I guess my thinking is that something may have gone awry with the 4.43 install itself. It's not that the new scheduler isn't giving him work, because it is... they just keep getting client errors. If you look at his results you'll see that 4.43 downloads 3 work units, and they immediately error out. Then it downloads 3 more, and they error out, and so on, and so on. Every few minutes he's been getting 3 more units and 3 more client errors which now total 76. It has since stopped downloading work for him, but I can only assume that when he does get more, they will error out as well?

Just my thoughts. Carry on. :)

Dig

That is what I thought but up until today it was working just fine, today I upgraded to version 4.43 and it went haywire! I will wait until tomorrow and see if it clears up if not then I will go back to ver 4.19 or 4.25, I have both.
I will go to 4.25 first, then to 4.19 if 4.25 doesn't work.

Did you install the optimized seti-application at the same time you started getting only errors, or later?

Have you tried re-booting the computer, it's possible a problem will be fixed after reboot.

Another possibility is that a windows-bug that is fixed in sp4 is screwing up things since you're still running sp3.

Also, only 96 MB memory running win2k is in my opinion too little, but this shouldn't in itself give errors...

That is what I thought but up until today it was working just fine, today I upgraded to version 4.43 and it went haywire! I will wait until tomorrow and see if it clears up if not then I will go back to ver 4.19 or 4.25, I have both.
I will go to 4.25 first, then to 4.19 if 4.25 doesn't work.

Did you install the optimized seti-application at the same time you started getting only errors, or later?

yes I did

Have you tried re-booting the computer, it's possible a problem will be fixed after reboot.

yes

Another possibility is that a windows-bug that is fixed in sp4 is screwing up things since you're still running sp3.

I could try but it is set to auto and it just hasn't downloaded it yet. The machine has been running for awhile now, more than a year, and just has not downloaded SP4.

Also, only 96 MB memory running win2k is in my opinion too little, but this shouldn't in itself give errors...

Yes I have that on my todo list and it may get done tomorrow, depend on the garage. My older son wrecked my younger sons car, not into each other, so I am dealing with that too right now.

---

I guess my thinking is that something may have gone awry with the 4.43 install itself. It's not that the new scheduler isn't giving him work, because it is... they just keep getting client errors. If you look at his results you'll see that 4.43 downloads 3 work units, and they immediately error out. Then it downloads 3 more, and they error out, and so on, and so on. Every few minutes he's been getting 3 more units and 3 more client errors which now total 76. It has since stopped downloading work for him, but I can only assume that when he does get more, they will error out as well?

Just my thoughts. Carry on. :)

Dig

His later note says that he installed the optimized clients too, so I got fooled by Kepner-Tregoe.

I'll bet his app_info.xml file is inappropriate.

---

Did you install the optimized seti-application at the same time you started getting only errors, or later?

yes I did

In this case your errors is very likely from the optimized application, and no changing of BOINC core client will fix your problem.

If you're using the p3-application, try the general application. If using any of the p4 or amd64 try p3-application if this works.
If none of the available applications works, remove app_info.xml and see if this fixes your problems.

Did you install the optimized seti-application at the same time you started getting only errors, or later?

yes I did

In this case your errors is very likely from the optimized application, and no changing of BOINC core client will fix your problem.

If you're using the p3-application, try the general application. If using any of the p4 or amd64 try p3-application if this works.
If none of the available applications works, remove app_info.xml and see if this fixes your problems.

Actually it is an AMD 1400 Duron so there is only one optimized client available, under windows.
It gave lots of errors again today trying to download units and having "client error"s EVERYWHERE!!! So I uninstalled 4.43 and installed 4.25, I do not use ATI cards OR the graphics so it isn't an issue for me. Einstein is running fine and I will have to wait until tomorrow to see if Seti works, it should at this point. I am down to 12 units per day for that machine because of all the errors.
Sorry for the trouble!!!!!!

---

Did you install the optimized seti-application at the same time you started getting only errors, or later?

yes I did

In this case your errors is very likely from the optimized application, and no changing of BOINC core client will fix your problem.

If you're using the p3-application, try the general application. If using any of the p4 or amd64 try p3-application if this works.
If none of the available applications works, remove app_info.xml and see if this fixes your problems.

Actually it is an AMD 1400 Duron so there is only one optimized client available, under windows.
It gave lots of errors again today trying to download units and having "client error"s EVERYWHERE!!! So I uninstalled 4.43 and installed 4.25, I do not use ATI cards OR the graphics so it isn't an issue for me. Einstein is running fine and I will have to wait until tomorrow to see if Seti works, it should at this point. I am down to 12 units per day for that machine because of all the errors.
Sorry for the trouble!!!!!!

It is very likely to be the optimized S@H client. Try running with the standard S@H client for a while to see if that fixes the problem.

---

BOINC WIKI

It is very likely to be the optimized S@H client. Try running with the standard S@H client for a while to see if that fixes the problem.

Today it AGAIN was giving me nothing by Client Error's! So I have now done EXACTLY that! I am down to 6 per day available for this machine!!!

---

Your are not overclocking are you?

---

Your are not overclocking are you?

NO, never have, probably never will. I just checked and ANOTHER machine is doing the SAME THING! BOTH are AMD 1400 Duron's and DID have Tetsuji's AMD client running. I have JUST removed the optimized client from BOTH machines and I will see how they do tomorrow.

---