I started running boinc client 4.43 yesterday on a dual processor 550MHz Pentium 3 system running Red Hat Linux 9. It ran for quite a while, but then did this:

2005-06-09 00:19:48 [climateprediction.net] Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed
2005-06-09 00:19:48 [climateprediction.net] No schedulers responded
2005-06-09 00:19:48 [climateprediction.net] Deferring communication with project for 59 seconds
2005-06-09 00:20:52 [climateprediction.net] Master file fetch failed
2005-06-09 00:20:52 [climateprediction.net] Deferring communication with project for 59 seconds
2005-06-09 01:05:08 [SETI@home] Deferring communication with project for 4 hours, 27 minutes, and 29 seconds
2005-06-09 02:05:08 [SETI@home] Deferring communication with project for 3 hours, 27 minutes, and 29 seconds
2005-06-09 03:05:09 [SETI@home] Deferring communication with project for 2 hours, 27 minutes, and 29 seconds
2005-06-09 04:05:09 [SETI@home] Deferring communication with project for 1 hours, 27 minutes, and 28 seconds
2005-06-09 05:05:10 [SETI@home] Deferring communication with project for 27 minutes and 27 seconds
2005-06-09 05:32:48 [---] Can't resolve hostname [setiathome.berkeley.edu] host not found or server failure
2005-06-09 05:32:48 [SETI@home] Couldn't read master page for SETI@home: error -113
2005-06-09 05:32:48 [SETI@home] Master file fetch failed
2005-06-09 05:32:48 [SETI@home] Deferring communication with project for 17 hours, 15 minutes, and 35 seconds
SIGSEGV: segmentation violationStack trace (8 frames):
/boinc/BOINC/boinc[0x807e54e]
/lib/tls/libpthread.so.0[0x400508f8]
/boinc/BOINC/boinc[0x8072f43]
/boinc/BOINC/boinc[0x80535b4]
/boinc/BOINC/boinc[0x80725ab]
/boinc/BOINC/boinc[0x80726a8]
/lib/tls/libc.so.6(__libc_start_main+0xe4)[0x42015704]
/boinc/BOINC/boinc[0x804ae91]

Exiting...


I suppose this is not how it is supposed to run.

---

It just did it again.

2005-06-12 06:51:32 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-06-12 06:51:32 [SETI@home] No schedulers responded
2005-06-12 06:51:32 [SETI@home] Deferring communication with project for 1 hours, 20 minutes, and 35 seconds
2005-06-12 07:10:39 [---] Can't resolve hostname [predictor.scripps.edu] host not found or server failure
2005-06-12 07:10:39 [ProteinPredictorAtHome] scheduler init_op_project to http://predictor.scripps.edu/predictor_cgi/cgi failed, error -113
2005-06-12 07:10:39 [ProteinPredictorAtHome] init_op_project failed, error -113
2005-06-12 07:10:39 [ProteinPredictorAtHome] Deferring communication with project for 2 hours, 36 minutes, and 23 seconds
SIGSEGV: segmentation violationStack trace (8 frames):
/boinc/BOINC/boinc[0x807e54e]
/lib/tls/libpthread.so.0[0xa7be48]
/boinc/BOINC/boinc[0x8072f43]
/boinc/BOINC/boinc[0x80535b4]
/boinc/BOINC/boinc[0x80725ab]
/boinc/BOINC/boinc[0x80726a8]
/lib/tls/libc.so.6(__libc_start_main+0xda)[0x14278a]
/boinc/BOINC/boinc[0x804ae91]

Exiting...

---

It just did it again.

2005-06-12 06:51:32 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
2005-06-12 06:51:32 [SETI@home] No schedulers responded
2005-06-12 06:51:32 [SETI@home] Deferring communication with project for 1 hours, 20 minutes, and 35 seconds
2005-06-12 07:10:39 [---] Can't resolve hostname [predictor.scripps.edu] host not found or server failure
2005-06-12 07:10:39 [ProteinPredictorAtHome] scheduler init_op_project to http://predictor.scripps.edu/predictor_cgi/cgi failed, error -113
2005-06-12 07:10:39 [ProteinPredictorAtHome] init_op_project failed, error -113
2005-06-12 07:10:39 [ProteinPredictorAtHome] Deferring communication with project for 2 hours, 36 minutes, and 23 seconds
SIGSEGV: segmentation violationStack trace (8 frames):
/boinc/BOINC/boinc[0x807e54e]
/lib/tls/libpthread.so.0[0xa7be48]
/boinc/BOINC/boinc[0x8072f43]
/boinc/BOINC/boinc[0x80535b4]
/boinc/BOINC/boinc[0x80725ab]
/boinc/BOINC/boinc[0x80726a8]
/lib/tls/libc.so.6(__libc_start_main+0xda)[0x14278a]
/boinc/BOINC/boinc[0x804ae91]

Exiting...

It is still at it; this time on my main machine that is a dual processor Intel 3.06GHz Xeon processor with 4096 MBytes RAM running Red Hat Enterprise Linux 3. I have run memtest86 v3.0 on this machine for 9 hours (a little over 7 passes) with no error, and mprime -t for over 15 hours with no errors, so I doubt it is a hardware problem. Were it a hardware problem, I would expect different failure modes on different processors. Each of these machines is powered through a separate APC Smart-UPS uninterruptable power supply that includes considerable surge protection.

2005-06-16 06:31:52 [ProteinPredictorAtHome] scheduler init_op_project to http://predictor.scripps.edu/predictor_cgi/cgi failed, error -113
2005-06-16 06:31:52 [ProteinPredictorAtHome] init_op_project failed, error -113
2005-06-16 06:31:52 [ProteinPredictorAtHome] Deferring communication with project for 39 minutes and 53 seconds
SIGSEGV: segmentation violationStack trace (8 frames):
/boinc/BOINC/boinc[0x807e54e]
/lib/tls/libpthread.so.0[0x2e3e48]
/boinc/BOINC/boinc[0x8072f43]
/boinc/BOINC/boinc[0x80535b4]
/boinc/BOINC/boinc[0x80725ab]
/boinc/BOINC/boinc[0x80726a8]
/lib/tls/libc.so.6(__libc_start_main+0xda)[0x99e78a]
/boinc/BOINC/boinc[0x804ae91]

Exiting...

---