Page 2 of 5
Re: psummary upgrade
Posted: Wed Dec 16, 2009 9:23 pm
by jcoffland
I'm not sure yet but I think at least some of the missing projects are due to two things. One, I believe I cleaned out the psummary source files that are created by the assignment servers at one point. Two, one of the assignment servers is not and has not been updating it's psummary file for some time. So basically I believe the projects that dropped off were in a stale psummary file that I removed and it's not getting updated like it should.
I'll get it worked out.
Re: psummary upgrade
Posted: Thu Dec 17, 2009 12:02 am
by MtM
Question, I just noticed a post where fahspy monitoring is no longer working, did you finish changing the layout and should people now all update their respective monitoring applications ( granted that would only help if smokey here and the others update their applications ).
Re: psummary upgrade
Posted: Thu Dec 17, 2009 3:33 am
by jcoffland
I did finish the layout. Since it is now proper XHTML they can use an XML parser and then shouldn't have parsing problems if we change the content in the future.
I recommend they use the expat library:
http://expat.sourceforge.net/
It is a free, platform independent and Open-Source as well as commercial friendly SAX library in C.
Of course if the program is Python, Java or C# then there are built in XML parsers.
Re: psummary upgrade
Posted: Thu Dec 17, 2009 4:26 am
by anandhanju
The GRO-PS3 projects appear to be classified as GROMACS in the new psummary page.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 3:15 am
by jcoffland
anandhanju wrote:The GRO-PS3 projects appear to be classified as GROMACS in the new psummary page.
There is no mention of GRO-PS3 in the old psummary code.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 3:15 am
by jcoffland
missing projects should be coming back
Re: psummary upgrade
Posted: Fri Dec 18, 2009 3:21 am
by jcoffland
bollix47 wrote:Projects 2681 thru 2683 are no longer listed. This would cause problems with 3rd party monitoring for anyone running the bigadv clients if they update their psummary.
These projects don't seem to be up. Keep in mind psummary only displays active projects. I.e. those the assignment server can contact.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 3:28 am
by bollix47
jcoffland wrote:bollix47 wrote:Projects 2681 thru 2683 are no longer listed. This would cause problems with 3rd party monitoring for anyone running the bigadv clients if they update their psummary.
These projects don't seem to be up. Keep in mind psummary only displays active projects. I.e. those the assignment server can contact.
These projects have been active for months now and are currently being assigned to server 171.67.108.22. They were on psummary before you made your changes. I'm currently crunching 4 of them. They are commonly referred to as bigadv WUs.
Here's an example of one that's currently running:
Code: Select all
[14:11:24] + Attempting to get work packet
[14:11:24] - Will indicate memory of 5966 MB
[14:11:24] - Connecting to assignment server
[14:11:24] Connecting to http://assign.stanford.edu:8080/
[14:11:24] Posted data.
[14:11:24] Initial: 43AB; - Successful: assigned to (171.67.108.22).
[14:11:24] + News From Folding@Home: Welcome to Folding@Home
[14:11:24] Loaded queue successfully.
[14:11:24] Connecting to http://171.67.108.22:8080/
[14:12:03] Posted data.
[14:12:03] Initial: 0000; - Receiving payload (expected size: 30236150)
[14:12:28] - Downloaded at ~1181 kB/s
[14:12:28] - Averaged speed for that direction ~975 kB/s
[14:12:28] + Received work.
[14:12:33] Project: 2683 (Run 5, Clone 0, Gen 26)
If I remember correctly the CONTACT said kasson.
Hope this helps you track down the problem.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 3:59 am
by ChelseaOilman
jcoffland wrote:anandhanju wrote:The GRO-PS3 projects appear to be classified as GROMACS in the new psummary page.
There is no mention of GRO-PS3 in the old psummary code.
I can confirm that all the WUs that were assigned to PS3 consoles were labeled as GRO-PS3 on the old psummary page. It made it a lot easier to tell which WUs were PS3 only.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 4:42 am
by anandhanju
I can also confirm this. I had a Greasemonkey script that showed only classic projects (which now also shows PS3 projects due to this change.)
Re: psummary upgrade
Posted: Fri Dec 18, 2009 5:47 am
by smoking2000
From my psummary parser logs from the past few hours:
Projects missing contact person:
Code: Select all
Warning: Cannot parse project line (72):
<tr bgcolor="#dfdfdf"> <td>3023</td><td>171.64.65.56</td><td>p3023_SMP-water-box</td><td>9642</td><td>1.50</td><td>2.50</td><td>587.00</td><td>100</td><td>GRO-SMP</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3023">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Updated project: 3024 Status active: false -> true
Warning: Cannot parse project line (74):
<tr bgcolor="#dfdfdf"> <td>3025</td><td>171.64.65.56</td><td>p3025_SMP-nsv-03</td><td>9684</td><td>1.50</td><td>2.50</td><td>587.00</td><td>100</td><td>GRO-SMP</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3025">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (75):
<tr bgcolor="#ffffff"> <td>3027</td><td>171.64.65.56</td><td>p3027_SMP-nsv-03</td><td>9684</td><td>1.50</td><td>2.50</td><td>716.00</td><td>100</td><td>GRO-SMP</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3027">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (119):
<tr bgcolor="#ffffff"> <td>3500</td><td>171.64.65.111</td><td>p3500_supervillin-03</td><td>9684</td><td>36.00</td><td>53.00</td><td>188.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3500">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (120):
<tr bgcolor="#dfdfdf"> <td>3501</td><td>171.64.65.111</td><td>p3501_supervillin_03</td><td>9684</td><td>36.00</td><td>53.00</td><td>188.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3501">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (121):
<tr bgcolor="#ffffff"> <td>3502</td><td>171.64.65.111</td><td>p3502_supervillin-03</td><td>9684</td><td>35.00</td><td>52.00</td><td>183.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3502">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (122):
<tr bgcolor="#dfdfdf"> <td>3503</td><td>171.64.65.111</td><td>p3503_SMP-emsv-03</td><td>9684</td><td>35.00</td><td>52.00</td><td>183.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3503">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (123):
<tr bgcolor="#ffffff"> <td>3504</td><td>171.64.65.111</td><td>p3504_supervillin-03</td><td>9684</td><td>36.00</td><td>53.00</td><td>188.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3504">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (124):
<tr bgcolor="#dfdfdf"> <td>3505</td><td>171.64.65.111</td><td>p3505_p3501_supervillin_03</td><td>9684</td><td>36.00</td><td>53.00</td><td>188.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3505">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (125):
<tr bgcolor="#ffffff"> <td>3506</td><td>171.64.65.111</td><td>p3506_supervillin-03</td><td>9684</td><td>35.00</td><td>52.00</td><td>183.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3506">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Warning: Cannot parse project line (126):
<tr bgcolor="#dfdfdf"> <td>3507</td><td>171.64.65.111</td><td>p3507_SMP-emsv-03</td><td>9684</td><td>35.00</td><td>52.00</td><td>183.00</td><td>100</td><td>GROST</td><td><a href="http://fah-web.stanford.edu/cgi-bin/fahproject?p=3507">Description</a></td><td><font size="-1"></font></td><td>0.00</td></tr>
Code: Select all
Modified project: 2569 code: GRO-PS3 -> GROMACS
Modified project: 2570 code: GRO-PS3 -> GROMACS
Modified project: 3191 code: GRO-PS3 -> GROMACS
Modified project: 3192 code: GRO-PS3 -> GROMACS
Modified project: 3193 code: GRO-PS3 -> GROMACS
Modified project: 3194 code: GRO-PS3 -> GROMACS
Modified project: 3195 code: GRO-PS3 -> GROMACS
Modified project: 3196 code: GRO-PS3 -> GROMACS
Modified project: 3410 code: GRO-PS3 -> GROMACS
Modified project: 3412 code: GRO-PS3 -> GROMACS
Modified project: 3422 code: GRO-PS3 -> GROMACS
Modified project: 3423 code: GRO-PS3 -> GROMACS
Modified project: 3424 code: GRO-PS3 -> GROMACS
Modified project: 3425 code: GRO-PS3 -> GROMACS
Modified project: 3426 code: GRO-PS3 -> GROMACS
Modified project: 3445 code: GRO-PS3 -> GROMACS
Modified project: 3446 code: GRO-PS3 -> GROMACS
Modified project: 4001 code: GRO-PS3 -> GROMACS
Modified project: 4004 code: GRO-PS3 -> GROMACS
Modified project: 4005 code: GRO-PS3 -> GROMACS
Modified project: 4006 code: GRO-PS3 -> GROMACS
Modified project: 4007 code: GRO-PS3 -> GROMACS
Modified project: 4009 code: GRO-PS3 -> GROMACS
Modified project: 4011 code: GRO-PS3 -> GROMACS
Modified project: 4012 code: GRO-PS3 -> GROMACS
Modified project: 4013 code: GRO-PS3 -> GROMACS
Modified project: 4014 code: GRO-PS3 -> GROMACS
Modified project: 4022 server: 171.64.122.73 -> 171.64.65.96
name: p4022_supervillin_StillGBSA_AM03_mbondi2 -> p4022_p3127_hisvillin_e1
atoms: 576 -> 582
preferred: 2.00 -> 1.30
deadline: 6.00 -> 3.00
credit: 250.00 -> 287.00
code: GRO-PS3 -> GROMACS
Modified project: 4023 server: 171.64.122.73 -> 171.64.65.96
name: p4023_supervillin_StillGBSA_AM03_mbondi2 -> p4023_hisvillin_e1
atoms: 576 -> 582
code: GRO-PS3 -> GROMACS
Modified project: 5300 code: GRO-PS3 -> GROMACS
Modified project: 5301 code: GRO-PS3 -> GROMACS
Modified project: 5302 code: GRO-PS3 -> GROMACS
Modified project: 5303 code: GRO-PS3 -> GROMACS
Modified project: 5304 code: GRO-PS3 -> GROMACS
Modified project: 5305 code: GRO-PS3 -> GROMACS
Modified project: 5306 code: GRO-PS3 -> GROMACS
Modified project: 5307 code: GRO-PS3 -> GROMACS
Modified project: 5310 code: GRO-PS3 -> GROMACS
Modified project: 5311 server: 171.64.65.83 -> 171.64.65.73
credit: 110.00 -> 330.00
code: GRO-PS3 -> GROMACS
Modified project: 5311 server: 171.64.65.73 -> 171.64.65.83
credit: 330.00 -> 110.00
Modified project: 5312 code: GRO-PS3 -> GROMACS
If appreciated I can forward the full logs as this is just a subset of what was reported.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 7:08 am
by jcoffland
Other that missing a contact person I don't see what is wrong with those lines.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 7:42 am
by smoking2000
jcoffland wrote:Other that missing a contact person I don't see what is wrong with those lines.
For the unparsable lines, that is the only issue with those.
My parser is very strict because my earlier versions were to liberal and accepted invalid content from the psummary, so now I only accept what I know is correct.
There are currently also several projects with 0.00 credits: project 4038 to 4042
Re: psummary upgrade
Posted: Fri Dec 18, 2009 1:08 pm
by toTOW
jcoffland wrote:bollix47 wrote:Projects 2681 thru 2683 are no longer listed. This would cause problems with 3rd party monitoring for anyone running the bigadv clients if they update their psummary.
These projects don't seem to be up. Keep in mind psummary only displays active projects. I.e. those the assignment server can contact.
Are you sure that the atoms count doesn't trigger a bug ? These WUs have more than 1M atomsn and used to show nothing in the old psummary for the atoms count because of that.
Re: psummary upgrade
Posted: Fri Dec 18, 2009 1:30 pm
by Pette Broad
Noticed some duplicated entries in the Psummary page
P5311 is showing up twice ....171.64.65.73 300 credits
171.64.65.83 110 credits
2669 also duplicated...........171.67.108.24......GRO-SMP
171.64.65.56.......GROCVS
I've no idea if this is what's causing problems with FAHspy but p2611 is the only unit that's showing up correctly.
Pete