Info | Message |
---|---|
21) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18857 Posted 26 Jul 2008 by ![]() |
Are starting the client during boot ? MfG, MEX |
22) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18835 Posted 25 Jul 2008 by ![]() |
As the manager isn't started at boot, i prefer to change the cc_config.xml with gedit myself.Currently I have only written the flags into my cc_config.xml but until I reboot my computer, or restart the client, I wont get results from these flags ... After booting I still get the following messages with your cc_config.xml: Fri 25 Jul 2008 01:48:56 PM CEST||Unrecognized tag in cc_config.xml: <start_delay> Fri 25 Jul 2008 01:48:56 PM CEST||Starting BOINC client version 5.10.45 for i686-pc-linux-gnu Fri 25 Jul 2008 01:48:56 PM CEST||log flags: task, file_xfer, sched_ops, http_debug, proxy_debug, http_xfer_debug Fri 25 Jul 2008 01:48:56 PM CEST||log flags: network_status_debug Fri 25 Jul 2008 01:48:56 PM CEST||Libraries: libcurl/7.18.2 NSS/3.12.0.3 zlib/1.2.3 libidn/0.6.14 Fri 25 Jul 2008 01:48:56 PM CEST||Executing as a daemon Fri 25 Jul 2008 01:48:56 PM CEST||Data directory: /var/lib/boinc Fri 25 Jul 2008 01:48:56 PM CEST||Processor: 1 GenuineIntel Intel(R) Celeron(R) CPU 540 @ 1.86GHz [Family 6 Model 22 Stepping 1] Fri 25 Jul 2008 01:48:56 PM CEST||Processor features: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts pni monitor ds_cpl tm2 ssse3 cx16 xtpr lahf_lm Fri 25 Jul 2008 01:48:56 PM CEST||OS: Linux: 2.6.25.10-86.fc9.i686 Fri 25 Jul 2008 01:48:56 PM CEST||Memory: 2.71 GB physical, 3.99 GB virtual Fri 25 Jul 2008 01:48:56 PM CEST||Disk: 62.98 GB total, 56.26 GB free Fri 25 Jul 2008 01:48:56 PM CEST||Local time is UTC +2 hours Fri 25 Jul 2008 01:48:56 PM CEST|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1482516; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|SHA-1 Collision Search Graz|URL: http://boinc.iaik.tugraz.at/sha1_coll_search/; Computer ID: 31994; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|Rectilinear Crossing Numbers|URL: http://dist.ist.tugraz.at/cape5/; Computer ID: 39216; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9703324; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|orbit@home|URL: http://orbit.psi.edu/oah/; Computer ID: 8705; location: (none); project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 29977; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4482760; location: home; project prefs: default Fri 25 Jul 2008 01:48:56 PM CEST||General prefs: from orbit@home (last modified 27-Jun-2008 14:48:32) Fri 25 Jul 2008 01:48:56 PM CEST||Host location: none Fri 25 Jul 2008 01:48:56 PM CEST||General prefs: using your defaults Fri 25 Jul 2008 01:48:56 PM CEST||Reading preferences override file Fri 25 Jul 2008 01:48:56 PM CEST||Preferences limit memory usage when active to 1388.09MB Fri 25 Jul 2008 01:48:56 PM CEST||Preferences limit memory usage when idle to 2498.56MB Fri 25 Jul 2008 01:48:56 PM CEST||Preferences limit disk usage to 1.86GB Fri 25 Jul 2008 01:48:56 PM CEST|SHA-1 Collision Search Graz|Restarting task wu_sha1collisionsearchgraz_v55_1216958420_365_0 using sha1_collisionsearch_graz version 535 Fri 25 Jul 2008 01:49:37 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:38 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:39 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:40 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:41 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:42 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:43 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:44 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:45 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:46 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:47 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:48 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:49 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:50 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:51 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:52 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:53 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:54 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:55 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:56 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:57 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:58 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:49:59 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:00 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:01 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:02 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:03 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:04 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:05 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:06 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:07 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:08 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:09 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:10 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:11 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:12 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:13 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:14 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:15 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:16 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:17 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:18 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:19 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:20 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:21 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:22 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:23 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:24 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:25 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:26 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:27 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:28 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:29 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:30 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:31 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:32 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:33 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:34 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:35 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:36 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:37 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:38 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:39 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:40 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:41 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:42 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:43 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:44 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:45 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:46 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:47 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:48 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:49 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:50 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:51 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:52 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:53 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:54 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:55 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:56 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:57 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:58 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:50:59 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:00 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:01 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:02 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:03 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:04 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:05 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:06 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:07 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:08 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:09 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:10 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:11 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:12 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:13 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:14 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:15 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:16 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:17 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:18 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:19 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:20 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:21 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:22 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:23 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:24 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:25 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:26 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:27 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:28 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:29 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:30 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:31 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:32 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:33 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:34 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:35 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:36 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:37 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:38 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:39 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:40 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:41 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:42 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:43 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:44 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:45 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:46 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:47 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:48 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:49 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:50 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:51 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:52 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:53 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:54 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:55 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:56 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:57 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:58 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:51:59 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:00 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:01 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:02 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:03 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:04 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:05 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:06 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:07 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:08 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:09 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:10 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:11 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:12 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:13 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:14 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:15 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:16 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:17 PM CEST||[network_status_debug] status: don't need connection Fri 25 Jul 2008 01:52:18 PM CEST|lhcathome|Sending scheduler request: To fetch work. Requesting 1399 seconds of work, reporting 0 completed tasks Fri 25 Jul 2008 01:52:18 PM CEST||[http_debug] HTTP_OP::init_post(): http://lhcathome.cern.ch/lhcathome_cgi/cgi Fri 25 Jul 2008 01:52:18 PM CEST||[http_debug] [ID#0] info: getaddrinfo(3) failed for lhcathome.cern.ch:80 Fri 25 Jul 2008 01:52:18 PM CEST||[http_debug] [ID#0] info: Couldn't resolve host 'lhcathome.cern.ch' Fri 25 Jul 2008 01:52:18 PM CEST||[http_debug] [ID#0] info: Closing connection #0 Fri 25 Jul 2008 01:52:18 PM CEST||[network_status_debug] got http error and not still waking up Fri 25 Jul 2008 01:52:18 PM CEST||[http_debug] HTTP error: Couldn't resolve host name Fri 25 Jul 2008 01:52:18 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:19 PM CEST||[network_status_debug] need_phys_conn 0; trying google Fri 25 Jul 2008 01:52:19 PM CEST||Project communication failed: attempting access to reference site Fri 25 Jul 2008 01:52:19 PM CEST||[http_debug] HTTP_OP::init_get(): http://www.google.com Fri 25 Jul 2008 01:52:19 PM CEST||[http_debug] [ID#1] info: getaddrinfo(3) failed for www.google.com:80 Fri 25 Jul 2008 01:52:19 PM CEST||[http_debug] [ID#1] info: Couldn't resolve host 'www.google.com' Fri 25 Jul 2008 01:52:19 PM CEST||[http_debug] [ID#1] info: Closing connection #0 Fri 25 Jul 2008 01:52:19 PM CEST||[http_debug] HTTP error: Couldn't resolve host name Fri 25 Jul 2008 01:52:19 PM CEST||[network_status_debug] status: reference site lookup pending Fri 25 Jul 2008 01:52:20 PM CEST||Access to reference site failed - check network connection or proxy configuration. Fri 25 Jul 2008 01:52:20 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:21 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:22 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:23 PM CEST|lhcathome|Scheduler request failed: Couldn't resolve host name Fri 25 Jul 2008 01:52:23 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:24 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:25 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:26 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:27 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:28 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:29 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:30 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:31 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:52:32 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:33 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:34 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:35 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:36 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:37 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:38 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:39 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:40 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:41 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:42 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:43 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:44 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:45 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:46 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:47 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:48 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:49 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:50 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:51 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:52 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:53 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:54 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:55 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:56 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:57 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:58 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:52:59 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:00 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:01 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:02 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:03 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:04 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:05 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:06 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:07 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:08 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:09 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:10 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:11 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:12 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:13 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:14 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:15 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:16 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:17 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:18 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:19 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:20 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:21 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:22 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:23 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:24 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:25 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:26 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:27 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:28 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:29 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:30 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:31 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:32 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:33 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:34 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:35 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:36 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:37 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:38 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:39 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:40 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:41 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:42 PM CEST||[network_status_debug] status: need connection Fri 25 Jul 2008 01:53:43 PM CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 689 seconds of work, reporting 0 completed tasks Fri 25 Jul 2008 01:53:43 PM CEST||[http_debug] HTTP_OP::init_post(): http://orbit.psi.edu/oah_cgi/cgi Fri 25 Jul 2008 01:53:43 PM CEST||[http_debug] [ID#2] info: getaddrinfo(3) failed for orbit.psi.edu:80 Fri 25 Jul 2008 01:53:43 PM CEST||[http_debug] [ID#2] info: Couldn't resolve host 'orbit.psi.edu' Fri 25 Jul 2008 01:53:43 PM CEST||[http_debug] [ID#2] info: Closing connection #0 Fri 25 Jul 2008 01:53:43 PM CEST||[http_debug] HTTP error: Couldn't resolve host name Fri 25 Jul 2008 01:53:43 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:53:44 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:53:45 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:53:46 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:53:47 PM CEST||[network_status_debug] status: online Fri 25 Jul 2008 01:53:48 PM CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Fri 25 Jul 2008 01:53:48 PM CEST||[network_status_debug] status: online ... MfG, MEX |
23) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18834 Posted 25 Jul 2008 by ![]() |
The <start_delay> option won't work before version 6.x.With your cc_config.xml I get the following messages: Fre 25 Jul 2008 12:35:12 CEST||Unrecognized tag in cc_config.xml: <start_delay> MfG, MEX |
24) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18828 Posted 25 Jul 2008 by ![]() |
The <start_delay> option won't work before version 6.x.Currently I have only written the flags into my cc_config.xml but until I reboot my computer, or restart the client, I wont get results from these flags ... As I know about the clients quirk with not being able to connect to the www when started during boot, and how to correct this later with a restart, I am not in a hurry. MfG, MEX PS: How do I upgrade to a 6.x version of the client, and will i have to upgrade the manager too if I do this ? |
25) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18812 Posted 24 Jul 2008 by ![]() |
I've also found this thread:That looks very interesting ! I will try the following cc_config.xml : <cc_config> <log_flags> <http_debug> <http_xfer_debug> <network_status_debug> <proxy_debug> </log_flags> <options> [ <http_1_0> ] [ <start_delay>X</start_delay> ] </options> </cc_config>If the debug info doesn't help, maybe the option to delay the start of applications and/or updating to the new client 6.1.6 might help. MfG, MEX |
26) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18811 Posted 24 Jul 2008 by ![]() |
Anyway it seems to be a networking problem. What's the output of "host orbit.psi.edu", for example?I have already tried disabling SELinux or settig it to permissive, which didn't help. I assume stopping iptables wont help too, as RESTARTING the boinc-client manually after logging in with my username solves the problem. Something must be different at the time boinc is started during booting f9 and when I restart it later ... but as I am no expert for Linux I don't have any idea what that could be :rollingeyes: MfG, MEX PS: Next thing I try is installing BOINC on my PS3 with f9, if I have the same problems with my PS3 I can be sure that it is a problem of the RPM or the f9 release ... otherwise the hardware of my FSC ESPRIMO Mobile V5535 might be the source of my problem :( PPS: [mex@localhost ~]$ host orbit.psi.edu orbit.psi.edu has address 204.17.38.37 [mex@localhost ~]$But this doesn't say anything, as surfing with Firefox was always possible while the client still couldn't resolve the host name until I restarted it ( it seems that the client remembers some faulty status from the time when it is started during boot until it is ordered to restart ) |
27) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18781 Posted 23 Jul 2008 by ![]() |
Still the same as in http://boinc.berkeley.edu/dev/forum_thread.php?id=2896&nowrap=true#18725: "...Scheduler request failed: Couldn't resolve host name" MfG, MEX PS: This happens when I try to attach a new project: Mit 23 Jul 2008 17:10:18 CEST|SETI@home Beta Test|Restarting task ap_23ap08ab_B1_P0_00015_20080715_06439.wu_1 using astropulse version 434 Mit 23 Jul 2008 17:10:18 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 665 seconds of work, reporting 0 completed tasks Mit 23 Jul 2008 17:10:23 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Mit 23 Jul 2008 17:11:39 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 665 seconds of work, reporting 0 completed tasks Mit 23 Jul 2008 17:11:40 CEST||Project communication failed: attempting access to reference site Mit 23 Jul 2008 17:11:41 CEST||Access to reference site failed - check network connection or proxy configuration. Mit 23 Jul 2008 17:11:44 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Mit 23 Jul 2008 17:12:08 CEST||Fetching configuration file from http://www.chess960athome.org/alpha/get_project_config.php Mit 23 Jul 2008 17:14:00 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 665 seconds of work, reporting 0 completed tasks Mit 23 Jul 2008 17:14:05 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Mit 23 Jul 2008 17:16:01 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 665 seconds of work, reporting 0 completed tasks Mit 23 Jul 2008 17:16:06 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name |
28) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18764 Posted 23 Jul 2008 by ![]() |
One thing is the RPC connection, another then the connection to the project website.After I discovered my fault (creating the symlink for root and not for my user mex) RPC connection to localhost is working flawlessly. But I still have the problem that the client started during boot by f9 isn't able to connect to ANY projects website (until I restart the client manually as root) I just stumbled across some old notes I made. Those notes mention it's necessary to enable port 31416 to allow remote hosts to connect to the client. Sorry for all the confusion. It's been so long since I installed it and since it's worked trouble free I've never had to review the topic to make repairs.Currently I only want to connect to the client at localhost, so enabling port 31416 isn't a problem currently ... until I install boinc at my PS3 too and want to communicate with my PS3boinc using the manager on my notebook. How do I enable port 31416 in SELinux ? What project? Isn't it World Community Grid?Currently I am participating in 7 projects: Mit 23 Jul 2008 08:18:40 CEST|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1482516; location: home; project prefs: default Mit 23 Jul 2008 08:18:40 CEST|SHA-1 Collision Search Graz|URL: http://boinc.iaik.tugraz.at/sha1_coll_search/; Computer ID: 31994; location: (none); project prefs: default Mit 23 Jul 2008 08:18:40 CEST|Rectilinear Crossing Numbers|URL: http://dist.ist.tugraz.at/cape5/; Computer ID: 39216; location: home; project prefs: default Mit 23 Jul 2008 08:18:40 CEST|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9703324; location: home; project prefs: default Mit 23 Jul 2008 08:18:40 CEST|orbit@home|URL: http://orbit.psi.edu/oah/; Computer ID: 8705; location: (none); project prefs: default Mit 23 Jul 2008 08:18:40 CEST|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 29977; location: home; project prefs: default Mit 23 Jul 2008 08:18:40 CEST|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4482760; location: home; project prefs: default I don't start the client, but f9 does during boot !To RESTART the client I still have to use su to become root, and even worse: when the client is started at boot it isn't able to connect to the www unless I manually RESTART the client as root :(I'm getting confused here... But then the problem is that this client can't connect to the www and is unable to communicate with projects, download WU or upload results. A normal user ( like me working with my username mex at my V5535 notebook from FSC ) is not able to restart or start the client, as you need to become su for these tasks. The only option a normal user has is to deactivate the client from the EXTRAS of the manager (version 5.10.45). MfG, MEX PS: Of course I know the password for su, as i have installed f9 myself on my notebook. But I can't take you step by step through how f9 is starting the client during boot as I am not f9, or the maintainer of the RPM boinc-client which I installed with yum on a fresh installation of f9 at my FSC ESPRIMO Mobile V5535 The point is a normal user can't solve this problem without knowing the root password, and I don't want to restart the client as su whenever I boot f9 anyway (it is the job of f9 to start the client during boot, why should I do it when my OS should be able to do it ? :rollingeyes: ) |
29) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18750 Posted 22 Jul 2008 by ![]() |
I have now created the correct symlink and my own username is in the boinc group, but I still don't have full control over the client from the manager !If you want BOINC to be started automatically at boot, type "chkconfig boinc-client on". I can only STOP the client from the manager, but I cant RESTART or START the client :( To RESTART the client I still have to use su to become root, and even worse: when the client is started at boot it isnt able to connect to the www unless I manually RESTART the client as root :( MfG, MEX |
30) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18748 Posted 22 Jul 2008 by ![]() |
As mentioned in http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up I did of course use "/sbin/chkconfig boinc-client on" to tell Linux to auto-start the boinc-client daemon at boot time.I can only start the boinc demon as root !That's correct -- as for any other daemon. But the result didn't seem to work as expected. The boinc-client is indeed started during the boot, but it isnt able to connect to the www unless I manually restart it with "/sbin/service boinc-client restart". Can you please check /etc/init.d/boinc-client too if it is started at the right time (after access to the www is possible) and check if the user and/or group boinc has the necessary rights to access the www ?[mex@localhost ~]$ /sbin/service boinc-client start Starting BOINC client as a daemon: /etc/init.d/boinc-client: line 165: /var/log/boincerr.log: Keine BerechtigungCorrect too, the only odd thing I see right now is that it should return 4 instead of 0 (which is confusing -- I'll fix that of course and release an update occasionally). MfG, MEX PS: I too expected that "setenforce 1" will reverse the setting you suggested, as I had my first contact with Unix in the 80ies (I even bought MINIX 1.2 during this time for my PC after reading the book about OS from A.Tanenbaum !), I just wanted to be sure ... As there is a GUI to be found at SYSTEM > ADMINISTRATION > SELinux Management, I will try now to set "System Default Enforcing Mode" in "Status" to "Permissive" or "Disabled" ... 2 reboots later I can tell you now that neither "Permissive" nor "Disabled" has solved my problem. I still get the Messages ... Die 22 Jul 2008 23:38:52 CEST|SETI@home Beta Test|Restarting task ap_23ap08ab_B1_P0_00015_20080715_06439.wu_1 using astropulse version 434 Die 22 Jul 2008 23:40:28 CEST|orbit@home|Sending scheduler request: Requested by user. Requesting 666 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 23:40:29 CEST||Project communication failed: attempting access to reference site Die 22 Jul 2008 23:40:30 CEST||Access to reference site failed - check network connection or proxy configuration. Die 22 Jul 2008 23:40:33 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 23:41:33 CEST|orbit@home|Fetching scheduler list Die 22 Jul 2008 23:42:39 CEST|orbit@home|Sending scheduler request: Requested by user. Requesting 666 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 23:42:44 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 23:43:44 CEST|orbit@home|Sending scheduler request: Requested by user. Requesting 666 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 23:43:49 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name ...until I restart the client as root :( I am rebooting now to set "Enforcing" for SELinux again ... |
31) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18742 Posted 22 Jul 2008 by ![]() |
- What concerns SELinux, a quick way how to check whether SELinux is a reason of any troubles is setting it to permissive mode by typing "setenforce 0" as root and trying whether it works. If still not, then it is SElinux-unrelated for sure. Many thanks for your help Milos, I will try "setenforce 0" to deactivate SELinux later. If this doest cure my problem, I will try to deactivate starting boinc as a demon at boot or to start it at a later time in the boot to check if this is the issue why the client doesn't get a connection to the www until I restart it manually as root. I didn't use any hacks, except those mentioned in http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up , and will try installing boinc to a clean install on my PS3 as soon as I have found and corrected the reason for the client not beeing able to connect to the www unless I restart it manually as root. The issue with the manager not beeing able to connect automatically to localhost with a GUI_RPC_password is solved as I made the fault to create the symlink to the HOME directory as root instead of staying my user. MfG, MEX PS: How do I reactivate SELINUX after the test ? |
32) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18730 Posted 22 Jul 2008 by ![]() |
Maybe I have to use a empty password to solve my problem with the manager not connecting to the client automatically, like mentioned in your link ...Open the file up in gedit. Hightlight whatever is in there and delete it. Then hit enter once and save the file. Many thanks for the help :D ... but I have found the source of the problem why my manager wasn't able to connect to the client: Now it isn't necessary anymore to compromise my security by using NL as a password, which wouldn't have helped me anyway ... I did "link /var/lib/boinc/gui_rpc_auth.cfg $HOME/gui_rpc_auth.cfg" after performing su, and created a link to /root/gui_rpc_auth.cfg instead of /home/mex/gui_rpc_auth.cfg (silly me, I should have checked this much earlier :rollingeyes:) This only leaves the problem that the client started as a daemon at boot isnt able to connect to the www unless i restart it as root. MfG, MEX PS: It is annoying, but no critical fault, that I have to restart the client as root manually ... and maybe I did something wrong myself when installing boinc or f9 which now causes this strange behavior :rollingeyes: |
33) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18726 Posted 22 Jul 2008 by ![]() |
I just found the link to this page in my bookmarks... http://fedoraproject.org/wiki/User:Mjakubicek/HowToUseBoinc. See the Discussion link there.Maybe I have to use a empty password to solve my problem with the manager not connecting to the client automatically, like mentioned in your link ... HOW do I paste only a NEWLINE into gui_rpc_auth.cfg with gedit, or should i use another editor ( which would require which commands) ?If you want to set an empty password for BOINC, just paste only a newline into /var/lib/boinc/gui_rpc_auth.cfg MfG, MEX |
34) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18725 Posted 22 Jul 2008 by ![]() |
Note, you need to create an account (which is kinda hard to find).What type of account are you talking about ? ... A BOINC account ? ... the account boinc in f9? ... my useraccount which I have added to the group boinc in f9 ? ... I am participating in SETI@home since the last century, and have used a linux client without problems for the CLASSIC application years ago. After installing f9 on my FSC ESPRIMO Mobile V5535, as I wasn't satisfied with the support of Ubuntu for my PS3 because I want to use the same distribution on both computers with BOINC, I installed BOINC with "yum install boinc-client boinc-manager" as mentioned in http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up and changed the GUI RPC password to something shorter and easier to remember. I also created a link to /var/lib/boinc/gui_rpc_auth.cfg in my home directory and added my username to the boinc group. Until now I didn't modify the SELinux settings to give users in the boinc group access to port 31416 (as I don't know how to do this), or anything else. My current status with BOINC and f9 on my V5535 is that I still have to connect the manager manually to localhost in its Extras, and that the client isn't able to connect to the www: Die 22 Jul 2008 11:50:27 CEST||Starting BOINC client version 5.10.45 for i686-pc-linux-gnu Die 22 Jul 2008 11:50:27 CEST||log flags: task, file_xfer, sched_ops Die 22 Jul 2008 11:50:27 CEST||Libraries: libcurl/7.18.2 NSS/3.12.0.3 zlib/1.2.3 libidn/0.6.14 Die 22 Jul 2008 11:50:27 CEST||Executing as a daemon Die 22 Jul 2008 11:50:27 CEST||Data directory: /var/lib/boinc Die 22 Jul 2008 11:50:27 CEST||Processor: 1 GenuineIntel Intel(R) Celeron(R) CPU 540 @ 1.86GHz [Family 6 Model 22 Stepping 1] Die 22 Jul 2008 11:50:27 CEST||Processor features: fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts pni monitor ds_cpl tm2 ssse3 cx16 xtpr lahf_lm Die 22 Jul 2008 11:50:27 CEST||OS: Linux: 2.6.25.10-86.fc9.i686 Die 22 Jul 2008 11:50:27 CEST||Memory: 2.71 GB physical, 3.99 GB virtual Die 22 Jul 2008 11:50:27 CEST||Disk: 62.98 GB total, 56.37 GB free Die 22 Jul 2008 11:50:27 CEST||Local time is UTC +2 hours Die 22 Jul 2008 11:50:27 CEST|Einstein@Home|URL: http://einstein.phys.uwm.edu/; Computer ID: 1482516; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST|SHA-1 Collision Search Graz|URL: http://boinc.iaik.tugraz.at/sha1_coll_search/; Computer ID: 31994; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST|Rectilinear Crossing Numbers|URL: http://dist.ist.tugraz.at/cape5/; Computer ID: 39216; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST|lhcathome|URL: http://lhcathome.cern.ch/lhcathome/; Computer ID: 9703324; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST|orbit@home|URL: http://orbit.psi.edu/oah/; Computer ID: 8705; location: (none); project prefs: default Die 22 Jul 2008 11:50:27 CEST|SETI@home Beta Test|URL: http://setiweb.ssl.berkeley.edu/beta/; Computer ID: 29977; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 4482760; location: home; project prefs: default Die 22 Jul 2008 11:50:27 CEST||General prefs: from orbit@home (last modified 27-Jun-2008 14:48:32) Die 22 Jul 2008 11:50:27 CEST||Host location: none Die 22 Jul 2008 11:50:27 CEST||General prefs: using your defaults Die 22 Jul 2008 11:50:27 CEST||Preferences limit memory usage when active to 1388.09MB Die 22 Jul 2008 11:50:27 CEST||Preferences limit memory usage when idle to 2498.56MB Die 22 Jul 2008 11:50:27 CEST||Preferences limit disk usage to 1.86GB Die 22 Jul 2008 11:50:27 CEST||Running CPU benchmarks Die 22 Jul 2008 11:50:58 CEST||Benchmark results: Die 22 Jul 2008 11:50:58 CEST|| Number of CPUs: 1 Die 22 Jul 2008 11:50:58 CEST|| 1109 floating point MIPS (Whetstone) per CPU Die 22 Jul 2008 11:50:58 CEST|| 4371 integer MIPS (Dhrystone) per CPU Die 22 Jul 2008 11:50:59 CEST|SETI@home Beta Test|Restarting task ap_23ap08ab_B1_P0_00015_20080715_06439.wu_1 using astropulse version 434 Die 22 Jul 2008 11:51:00 CEST|lhcathome|Sending scheduler request: To fetch work. Requesting 1324 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 11:51:01 CEST||Project communication failed: attempting access to reference site Die 22 Jul 2008 11:51:02 CEST||Access to reference site failed - check network connection or proxy configuration. Die 22 Jul 2008 11:51:05 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 11:51:10 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 651 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 11:51:16 CEST|orbit@home|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 11:52:11 CEST|lhcathome|Sending scheduler request: To fetch work. Requesting 1324 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 11:52:16 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 11:53:52 CEST|lhcathome|Sending scheduler request: To fetch work. Requesting 1323 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 11:53:57 CEST|lhcathome|Scheduler request failed: Couldn't resolve host name Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Finished download of icon_krypto_01.png Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Finished download of show_01_01.png Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Started download of show_02_01.png Die 22 Jul 2008 12:23:12 CEST|SHA-1 Collision Search Graz|Started download of show_03_01.png Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Finished download of show_02_01.png Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Finished download of show_03_01.png Die 22 Jul 2008 12:23:13 CEST|SHA-1 Collision Search Graz|Started download of show_04_01.png Die 22 Jul 2008 12:23:14 CEST|SHA-1 Collision Search Graz|Finished download of show_04_01.png Die 22 Jul 2008 12:23:18 CEST|SHA-1 Collision Search Graz|Sending scheduler request: To fetch work. Requesting 44 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 12:23:19 CEST|SHA-1 Collision Search Graz|Starting wu_sha1collisionsearchgraz_v55_1216702853_958_0 Die 22 Jul 2008 12:23:19 CEST|SHA-1 Collision Search Graz|Starting task wu_sha1collisionsearchgraz_v55_1216702853_958_0 using sha1_collisionsearch_graz version 535 Die 22 Jul 2008 12:23:23 CEST|SHA-1 Collision Search Graz|Scheduler request succeeded: got 1 new tasks Die 22 Jul 2008 12:23:25 CEST|SHA-1 Collision Search Graz|Started download of wu_sha1collisionsearchgraz_v55_1216702853_1258 Die 22 Jul 2008 12:23:26 CEST|SHA-1 Collision Search Graz|Finished download of wu_sha1collisionsearchgraz_v55_1216702853_1258 Die 22 Jul 2008 12:25:50 CEST|orbit@home|Sending scheduler request: To fetch work. Requesting 651 seconds of work, reporting 0 completed tasks Die 22 Jul 2008 12:26:01 CEST|orbit@home|Scheduler request succeeded: got 0 new tasks until I restart the client as root: [mex@localhost ~]$ /sbin/service boinc-client restart rm: Entfernen von „/var/lib/boinc/lockfile“ nicht möglich: Keine Berechtigung rm: Entfernen von „/var/lock/subsys/boinc-client“ nicht möglich: Keine Berechtigung Starting BOINC client as a daemon: /etc/init.d/boinc-client: line 165: /var/log/boincerr.log: Keine Berechtigung touch: kann „/var/lock/subsys/boinc-client“ nicht berühren: Keine Berechtigung [FEHLGESCHLAGEN] [mex@localhost ~]$ su Passwort: [root@localhost mex]# ps aux | grep boinc boinc 1982 0.1 0.1 10796 3096 ? SNs 11:50 0:02 /usr/bin/boinc_client --daemon boinc 2225 89.7 1.7 50584 48356 ? RNl 11:50 24:29 astropulse_4.34_i686-pc-linux-gnu mex 2488 0.9 0.7 58440 22420 ? S 11:51 0:15 boincmgr root 2627 0.0 0.0 5068 784 pts/1 S+ 12:18 0:00 grep boinc [root@localhost mex]# /sbin/service boinc-client restart Stopping BOINC client daemon: [ OK ] Starting BOINC client as a daemon: [ OK ] [root@localhost mex]# ps aux | grep boinc mex 2488 0.9 0.7 58444 22428 ? S 11:51 0:16 boincmgr boinc 2668 0.1 0.1 10692 2864 ? SNs 12:19 0:00 /usr/bin/boinc_client --daemon boinc 2669 107 1.6 50304 46700 ? RNl 12:19 0:06 astropulse_4.34_i686-pc-linux-gnu root 2674 0.0 0.0 5064 768 pts/1 R+ 12:19 0:00 grep boinc [root@localhost mex]# MfG, MEX |
35) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18708 Posted 21 Jul 2008 by ![]() |
Upstart Init Daemon Maybe the new UPSTART is causing my problems with boinc_client started at boot beeing unable to connect to the www ... unless I restart boinc_client as root :( Can someone please check if the init scripts of boinc_client for F9 are compatible to Upstart ? MfG, MEX PS: Maybe boinc_client is started too early at boot, and remembers that it cant connect to the www unless it is restarted ... |
36) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18619 Posted 18 Jul 2008 by ![]() |
Also, you may have to modify the SELinux settings (if you're using SELinux) to give users in the boinc group access to port 31416. In the wiki I read "Enter chmod g+r /var/lib/boinc/gui_rpc_auth.cfg (change the permissions on /var/lib/boinc/gui_rpc_auth.cfg to allow group read)" Can it be that I have to do a chmod g+w to /var/lib/boinc or some of the files in this directory to solve my problem, like mentioned in http://lledgerock.com/boinc_logs/%23boinc.2008-06-20.log.html ? [mex@localhost lib]$ ls boinc -als insgesamt 1000 4 drwxr-xr-x 4 boinc boinc 4096 18. Jul 21:19 . 4 drwxr-xr-x 34 root root 4096 14. Jul 16:02 .. 4 -rw-r--r-- 1 boinc boinc 431 17. Jul 21:02 account_boinc.iaik.tugraz.at_sha1_coll_search.xml 4 -rw-r--r-- 1 boinc boinc 376 17. Jul 21:04 account_dist.ist.tugraz.at_cape5.xml 4 -rw-r--r-- 1 boinc boinc 3386 17. Jul 21:00 account_einstein.phys.uwm.edu.xml 4 -rw-r--r-- 1 boinc boinc 360 17. Jul 21:00 account_lhcathome.cern.ch_lhcathome.xml 4 -rw-r--r-- 1 boinc boinc 441 17. Jul 21:00 account_orbit.psi.edu_oah.xml 4 -rw-r--r-- 1 boinc boinc 2794 17. Jul 21:01 account_setiathome.berkeley.edu.xml 4 -rw-r--r-- 1 boinc boinc 371 16. Jul 15:48 account_setiweb.ssl.berkeley.edu_beta.xml 20 -rw-r--r-- 1 boinc boinc 16761 16. Jul 14:12 all_projects_list.xml 72 -rw-r--r-- 1 boinc boinc 65602 18. Jul 21:19 client_state_prev.xml 72 -rw-r--r-- 1 boinc boinc 65602 18. Jul 21:19 client_state.xml 8 -rw-r--r-- 1 boinc boinc 5141 16. Jul 15:13 get_current_version.xml 4 -rw-r--r-- 1 boinc boinc 181 16. Jul 15:54 get_project_config.xml 4 -rw-r--r-- 1 boinc boinc 992 16. Jul 15:13 global_prefs.xml 4 -rw-r----- 2 boinc boinc 9 16. Jul 14:58 gui_rpc_auth.cfg 4 -rw-r----- 1 root root 12 16. Jul 14:58 gui_rpc_auth.cfg~ ... MfG, MEX PS: Found a explanation for port 31416 in http://setiathome.berkeley.edu/forum_thread.php?id=17525&nowrap=true#147111 and http://www.archivum.info/debian-bugs-closed@lists.debian.org/2007-04/msg03584.html Which still leaves the question HOW do i give boinc access to port 31416 to solve my problem with SELinux ? |
37) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18617 Posted 18 Jul 2008 by ![]() |
I added my username to the boinc group correct in the first try (I am not THAT stupid :rolleyes: ).How can i give the client the right to connect to the www, even if nobodfy is logged on ? But I assume that I made a fault with the link, how can I check that the link is correct ( maybe he points to a old version of the file as I used gedit to change the password later ) ? The hint with SElinux has a high propability to solve my problem, isn't SElinux new to Fedora since release 9 ? ( that might be the reason that I am the first who complains about this ) How do i give the boinc group access to port 31416 ? What is this port used for ? MfG, MEX PS: I have edited http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_up to add your hint, and moved the start of the client BEFORE editing the GUI RPC password. |
38) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18613 Posted 18 Jul 2008 by ![]() |
I did create a symlink, but obviously something didnt work as it should :( which surley is my fault ;)1. manager cant connect to the client unless I go to EXTRAS and connect manually to localhost AND enter the password ( this is annoying but not a big problem )Your 1 will happen unless you create that symlink. How can i view this init.d script from the clients RPM ? I asume that the clients RPM isnt a "real" RPM, but only copies the clients files into the right place and that the maintainer thought that everyone is linux-literate enough to do the rest himself :( MfG, MEX PS: I try to repair the faulty installation of the clients RPM, so that i can use yum for updating later. Because of this i still have the problem: How can i give the client the right to connect to the www, even if nobodfy is logged on ? Into which groups do have to add the user boinc ? |
39) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18592 Posted 17 Jul 2008 by ![]() |
MEX wrote:Maybe I am just too stupid :rollingeyes:As not even a BOINC group exists, I assume that the installation of the client didn't work, although yum had told me that it had done everything :( ... but now I have 2 more problems: 1. manager cant connect to the client unless I go to EXTRAS and connect manually to localhost AND enter the password ( this is annoying but not a big problem ) 2. client cant connect to the internet, unless I restart it as su with root rights ! This is a BIG problem as I want to start it at boot so that it is running whenever my computer is running F9. Obviously the client started at boot isn't allowed to connect to the internet. How can I give the client the necessary rights ? MfG, MEX PS: I didn't see the boinc group as I was filtering system users & groups ... as soon as I removed the hook to filter these, a lot of groups and users showed up, including boinc ( although I am no new Linux user, it is several years since I had to administrate a Linux ) |
40) Message boards : BOINC client : HOW TO install BOINC with Fedora 9 ?
Message 18524 Posted 16 Jul 2008 by ![]() |
http://boinc.berkeley.edu/wiki/Installing_on_Linux#Fedora_7_and_upIt seems that the order in which to do the steps mentioned in the link above isnt correct. I first had to start the client as root before being able to change the GUI RPC password: [mex@localhost ~]$ su Passwort: [root@localhost mex]# /sbin/service boinc-client start The BOINC client requires initialization (no projects attac[WARNUNG] Starting BOINC client as a daemon: [ OK ] [root@localhost mex]#After stopping the boinc-client, i was able to change the GUI RPC password and add the user mex to the group boinc with "gedit /etc/group" and did the other steps which shold allow me to connect to "localhost" without having to use a password. But now i get the following message when i try to connect the manager to the client: [b]BOINC Manager - Verbindungsfehler[/b] Das eingegebene Passwort ist falsch. Bitte erneut versuchen. MfG, MEX PS: Suddenly, after switching to "English U.S." as language for the manager, and restarting the manager, i was able to connect to the client and download a WU for SETI@home : http://setiathome.berkeley.edu/result.php?resultid=919440442 |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.