Posts by AMDave

1) Message boards : Number crunching : Error in the PARI system (Message 65)
Posted 25 Aug 2011 by AMDave
Post:
Caught the output of a computation error on Linux AMD64
BOINC core and manager ver 6.10.58
ia32libs installed
most wu's complete successfully
client app ver is 1.03
output follows
Stderr output

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
APP: Checkpoint Flag = 0.
APP: a21 Starting Value = -10000000.
APP: PolyCount starting value = 0.
APP: Stat Count 1 = 0.
APP: Stat Count 2 = 0.
APP: Stat Count 3 = 0.
APP: Reading file ../../projects/stat.la.asu.edu_NumberFields/wu_12E10_SF-3-0_Idx2_Grp9019of11232.dat
Disc Bound = 120000000000.00000000
    K = y^2 + 3
    TgtFlag = 0
    a1 Index = 2
    a5 = 4 + 8w
    a22 = 2
    |dK| = 3
    Signature = [0,1]
  sig1w = [1, -0.50000000000000000000000000000000000000 - 0.86602540378443864676372317075293618347*I]
  sig2w = [1, -0.50000000000000000000000000000000000000 + 0.86602540378443864676372317075293618347*I]
  a11 = 0
  a12 = 1
  sig1a1 = -0.50000000000000000000000000000000000000 - 0.86602540378443864676372317075293618347*I
  sig2a1 = -0.50000000000000000000000000000000000000 + 0.86602540378443864676372317075293618347*I
  Ca1_pre = 0.400000
APP: Opening output file ../../projects/stat.la.asu.edu_NumberFields/wu_12E10_SF-3-0_Idx2_Grp9019of11232_1_0
APP: Now starting the Martinet search:
      2nd part of Martinet bound = 28.284271.
      Martinet bound = 28.684271.
            a21_L = -6.
            a21_U = 7.
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
APP: Starting GetDecics checkpoint.
APP: GetDecics checkpoint done
  ***   segmentation fault: bug in PARI or calling program.
  ***   Error in the PARI system. End of program.

</stderr_txt>
]]>


searched on "libpari" and "PARI/GP" and found verious references to the same output message.
a more current discussion thread can be found here:
http://old.nabble.com/Trapping-errors-in-library-mode-td31332062.html

This could be a hard one to debug.
Timing shows it ran for 4,890.10 seconds before the error occurred.

HTH
2) Message boards : News : Private messaging now operational (Message 63)
Posted 24 Aug 2011 by AMDave
Post:
Confirmed working
3) Message boards : Number crunching : Process got signal 11 (Message 60)
Posted 24 Aug 2011 by AMDave
Post:
Thanks for the quick reply.
I'm out of ideas then.
Your experience makes it more likely to be some extraordinary WU parameters causing the client app to crash then.
I checked my results and I have had a few errors on 64-bit Linux and Win7, but not many.
Perhaps admin can query the results database and see if there are any trends in errors.
Sounds like fun ;)
4) Message boards : Number crunching : Process got signal 11 (Message 58)
Posted 24 Aug 2011 by AMDave
Post:
For your windows machine, I can't suggest anything other than a project reset (see below).

But for your linux machine [edit- if you are running 64-bit linux kernel -edit], we cannot rule out the ia32lib dependency if the client app uses a 'wrapper'.
The client app may be compiled in 64-bit but we have witnessed wrappers around 64-bit client apps that still have a 32-bit dependency.
This can be resolved by installing ia32lib

But that would only be if ALL of your wu's are failing on the linux box.
If it is only some of them then it could be some extraordinary parameters in the WU that cause the client app to SIGSEGV

Reference

In the latter case (intermittent signal 11's) try resetting the project (or detach and re-attach) to get a 'clean' set of the latest project files.
Apparently this can occur when files get 'mixed up'.
A couple of days ago our machines were processing work with 3 different versions of the client app at the same time (1.01, 1.02 and 1.03).
That could have done it.

Reference

HTH
5) Message boards : News : Private messaging now operational (Message 57)
Posted 24 Aug 2011 by AMDave
Post:
Test message sent with various tags
6) Message boards : News : Link to server status added (Message 50)
Posted 23 Aug 2011 by AMDave
Post:
example:
http://boincstats.com/page/project_status.php

another example:
http://stats.free-dc.org/stats.php?page=boinc_status

The static XML gets imported by quite a few sites these days.
7) Message boards : Cafe : will not be empty any longer (Message 44)
Posted 22 Aug 2011 by AMDave
Post:
Hey Moon!

messaging issue reported here:
http://stat.la.asu.edu/NumberFields/forum_thread.php?id=7




Main page · Your account · Message boards


Copyright © 2017 Arizona State University