Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1925 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Android FAHV Clients All Erroring Out

I have several BOINC clients running on Android devices crunching nothing but FAHV units with the Android Vina application, and for some reason, nearly every result I've seen them return over the last few days has ended up in Error state. Upon further analysis, when I click on the work unit, I see all the other clients that processed these work units also resulted in Error, or some sort of Abort.

I saw the other posts about how the errored worked units were removed and rebuilt a few days ago, but I'm still seeing this problem even as of now. Is this still a known issue? Am I blowing something here, or does this need to be fixed from the project admin end?
[Mar 30, 2014 4:39:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Android FAHV Clients All Erroring Out

asawchuk: I'm seeing the exact same thing from 3/27 forward to today have had only one complete successfully. Noted that one had given errors to about 8 other users before mine completed, now waiting for a wing man to complete successfully too. In many cases they don't error out immediately either; had one run for 30 hrs before deciding to throw the error.
[Mar 30, 2014 5:16:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Android FAHV Clients All Erroring Out

Have you clicked on the error link to view the result log? What I'm seeing is that 99.9% of the errors on wingman are of the 195 type, with an accompanying

ERROR: VINA was killed by signal 9.

All signal errors, most frequently this #9 and also the rarer #11, had 2 going out with this during heavy load, are discussed in the faq: http://boincfaq.mundayweb.com/index.php?language=1&view=165

Nine suggests a process gone rampant. Not had a single one here since version 7.16.

Oddly, on the version, I've seen several wingman going feet skyward showing version 7.20, then after these first 2 additional copies circulated with 7.16. As if the feeder is confused what to pick. No, think we can safely consider that x86 apps, think this is what they are, wont process on arm.
[Mar 30, 2014 5:25:17 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Android FAHV Clients All Erroring Out

Maybe I should have a try .
[Apr 16, 2014 3:04:51 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread