1) Message boards : Sixtrack Application : SIXTRACKTEST (Message 32186)
Posted 1 Sep 2017 by Armin
Post:
would it be possible to get a logcat to see which syscall is getting blocked?

I am not so familiar with ADB debugging. Is the regular command "adb logcat" sufficient enough to show the necessary info in the log file or which additional options/filter must be set in the command? I can try to log this when some WUs are available again and I am quick enough to connect my tablet with my Desktop PC.

Setting the debug options in the BOINC client itself has no effect. Any debug flag selection changes (like "android_debug") were not saved.
2) Message boards : Sixtrack Application : SIXTRACKTEST (Message 32179)
Posted 1 Sep 2017 by Armin
Post:
I made a short test with my tablet but all tasks failed: My Pixel C.
Looks like that I have no CPU type ;-)
3) Message boards : News : More work coming now. (Message 25547)
Posted 9 May 2013 by Armin
Post:
@Eric: Perhaps you will take a look to this problem. May be that this is correlated with the behaviour of not sending any work units.

I have found some hundred work units from different users, which generated the same error message. The WUs were created yesterday, ca. 18:17 UTC:

<core_client_version>7.0.64</core_client_version>
<![CDATA[
<stderr_txt>
[fort.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in fort.zip,
        and cannot find fort.zip.zip, period.
20:23:34 (7148): called boinc_finish

</stderr_txt>
]]>



Example: wuid=6962011

Good luck!



©2019 CERN