Well I just came home and saw your answer, and I just found out that the WU finished only a few minutes ago ! What a coincidence, or was it fear ? (from the WU, that I would cancel it) :D

Anyway here is the beast : 2 days 18 hours of calculation for a total of 18 days 11 hours of computing time on my i7 !!!

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=859028388

I definitively hope that someone else is going to calculate it... and that I get "some kind of credit" for this :)

Guess what, now I have another mt WU working now (since 6mn) but it claims only 1h30 min left as an estimate... what can be SO different between these two ?

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=859028387

I've had one of these wu hang up, leaving 1 core out of 4 actually running till I restarted boinc.
I've done several of them and they're not validating.
There's definitely a problem here. I'm going to opt out of them for a while till it's fixed.
whoops.. nope. 4 open CL's and 1 N-body..all in the last 5 days.
something going on that's different.

---

;

Hi Jake. This is just feedback. I'm not fussed if these things don't get resolved for a while... (and I'm not looking at this message board every day)
I have a new n-body workunit de_nbody_08_05_orphan_sim_0_1413455402_59970
1) The task is showing ~8% progress after ~7.5 hours elapsed time with a remaining estimate of ~34 minutes. "Somewhat" optimistic I would say.
2) (Presumably a BOINC issue) I cannot select and copy lines from the task property window. Which makes detailed reporting a pain unless I use a screen snapshot
3) My user average statistics took a huge dive while the application was grinding away on the previous work unit I commented on. Does this average simply measure task completion - if so it's a bit simplistic.
Hope this feedback helps with some of your troubleshooting
Cheers
Chris

Hi Jake. This is just additional feedback with a similar issue as Chris Lee (Message 62648).

I have another n-body work unit( ps_nbody_09_10_orphan_real_2_1413455402_21718 )
that seems to be running very long.

1. The task is now past the deadline and only shows 52.683% completion with 94:18:01 elapsed time and 23:30:25 time remaining. Looks like 180 hours + WU.

2. I am running an Intel 2 Core Duo CPU @ 1.4 GHz w/ 4 Gb Ram on a 32 bit OS. The system runs about 22 hours a day.

Should I leave the WU keep running? Will I get credit if it finally finishes?

Because of the long run time, I have a couple of WU's that are partially finished and past the deadline.

Your thoughts.

Ciao!

Hi jake,

i got an intel i7 980 3ghz (6 cores), and none of the n-body aps was able to begin computing, even after more than an hour...

All other milkyway apps work without any problems...

So i cancelled them all and turned off nbody for moment because i don't want other boinc projects to be blocked by nbody WU...

Hope you will fix this and the different problems i read here ;)

---

Hello to whomever,

I've just returned the trail and have found a few new items that I've added to my dedicated unit.

Is there a graphics display that can run in my screensaver modes similar to Quake Catcher Net. or Seti@Home.

Just leave me the URL if there is or a simple no if not.

Thanks.

Edward

I am aborting de_nbody_08_05_orphan_sim_0_1413455402_345349_0

which after 16.5 hours at 0.411%/hr has achieved 6.78%.

I also have another N-Body workunit [de_nbody_08_05_orphan_sim_0_1413455402_195772_3]

If this one is similarly 0.4%/hr I shall be aborting it as well.

de_nbody_08_05_orphan_sim_0_1413455402_195772_3 was progressing slower than the previous N-Body Task at .37%/hr.

I've aborted it after 24 hours[9.08%] and won't do N-body Tasks until a new app version is released.

Greetings!

<first day to post this, found this thread dealing with N-body - as it may have the proper thread subjects from the issues I have trying to run Milkyway@Home>

I'm finding messages from BOINC telling me...

Milkyway@Home: Notice from server
Your app_info.xml file doesn't have a useable version of Milkyway@Home Separation (Modified Fit). and message containing N-body Simulation - same context...
DTD Tue 25 Nov 2014 03:40.36 AM EST

This is two notices each day, process I do is...
Reset Project>>Update

Continuing issue starting back in November 5th or thereabouts...

Searching Linux Mint V17 [Quiana]

Locates this xml file...

/user/share/boinc-app-milkyway
and file contents...
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>18</version_num>
<file_ref>
<file_name>milkyway</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Seems either I need this file, or I already have a file or do I need to delete this file so the system can sense this and reinstall?

Trying to help you run stuff but I'm not sure how to fix the above...

Any suggestions?
Regards!
:+> Andy <+:

Greetings!

<first day to post this, found this thread dealing with N-body - as it may have the proper thread subjects from the issues I have trying to run Milkyway@Home>

I'm finding messages from BOINC telling me...

Milkyway@Home: Notice from server
Your app_info.xml file doesn't have a useable version of Milkyway@Home Separation (Modified Fit). and message containing N-body Simulation - same context...
DTD Tue 25 Nov 2014 03:40.36 AM EST

This is two notices each day, process I do is...
Reset Project>>Update

Continuing issue starting back in November 5th or thereabouts...

Searching Linux Mint V17 [Quiana]

Locates this xml file...

/user/share/boinc-app-milkyway
and file contents...
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>18</version_num>
<file_ref>
<file_name>milkyway</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Seems either I need this file, or I already have a file or do I need to delete this file so the system can sense this and reinstall?

Trying to help you run stuff but I'm not sure how to fix the above...

Any suggestions?
Regards!
:+> Andy <+:

I think you should delete the file and then reset the project. It sounds as though it is behaving like an local override file and the server is saying it does not match the current app version but is being prevented from auto updating the app.

If Resetting does not work you might need to detach [Remove] and (Re)join the Poject

Greetings!

I seem to have solved the problem - abeit in several ways - similar to the "Buckshot" method of having the following steps performed... it's lengthy but if someone else that has this problem can find their answers - then it was worth the effort...

First:
Computer was a working "pull" for a required upgrade and installed new software - Linux Mint 17 - using Cinnamon...

Used Mint 17 on other machines but they never did get a similar message...

So, the system is an ASUS B75 Motherboard with 16GB ram with 250 GB hard drive and generic blu-ray DVD SATA drive - only thing different was previous install has a video driver for the GPU in a card on the PCIe backplane that worked with the previous software - it was not saved during the wipe and upgrade - figured I didn't need it.

Upon the install of the newer sofware the Synaptic package manager installed the meta-BOINC platform as well as several other support packages. A newer Video card was also replacing the older unit.[nVida replaced an older ATI]

So, while running - the Milkyway app the system used was from a stray directory install that synaptic or myself inadvertenly selected - removing all the BOINC install and reinstalling it seems to have worked but a lot of clean-up needed to be done by hand, both in Terminal and Mints' Files programs, to finish cleaning up the mess.

Lets' say - it wasn't a good clean install in the first place and I worked too fast to bring the refurbished system up and running without verifying all the bugs were worked out.

That's what I get for working too hard for the holidays and attempting to automate the system for a headless install to quietly run your work - unattended ... Ha! Fooled me! Foiled again! So rework and some minor tweaks and our systems are back in agreement...

So, I followed your advice, and had to rework some issues with Mints' suggestions of Video Upgrade packages - and - thanks to your tips and tricks - I'm functional again.

Thank You!
Regards!
:+> Andy <+:

Two issues with de_nbody_08_05_orphan_sim_0_1413455402_859206_0

a: it has acquired all 16 threads of m i7-5960x processor, but is actually only using about 2 threads at a time (overall cpu use averaging around 15%, and use bouncing around sort of randomly among all threads)

b: It has run over 91 hours, and percent complete is stalled at about 91.558.

I'm aborting now.

/Dave

---

Dave
www.damouth.org