As you may know already, we have a significant problem at the moment. Everyone using an app_info.xml file - which includes, but is not limited to, everyone using an optimised application - cannot download any new work.

We are seeing posts in Technical News and Number Crunching from people who are clearly suffering from this problem, but who say they don't have the technical knowledge (or fluency in technical English) to apply the workrounds which have been tested and recommended.

I wonder if some of these non-technical optimisers have been guided and supported by their teams?

If so, I would urge all team captains to publicise the problem, and offer quidance in whatever form is most appropriate and accessible to their team members (as Kirsten has already done, in Danish, for BOINC Denmark), through their team websites, fora or mailing lists. [My apologies if you have already done this.]

The main focal point for discussions about this issue is the thread Ghost WU issue (and some talk about deadlines) in the Number Crunching forum.

Many thanks.

As you may know already, we have a significant problem at the moment. Everyone using an app_info.xml file - which includes, but is not limited to, everyone using an optimised application - cannot download any new work.

I'd also like to mention that another option is to do work for other projects right now. This is particularly important if the participant here is not staying on the stock application to do the work and is then unwilling/unable to monitor all of their hosts to make sure that they don't start requesting work again before getting the app_info.xml out of the way again.

As you may know already, we have a significant problem at the moment. Everyone using an app_info.xml file - which includes, but is not limited to, everyone using an optimised application - cannot download any new work.

We are seeing posts in Technical News and Number Crunching from people who are clearly suffering from this problem, but who say they don't have the technical knowledge (or fluency in technical English) to apply the workrounds which have been tested and recommended.

I wonder if some of these non-technical optimisers have been guided and supported by their teams?

If so, I would urge all team captains to publicise the problem, and offer quidance in whatever form is most appropriate and accessible to their team members (as Kirsten has already done, in Danish, for BOINC Denmark), through their team websites, fora or mailing lists. [My apologies if you have already done this.]

The main focal point for discussions about this issue is the thread Ghost WU issue (and some talk about deadlines) in the Number Crunching forum.

Many thanks.

I have some serious issues with the app_info fix. I recommend people staying away from it since it gives problems with the Ben_joe app resulting in the need to reinstall Boinc in its entirety. Right now probably ten percent of those who have performed the fix will need to abort everything and reinstall.

And yes, I am crankmeister 3000 right now:-(
Carl

---

It is SEXY to DONATE!
Skype = demiurg2

Richards short 'trick': (Thank you again!:-)
--------------------------------------------------------
Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying


A thought:
Now I'm here and download WUs.
So I can let run BOINC like this.
Or I must finish the 'trick' to the end?
(Or if I let run BOINC all the time, then not? Only if I close BOINC?)


Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)
--------------------------------------------------------


I had done all the steps.
Reporting results was not all the time well.


Then I had done steps 1 to 3 and not more.
The whole time everything is O.K.
And the opt. app is running well!
My experiences! :-)

When I don't close BOINC, then everything must be O.K., or?
I think, I didn't had the chance to test, if I run out of work, then BOINC will download the stock app, or, without app_info.xml?

---

Richards short 'trick': (Thank you again!:-)
--------------------------------------------------------
Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying


A thought:
Now I'm here and download WUs.
So I can let run BOINC like this.
Or I must finish the 'trick' to the end?
(Or if I let run BOINC all the time, then not? Only if I close BOINC?)


Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)
--------------------------------------------------------


I had done all the steps.
Reporting results was not all the time well.


Then I had done steps 1 to 3 and not more.
The whole time everything is O.K.
And the opt. app is running well!
My experiences! :-)

When I don't close BOINC, then everything must be O.K., or?
I think, I didn't had the chance to test, if I run out of work, then BOINC will download the stock app, or, without app_info.xml?

---

It is SEXY to DONATE!
Skype = demiurg2

Richards short 'trick': (Thank you again!:-)
--------------------------------------------------------
Rename app_info.xml so it won't be recognised
Restart BOINC (service)
Update SETI - may not get through first time, but keep trying


A thought:
Now I'm here and download WUs.
So I can let run BOINC like this.
Or I must finish the 'trick' to the end?
(Or if I let run BOINC all the time, then not? Only if I close BOINC?)


Restore app_info.xml to original name
Wait until all transfers have finished
Restart BOINC (service)
--------------------------------------------------------


I had done all the steps.
Reporting results was not all the time well.


Then I had done steps 1 to 3 and not more.
The whole time everything is O.K.
And the opt. app is running well!
My experiences! :-)

When I don't close BOINC, then everything must be O.K., or?
I think, I didn't had the chance to test, if I run out of work, then BOINC will download the stock app, or, without app_info.xml?

what damage to boinc I have done the rename work around on all three of my hosts with no problems all 3 running and reporting Wu's now.???
and yes I did restore the file to its origional name so Im still running optomised.

