Message boards :
Number crunching :
Inconclusive WU , Wingman STDERR looks unusual ?
Message board moderation
Author | Message |
---|---|
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
http://setiathome.berkeley.edu/result.php?resultid=2847904671 This WU came up inconclusive , and I looked at it and noticed the wingmans task info looked unusual... stderr showed that the appinfo.xml for that computer seems to have some ( maybe ) errors in it ? http://setiathome.berkeley.edu/workunit.php?wuid=1175840368 |
arkayn Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0 |
|
Floyd Send message Joined: 19 May 11 Posts: 524 Credit: 1,870,625 RAC: 0 |
No app_info at all, that is a stock 64-bit Linux app on that machine. Ok , I just noticed the stderr showed some unusual context in it , sample below. <stderr_txt> Unrecognized XML in parse_init_data_file: hostid Skipping: 6882240 Skipping: /hostid Unrecognized XML in parse_init_data_file: starting_elapsed_time Skipping: 0.000000 Skipping: /starting_elapsed_time Unrecognized XML in parse_init_data_file: computation_deadline Skipping: 1365761700.136000 Skipping: /computation_deadline Unrecognized XML in GLOBAL_PREFS::parse_override: mod_time Skipping: /mod_time Unrecognized XML in GLOBAL_PREFS::parse_override: run_gpu_if_user_active Skipping: 0 Skipping: /run_gpu_if_user_active Unrecognized XML in GLOBAL_PREFS::parse_override: suspend_cpu_usage Skipping: 0.000000 Skipping: /suspend_cpu_usage Unrecognized XML in GLOBAL_PREFS::parse_override: max_ncpus_pct Skipping: 100.000000 Skipping: /max_ncpus_pct Unrecognized XML in parse_init_data_file: hosted ----------------------------------------------------- Not being a Linux user myself , I didn't realize that might be a normal thing for a Linux machine... Sorry for my mis-understanding of the stderr text file... I guess you never learn if you don't ask... |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
...and that stock 5.28 application is from October 2007, when the BOINC API was set to print out any unrecognized XML. The host is running BOINC 6.10.45 from April 2010, which puts additional information in the init_data.xml file which is not expected or needed by the application. No harm done, though it does look peculiar. Joe |
©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.