Hi, BoincSTAT doesn't work with the cp.net project. This is because the client_state.xml file seems to be malformed:

....


<file_info>
<name>hadsm3_4.02_i686-pc-linux-gnu</name>
<nbytes>1202259.000000</nbytes>
<max_nbytes>0.000000</max_nbytes>
<status>1</status>
<executable/>
<signature_required/>
<file_signature>
5711334c4eb0af326bc28cad76cdfa5c15480545d68c2311b4ff50c3efd0197b
e23f230212b7035533a7c0a7eebf373943564865a91193e8ac4490c2562b469d
b706ff027eca98016f6eaba45b1a1ea5528ea9847809528fda0fc0622ba42f54
a82209bc756caa8a19cf26a4fb771747b3c2ad1f2962eecd67cef49a85087a2b
.
</file_signature>
<url>http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/hadsm3_4.02_i686-pc-linux-gnu</url>
<signed_xml>
<name>hadsm3_4.02_i686-pc-linux-gnu</name>
<url>http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/hadsm3_4.02_i686-pc-linux-gnu</url>
<executable/>
<b>&lt;file_signature&gt;</b>
&lt;nbytes&gt;1202259.000000&lt;/nbytes&gt;
&lt;/signed_xml&gt;
&lt;/file_info&gt;


...

There is a second &lt;file_signature&gt; tag and it's not closed. Doesn't seem to affect boinc itself though.

nick

Actually, there's a second reason it doesn't work. It's looking for a state.sah in the slots/0/ dir. And it ain't there. Perhaps a seti specific file?

nick

yeah .sah sounds like a SETI-specific file. Plus, with CPDN/BOINC pretty much everything runs out of the project directory, with a subdirectory for a workunit name so that we can keep track &amp; keep an archive of the run (since the climate model uses hundreds of files, not just a single checkpoint file, etc)

what would be our "state" file is the workunitname.xml file that would be in our project dir.

I have a similar error here. boincstat worked fine for when I was running s@h under boinc 3.20.


More useful for debug is (boinc 4.02):

$ ./boincstat
/home/bgusr/.boinc/client_state.xml:130: parser error : Opening and ending tag mismatch: file_signature line 128 and signed_xml

^
/home/bgusr/.boinc/client_state.xml:131: parser error : Opening and ending tag mismatch: signed_xml line 124 and file_info

^
/home/bgusr/.boinc/client_state.xml:412: parser error : Opening and ending tag mismatch: file_info line 109 and client_state

^
/home/bgusr/.boinc/client_state.xml:413: parser error : Premature end of data in tag client_state line 1

^
Document not parsed successfully.


Looking up to line 131:
{app}
{name}hadsm3{/name}
{/app}
{file_info}
{name}hadsm3_4.02_i686-pc-linux-gnu{/name}
{nbytes}1202259.000000{/nbytes}
{max_nbytes}0.000000{/max_nbytes}
{status}1{/status}
{executable/}
{signature_required/}
{file_signature}
5711334c4eb0af326bc28cad76cdfa5c15480545d68c2311b4ff50c3efd0197b
e23f230212b7035533a7c0a7eebf373943564865a91193e8ac4490c2562b469d
b706ff027eca98016f6eaba45b1a1ea5528ea9847809528fda0fc0622ba42f54
a82209bc756caa8a19cf26a4fb771747b3c2ad1f2962eecd67cef49a85087a2b
.
{/file_signature}
{url}http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/hadsm3_4.02_i686-pc-linux-gnu{/url}
{signed_xml}
{name}hadsm3_4.02_i686-pc-linux-gnu{/name}
{url}http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/hadsm3_4.02_i686-pc-linux-gnu{/url}
{executable/}
{file_signature}
{nbytes}1202259.000000{/nbytes}
{/signed_xml}
{/file_info}

(OK, so how do you get tags _not_ to be interpreted by the message board?!)

And yep... The xml tags are not bracketing properly...

Is this a boinc 4.02 bug?
Also, why is 4.02 so much smaller than the previous 3.20 version?


(Meanwhile, the simulation is burning through phase 1)

Regards,
Martin

I've shown these odd mis-matched tags to David A. Hopefully it's nothing we introduced by generating workunits etc, I'm pretty sure we were just making "stock" stuff. I don't have my 3.20 stuff around so perhaps it was an oddity introduced, seems to be when the client gets and processes our file info. And since we're the only 4.x BOINC app that I know of nobody else has hit this yet?