"Aborted by User"

Carlos Perez
Carlos Perez
Joined: 3 Oct 11
Posts: 6
Credit: 579841
RAC: 0
Topic 196029

So I have the following two work units that reported as "Aborted by User":

http://einsteinathome.org/workunit/106905436
http://einsteinathome.org/workunit/107871806

I did not abort these units as I leave my BOINC up and running pretty much all the time.

What caused this? Any ideas? That way I may be able to prevent such errors.

Thanks!

-C

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250587653
RAC: 34337

"Aborted by User"

The Client aborts tasks on its own when the deadline has passed and the task wasn't started yet.

BM

BM

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5872
Credit: 117700092448
RAC: 35074380

RE: ... I did not abort

Quote:
... I did not abort these units as I leave my BOINC up and running pretty much all the time.


At the moment, those two aborted tasks can be seen in this list of tasks for your HostID 4232913. They were aborted on the same day they were received so it can't be what Bernd suggested as they certainly weren't past deadline. One of them has a bit of accumulated run time so it would appear the task was aborted while it was running.

You weren't trying to suspend it by any chance, were you. On the tasks tab of BOINC Manager, the suspend button and the abort button are right next to each other. It sort of looks like you had selected two tasks to suspend and you accidently aborted them by mistake. They were both reported at exactly the same time and in the same scheduler contact you were sent two replacement tasks. Sure looks like an accidental abort by the user.

Cheers,
Gary.

Robert Jones
Robert Jones
Joined: 8 Jan 20
Posts: 2
Credit: 22807697
RAC: 91506

May not matter but for whom

May not matter but for whom it may concern, Computer 1 (my boinc computer) has had a very frustrating memory issue (meaning that trying to figure out that is WAS a memory issue was frustrating) LOL.

Anyway, this caused me to dump work units, and for that I am sorry. The problem has been fixed (down to 32gb from 64gb until another 32gb shows up from the memory fairy (yes there is such a thing).

Again sorry for any inconvenience this may have caused.

On a better note, later this month, I will have Computer 2 finished x99 dual Mb 2x e5 2699v3 128GB ram 2x 1tb nvme  1x 4tb 7200 hd... after overclocking, this should out perform Computer 1. 36 core/72 threads.

 

Thanks for your time.

mikey
mikey
Joined: 22 Jan 05
Posts: 12693
Credit: 1839099661
RAC: 3717

Robert Jones wrote: May not

Robert Jones wrote:

May not matter but for whom it may concern, Computer 1 (my boinc computer) has had a very frustrating memory issue (meaning that trying to figure out that is WAS a memory issue was frustrating) LOL.

Anyway, this caused me to dump work units, and for that I am sorry. The problem has been fixed (down to 32gb from 64gb until another 32gb shows up from the memory fairy (yes there is such a thing).

Again sorry for any inconvenience this may have caused.

On a better note, later this month, I will have Computer 2 finished x99 dual Mb 2x e5 2699v3 128GB ram 2x 1tb nvme  1x 4tb 7200 hd... after overclocking, this should out perform Computer 1. 36 core/72 threads.

Thanks for your time. 

Dumping work units does nothing more than put them back in the queue for someone else to run, it's no biggie in the overall scheme of things. Yes if you dump alot of work units it can count against you getting future tasks but that builds back up again really quickly.

Regarding your pc's you do know how to make people envious!!!

Over the next few weeks I will have more cores overall working for Boinc but nothing with the horsepower in any single machine like you do!! I do the 'shotgun' approach with a bunch of pc's instead of a couple really good ones.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.