BOINC and SETI@Home at Raspberry Pi 3B recent problems

Author	Message
Skalgrin Send message Joined: 3 Mar 18 Posts: 2 Credit: 17,998 RAC: 0	Message 1959468 - Posted: 10 Oct 2018, 6:23:11 UTC I have an issue ony my Raspberry Pi 3B with up to date raspbian. I run BOINC and SETI@Home at it since March '18 without issues until 27th of September. On that day I had "Error while downloading" and ever since I either have "error while computing" or "error while downloading" and strangely "completed and marked as invalid" - which gives me credit though. I have performed restart (RPi normaly runs 24/7) - same result. Other "background" processes which runs on RPi (e.g. Pi-Hole) runs without issues and I succesfuly use the Raspbian environment and KODI on it without any recorded issues. What could be wrong? What can I do about that? As if this would be ongoing I would rather shut the BOINC down to not waste time of others (as all invalid results require revalidation) and the "effort" put into this goes wasted. ID: 1959468 ·

Kissagogo27 Send message Joined: 6 Nov 99 Posts: 716 Credit: 8,032,827 RAC: 62	Message 1959485 - Posted: 10 Oct 2018, 9:09:37 UTC Last modified: 10 Oct 2018, 9:10:25 UTC when i take a look at Sterr result, i can notice some restarted task even with good results ... <core_client_version>7.6.33</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work setiathome_v8 8.00 $Revision: 1146 $ g++ (Raspbian 5.4.0-4) 5.4.0 20160609 libboinc: BOINC 7.6.33 Work Unit Info: ............... WU true angle range is : 0.012974 features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 Optimal function choices: -------------------------------------------------------- name timing error -------------------------------------------------------- v_BaseLineSmooth (no other) vfp_GetPowerSpectrum 0.005209 0.00000 fpu_opt_ChirpData 0.359231 0.00000 fftwf_transpose 0.154821 0.00000 FPU opt folding 0.088403 0.00000 Spike: peak=31.66306, time=34.43, d_freq=8518753031.6, chirp=9.8014, fft_len=32 Spike: peak=31.67129, time=34.43, d_freq=8518753071.91, chirp=-9.8014, fft_len=32 boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 10.48 percent. Triplet: peak=13.7964, time=77.76, period=10.89, d_freq=8518752373.11, chirp=-11.027, fft_len=512 Triplet: peak=15.07464, time=77.76, period=10.89, d_freq=8518752371.68, chirp=-11.333, fft_len=512 Spike: peak=28.7598, time=34.43, d_freq=8518753115.99, chirp=12.252, fft_len=32 Pulse: peak=16.59099, time=45.82, period=20.73, d_freq=8518747533.43, score=1.942, chirp=12.252, fft_len=64 Spike: peak=28.73582, time=34.43, d_freq=8518752987.52, chirp=-12.252, fft_len=32 Triplet: peak=12.69047, time=26.89, period=9.149, d_freq=8518749316.62, chirp=-12.558, fft_len=512 boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 13.28 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 13.52 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 13.53 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 16.73 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 16.91 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 17.00 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 17.26 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 17.36 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 18.72 percent. boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 18.72 percent. Triplet: peak=10.31864, time=51.72, period=18.97, d_freq=8518748474.45, chirp=18.839, fft_len=4k Spike: peak=30.68042, time=34.43, d_freq=8518753011.49, chirp=19.604, fft_len=32 Spike: peak=30.69639, time=34.43, d_freq=8518753092.03, chirp=-19.604, fft_len=32 boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 20.68 percent. Spike: peak=24.52746, time=5.727, d_freq=8518747889.86, chirp=19.859, fft_len=128k Spike: peak=25.33526, time=5.727, d_freq=8518747889.87, chirp=19.86, fft_len=128k Spike: peak=24.94698, time=5.727, d_freq=8518747889.88, chirp=19.862, fft_len=128k boinc-app-seti is invoked with the following arguments: --start --end. I: boinc_parse_init_data_file I: boinc_get_init_data I: boinc_init I: worker I: worker() - common_init I: worker() - read_wu_state I: worker() - seti_do_work Restarted at 20.91 percent. Triplet: peak=11.11332, time=20.71, period=17.36, d_freq=8518750872.9, chirp=20.523, fft_len=1024 </stderr_txt> ]]> any idea why ? ID: 1959485 ·

Jord Volunteer tester Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3	Message 1959520 - Posted: 10 Oct 2018, 14:16:22 UTC - in response to Message 1959468. You have two errors. "process got signal 11" and "process exited with code 193". Both are segmentation violation errors, or memory errors. Part of your Raspbi's memory is broken, which also accounts for some tasks ending fine, others with validation errors and the rest as plain error. ID: 1959520 ·

Skalgrin Send message Joined: 3 Mar 18 Posts: 2 Credit: 17,998 RAC: 0	Message 1959842 - Posted: 12 Oct 2018, 6:53:49 UTC OP updated : I was working from home yesterday and during that time I watched closely my RPi - the issue is actualy very simple in my case. As in my country heating season started - the humidity, temperature and "dustiness" of air in our home changed and RPi under prolonged load started to overheat. But during my "home PC time" - which is evening and early night it was just below the treshold. However it peakes in my "work-hours" (when I am normaly in my office) as my wife who is home with our little ones cooks and bakes in room next to the one where RPi is, and we have no doors in between. I have been reluctant to make active cooling and passive cannot handle 24/7 load through boinc in the "new" envirornment. The result was RPi A) was all the time throttling down B) occasionaly freezing - which indeed had... not good effect on running processes. Therefore I suspended BOINC until I manage to build active cooling. However I posted it here as it might help other with similar(-ish) issue. ID: 1959842 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.