---

I have some serious issues with the app_info fix. I recommend people staying away from it since it gives problems with the Ben_joe app resulting in the need to reinstall Boinc in its entirety. Right now probably ten percent of those who have performed the fix will need to abort everything and reinstall.

We're making up numbers now?

---

Dublin, California
Team: SETI.USA

As you may know already, we have a significant problem at the moment. Everyone using an app_info.xml file - which includes, but is not limited to, everyone using an optimised application - cannot download any new work.

this is not

not acceptably

until this is cleared, i stay away from Seti...

Greetings from Germany NRW
Ulli

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

---

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

It wasn't ment to be a solution just a quick fix to fill your cashe with work to get you on your way.

---

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimised apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimised apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

LOL on that note, it seems the other two splitters may have come up :O

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimised apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

LOL on that note, it seems the other two splitters may have come up :O

Eric has been spotted lurking in Beta. More midnight oil. (well, another ruined weekend).

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimised apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

_Clap-Clap_

---

I have some serious issues with the app_info fix. I recommend people staying away from it since it gives problems with the Ben_joe app resulting in the need to reinstall Boinc in its entirety. Right now probably ten percent of those who have performed the fix will need to abort everything and reinstall.

And yes, I am crankmeister 3000 right now:-(
Carl

I don't agree at all -

I just updated my farm - took me about 45 minutes. 15 of that was to write a script and test it to do the following. The other 30 minutes was to execute the script on my crunchers.

Script

C:
CD C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu\\
REN app_info.xml blablabla.xml


then reboot computer

DONE!

---
I am running different versions of BOINC and it worked all all - from trux, 5.5.0 and 5.8.xx

DONE!

All systems are a go. Not a single problem.

When the problem is fixed on Berkeley, Rename the app_info.xml back

---

Do we need to do anything when reporting WUs crunched under this "fix" for the optimized apps, or can we let them upload w/o issue (ie. not having to break the app_.xml file)

I have some serious issues with the app_info fix. I recommend people staying away from it since it gives problems with the Ben_joe app resulting in the need to reinstall Boinc in its entirety. Right now probably ten percent of those who have performed the fix will need to abort everything and reinstall.

And yes, I am crankmeister 3000 right now:-(
Carl

I don't agree at all -

I just updated my farm - took me about 45 minutes. 15 of that was to write a script and test it to do the following. The other 30 minutes was to execute the script on my crunchers.

Script

C:
CD C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu\\
REN app_info.xml blablabla.xml


then reboot computer

DONE!

---
I am running different versions of BOINC and it worked all all - from trux, 5.5.0 and 5.8.xx

DONE!

All systems are a go. Not a single problem.

When the problem is fixed on Berkeley, Rename the app_info.xml back

---

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimized apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

Yeah It isn't ideal, But I was able to download work and while I was at It I sped up My fifth PC to 3.02GHz from 1.8GHz. :D

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Do we need to do anything when reporting WUs crunched under this "fix" for the optimized apps, or can we let them upload w/o issue (ie. not having to break the app_.xml file)

Set 'No new work', then it's safe. Updating to report only works, updating and requesting work causes an error with app_info.

Guys, this is not a solution. Me, (and many of us...) won't use unoptimized apps. If this situation cannot be solved in few days, seti will lose a lot of crunchers.

Regards.

If you use the suggested work-round, 99% of you (well, everybody except Carl, so far) can continue using optimized apps, albeit with a bit of manual gardening in the farm. Not ideal, I agree, but it can be done.

I suggest you limp along as best you can for another 48 hours, then see if the project posts some definitive information when they get into the office on Monday morning. Then decide.

Alternatively, I think the work-round is going to drain the pond of available WUs in a couple of hours or so. If you leave now, there'll be more left for the rest of us, LOL!

Your call.

Yeah It isn't ideal, But I was able to download work and while I was at It I sped up My fifth PC to 3.02GHz from 1.8GHz. :D

I have made an aditional change on my pc and now im can report and get new work without problems and still running the opp app. It work now for 10 hours, even after a reboot.

after the work round, getting new work with the original app and the change to the opp app i have stop boinc again and renamed app_info again to another name. After this i started boinc again and can set seti to get new work, and it is working fine. It look boinc think it is working with with the original version but it crunches with the opp app. How i told above, it works the last 10 hours on my system.

happy crunching

Set 'No new work', then it's safe. Updating to report only works, updating and requesting work causes an error with app_info.

Let me understand .... every time we have an HTTP an error with app_info
berkeley generate some gost Run Units?

And what do you think about the suggestion written by crazyrabbit1?
(to rename at last app_info again and let run optimized apps
without che app_info file))

Bye,
Franz

---