Description of problem: Startet boinc-client, selected LHC@home. Everything worked nice. After setting everything up (with boincmgr), the program crashed with the attached messages. Version-Release number of selected component (if applicable): boinc-client-5.10.45-4.20080315svn.fc8 boinc-manager-5.10.45-8.20080315svn.fc8 boinc-client-5.10.45-8.20080315svn.fc8 How reproducible: Every time Steps to Reproduce: 1.start boinc_client 2.Boom Actual results: Expected results: Additional info:
Created attachment 303658 [details] Text copied from the terminal (backtrace)
This should be probably filed upstream into http://boinc.berkeley.edu/trac/ If you do not want to do it, I will, just tell me. Anyway, please try to produce the core file, type: ulimit -c unlimited boinc_client --run_cpu_benchmarks A core file should be produced (core.XXXXX), you should attach it to the ticket into Boinc trac or here. Did you use Boinc previously from the universal linux binary installer available at Boinc homepage? (If so, did it work?) Would you mind trying recompiling boinc on your computer and test it then? I'd send you detailed instructions, if you don't know how to.
No, it didn't produce a corefile, but it creates a lot of other files... (xml files and a lockfile + leaves to prosesses (i have hyper-threading, so to the OS its 2 CPU's)) Switching to another, empty folder made the cpu benchmark run fine (and lost my configuration). Setting it up with LHC@home now seems to work?!?
(In reply to comment #3) > No, it didn't produce a corefile, but it creates a lot of other files... (xml > files and a lockfile + leaves to prosesses (i have hyper-threading, so to the OS > its 2 CPU's)) > > Switching to another, empty folder made the cpu benchmark run fine (and lost my > configuration). Setting it up with LHC@home now seems to work?!? Hm, I guess I know now where is the problem: In your report I see "start boinc_client". Does it mean you just typed "boinc_client" in shell in current directory? Because then boinc assumes the current directory to be the working directory and the benchmarks might have failed e.g. because of insufficient permissions in the current directory. You should always run boinc daemon using "service boinc-client start" (and/or setup it to run in system-config-service or using chkconfig, if you wish it to run after each computer startup). This ensures that boinc is running with working directory set to /var/lib/boinc. (I'm also assuming you first installed boinc-client-5.10.45-4.20080315svn.fc8 and then updated to boinc-client-5.10.45-8.20080315svn.fc8, am I right?)
(In reply to comment #4) > (In reply to comment #3) > > No, it didn't produce a corefile, but it creates a lot of other files... (xml > > files and a lockfile + leaves to prosesses (i have hyper-threading, so to the OS > > its 2 CPU's)) > > > > Switching to another, empty folder made the cpu benchmark run fine (and lost my > > configuration). Setting it up with LHC@home now seems to work?!? > > Hm, I guess I know now where is the problem: In your report I see "start > boinc_client". Does it mean you just typed "boinc_client" in shell in current > directory? Yes, I did! > Because then boinc assumes the current directory to be the working > directory and the benchmarks might have failed e.g. because of insufficient > permissions in the current directory. > > You should always run boinc daemon using "service boinc-client start" (and/or > setup it to run in system-config-service or using chkconfig, if you wish it to > run after each computer startup). This ensures that boinc is running with > working directory set to /var/lib/boinc. > > (I'm also assuming you first installed boinc-client-5.10.45-4.20080315svn.fc8 > and then updated to boinc-client-5.10.45-8.20080315svn.fc8, am I right?) Probably - I installed it a while ago (never got it to work), and then I tried again after I saw and installed the patch in yum.
...just to be sure the problem is solved: does running Boinc in the proper way ("service boinc-client start") work for you now? You should see "Starting BOINC client as a daemon: [ OK ]" and you should be able to connect via Boinc manager, choose project etc.
It might be just me doing something stupid, but this doesn't work (no crashes, tough...): [root@storeulv ~]# service boinc-client start The BOINC client requires initialization. [ADVARSEL] Starting BOINC client as a daemon: [ OK ] (ADVARSEL is norwegian for WARNING) Boincmgr doesn't work: Authorization failed connecting to running client. Make sure you start this program in the same directory as the client.
OK, that's correct behavior: 1) The WARNING is displayed because boinc is not attached to any project. 2) To connect via boinc manager, type "localhost" as host name and password which is stored in /var/lib/boinc/gui_rpc_auth.cfg. (Hint: if you do NOT want to use any password, paste _only_ a newline into this file.) Closing as NOTABUG.