Toon posts:

[Folding@Home] Announce: Client monitor voor Linux

Pagina: 1
Acties:
  • 7.063 views sinds 30-01-2008
  • Reageer

  • smoking2000
  • Registratie: september 2001
  • Laatst online: 18:26

smoking2000

DPC-Crew

dpkg-reconfigure reality

Topicstarter
SandStar schreef op woensdag 16 februari 2005 @ 18:47:
wil niet :'(

http://pr0ner.no-ip.org/folding/index.pl

als ik naar clients ga zie ik ten eerste niet waar ze mee bezig zijn en ten tweede als ik daar via een omweg wel ben zie ik alleen maar een opsomming van de files .xyz etc etc

wat doe ik verkeerd?
Je doet niets verkeerd, ik heb per ongeluk www/clients.plc overschreven met www/settings/clients.plc. http://images.fok.nl/s/bloos.gif
De clients.plc die er nu stond was dus die uit de configuratie interface, en niet de normale.

Ik heb het meteen gefixt: fci-0.5.2

| [Folding@Home] Announce: Client monitor voor Linux (fci) | fci-1.8.4 | Fatal Error Group |


  • smoking2000
  • Registratie: september 2001
  • Laatst online: 18:26

smoking2000

DPC-Crew

dpkg-reconfigure reality

Topicstarter
fci-1.6 released!

Het heeft teveel tijd gekost, maar hij is er dan eindelijk. Ook het schrijven van de release announcement heeft me teveel tijd gekost, dus hou ik het bij het posten van het origineel in het Engels:



New release of FCI: v1.6

It seems like forever since the last release (v1.5.1), but that was only a few months ago (v1.5.1 was released Wed Nov 18, 2009). It has been far too long since the last major release (v1.5 was released Wed Apr 15, 2009 9:13 pm). Approximately 9 months is not very good in the release early, release often department. You can have a baby in that time frame, although you may not want to release early and often in that case ;)

This release resembles the v1.3 release (Sat Mar 14, 2009) a bit, introducing some major new features. But this release took much longer to get done. At least I beat Duke Nukem Forever _O-

New Feature: FahChart-like TPF graphs for the current WU using jQuery Flot

This is the first feature of FCI that requires javascript. I've long sought for some way to integrated FahCharts features in FCI, it was a unique application that allowed you to inspect the TPF at each completed step in the graph. Now you can do this in FCI too thanks to the wonderful jQuery Flot plotting library, you can even click through to the line in the FAHlog on which the step in question was completed (good for inspecting peaks). 8-)

Example:


These TPF graphs are displayed on the client page, and on the project page if the trajectory a client is working on is selected.

New Feature: Trajectory tracking for projects

Next to the individual projects, each trajectory for a project is now also tracked in the expanded known-projects. Each project now has its own known-project XML file in which the general project information is stored, just like it is in the known-projects XML file listing all known-projects. But the project specific known-project XML file also stores a list of trajectories the FCI clients have worked on. If a current.xyz file is availble the project images will be stored per trajectory as well.

A project page for which the trajectory is specified (by clicking a trajectory link) will now highlight the client running the trajectory, and the TPF graph if available.

(click for full size 774x1033)

This feature is not fully implemented yet, because the TPF data for the trajectory is not stored for completed WUs, only for the currently active WUs. This will be addressed in a future release of FCI, where a client list will also be shown for completed WUs.

New Feature: Queue History RRD graphs

RRD graphs are now also generated for the following queue values:
- Current PPD
- Speed
- Progress (%)
- Flops
- Performance Fraction
- Average PPD

All values are for the current work unit, except the Performance Fraction and Average PPD, these are queue averages of multiple WUs.

New Feature: FCI server support on OpenSUSE

With the release of OpenSUSE 11.2 it's now possible to get all FCI servers dependencies installed, so I got to update the supported OSes in the start post. :)
In previous releases everything except libapreq2 was available, a working build is now available thanks to the openSUSE Build Service.

Improved Functionality: Slightly more intelligent FCI client

The FCI client now knows about a few known issues and how to handle them a bit more intelligently. It will no longer upload the current.xyz if it likely doesn't belong the work unit the FAH client is currently work on. This can happen with some SMP cores which no longer generate the current.xyz, but this is also one of the files the FahCores don't clean up (all the time). So if the current.xyz is was not modified in the time between the start of the current WU, and the time FCI client runs it will be skipped.

The reason why a file is skipped for upload is now displayed too, and can be one of the following:
- Nonexistent, the file simply does not exist.
- Unreadable, the file cannot be read.
- Commandline Override, --skip-<file> is used on the commandline.
- Configuration Override, skip-<file> is set in fci-client.conf.
- Unverifiable (current.xyz specific), there is no usable qd info to determine if the current.xyz likely belongs to the current WU or not.
- Not Current (current.xyz specific), the file was not modified in the time between the current WU started and the time FCI client runs.
- Filesize Limit (unitinfo.txt specific), the filesize exceeds 512 KB (150-200 is normal).

GPU detection is now also supported on Linux, FreeBSD and Mac OS X. On Linux if you have an Nvidia GPU and have the nvidia-settings utility installed, it will send more detailed information to the FCI server including the GPU core temp, amount of VRAM and driver version. For other GPUs only the name reported by lspci for the device is used.

Improved Functionality: Cleaner upload output

Mostly a cosmetic change, prettifying the server reponse sent to the FCI client after upload processing. But the upload processing is handled more uniformly behind the scenes now too.

Improved Functionality: Automatic Apache2 detection on Gentoo

Gentoo is the only distro that does not include the version of apache in the SERVER_SOFTWARE environmental variable on which FCI relies to detect the if Apache 2.x is used. It still assumes that Apache 1.3.x is used, although apache2 is more common these days. I recently stumbled upon the magical MOD_PERL_API_VERSION variable which allows automatic detection to work on Gentoo too. No need to modify index.pl to set $apache2 manually anymore.

Improved Functionality: New Client State Markers

Client hanging (h), this marker is shown for clients where no progress (of the currently active WU) was detected for the time of the last 2 frames. So if the time qd was executed is greater than the time it took to complete the last 2 frames added to the time of the last detected progress (completed frame). This way of classifying a client as hung can produce false positives when qd is run during a slow frame (one taking much longer than the last two frames), but this is almost always restored after the next FCI update (when more progress has been made). So when you see this marker for one of your clients you'll want to check its FAHlog.txt to see if it's justified, you may also want to check one the client locally if more progress may have been made since its last FCI client upload. The tooltip of the marker will so the time since last progress, e.g. "No progress for 1 hour 3 minutes 53 seconds". This marker is also known as the Shadowtester marker, who requested it some time ago now (Fri Mar 27, 2009).

Unable to get work (w), this marker is shown for clients whose last activity in the FAHlog.txt are "Attempt X to get work failed, and no other work to do" and "Waiting before retry" lines. This allows you to see why your clients are not showing any progress and linger at the bottom of the Expected WUs list. :)

EUE limit exceeded (e), this marker is shown for clients whose last line in the FAHlog.txt shows "EUE limit exceeded. Pausing 24 hours", which is usually preceded by a not so nice UNSTABLE_MACHINE event. This one is for rhavern who requested it some time ago now too (Tue Apr 14, 2009).

Improved Functionality: Installer now sets the default apache group for all supported OSes

Previously you were required to invoke install.pl using --group <grouname> to have the permissions set correctly for any OS other than those using 'www-data' (Debian, Ubuntu & Mepis). The installation instructions mentioned which groupname was used by default on each supported OS, this knowledge is now also available in the installer itself.

The installer has also been updated to create the parts of the /usr/local/ tree it needs if it doesn't existing on Mac OS X. Apple has learned not to pollute /usr/local/ with its system installed software as it did in Tiger, but removing it entirely is a bit drastic.

Bugfix: Team 0 now supported

This release has several team 0 fixes, and should now properly support members of this team.

Fixing this bug made me see some of the creative usernames (containing special characters) used in team 0, giving the XML parser a hard time. It was kind of silly to convert the teamstats text files to XML anyway, it was initially done for consistency with the other code, but there is a negative performance benefit to added the extra XML tags to the teamstats data. So we just parse the text file now, and stopped using the XML file. The XML teamstats files will be deleted on the first update with the new version of fci-update-stanford-files.pl, so upgrades to this new version clean up these files automatically.

Bugfix: Begun date used when Issued date is not set

The new v5 work servers initially didn't set the issue date as reported by qd anymore, so FCI cannot rely on the existence of an issue timestamp anymore. In cases where no issue timestamp is known, the begin timestamp is used.

This mostly affected the Assigned Projects page now using either the Issued date or the Begun date which ever is available (tooltip show which value is used), and to a lesser extent the Projects page which displayed the Issued date initially but now uses the Begun date.

Bugfix: fci-update-eoc-stats.pl

Fixed return value and verbose output in save_file(), so the error condition of an unwritable file is properly handled. Also, when the stats for a user cannot be downloaded, continue to the next username instead of quiting the program.

Not a bug, but a feature (although the lack of this feature could be considered a bug). I've added the --sleep <n>/-s <n> option, use -s to set the number of seconds to sleep between requests to the EOC server. Minimum sleep time is 1 second.

Minor Changes

fci-update-xml-files.pl Added support for extracting the client type from the qd data, that was added to qd released 5 December 2009 (fr 076). Before only the client.cfg was used.
The unitinfo.txt is no longer parsed (this was done if certain values could not be parsed from the qd data), the file is now only provided for personal inspection if it was uploaded in the first place.
Arguments in the client.cfg (extra_parms) and those used on the commandline (logged in FAHlog.txt on Arguments: lines) are now merged instead of concatenated, so double arguments are no longer displayed in the web interface.

fci-update-jmol-projects.pl Added mapping for new cores (A3 => GRO-A3, A4 => GRO-A4, PM => ProtoMol), and handle empty contact columns by setting the value to 'n/a' as used in FCI (Jmol uses 'NA').

convert-rrd.pl The script I used to convert all FCIs RRDs from 32bit to 64bit in the scripts/extra/ directory of the FCI tarball. It may be useful to others who need to migrate RRDs created on a 32bit server to a 64bit one.

Since this release includes a new version of fci-client.pl it's highly recommended that any FCI client you admin are updated to this new release.


The lastest FCI release (and previous releases) can be downloaded from the project website, or you can use the direct link.


For the next release, I'm planning to include support for the new (BigAdv) bonus scheme, but for this I need testers with dual quad machines to test an experimental qd release that I'm preparing for that. I'm hoping that jimerickson, Magic-Michael, and possibly others are willing to help out with testing this. Please get in touch via PM if you want to help test the new qd with bigadv support.

Beta team members using FCI should also get in touch via PM to get the super secret info on to how to include the beta projects in FCI so the beta status is indicated on the project page. Since the other psummary pages are not public yet (although the links leaked in an early version of the new project summary pages), I assume this information is still considered for beta team members only.



Meer informatie over deze release (en vorigen) in de ChangeLog op de FCI download pagina.

| [Folding@Home] Announce: Client monitor voor Linux (fci) | fci-1.8.4 | Fatal Error Group |


  • smoking2000
  • Registratie: september 2001
  • Laatst online: 18:26

smoking2000

DPC-Crew

dpkg-reconfigure reality

Topicstarter
Zoals ook op FF.org gepost, zit ik met het volgende.

Ik ben bijna klaar met het integreren van de nieuwe bonus punten in FCI, maar ben ik er nog niet uit op welke manier ik dit in PPD grafieken wil verwerken.

Welke optie heeft jullie voorkeur als FCI gebruikers?

Enkele Y-as


Dubbele Y-as


Laat je voorkeur horen middels de Doodle poll, thanks! d:)b

| [Folding@Home] Announce: Client monitor voor Linux (fci) | fci-1.8.4 | Fatal Error Group |


  • smoking2000
  • Registratie: september 2001
  • Laatst online: 18:26

smoking2000

DPC-Crew

dpkg-reconfigure reality

Topicstarter
fci-1.6.1 released!

Het resultaat van de poll was overduidelijk in voorkeur voor de enkele Y-as:



De PPD graphs in deze versie zijn dus als volgt geworden:



Verdere info over deze release uit de release announcement op FoldingForum.org:



New release of FCI: v1.6.1

New Feature: Support for the new Bonus Points

Since qd is able to calculate the bonus points from functional revision 081, FCI can use this data as well. The Bonus Points, Bonus PPD and Bonus Factor are displayed in additional columns next to the normal Points and PPD. As seen in my earlier posts, the Bonus PPD is also included in the PPD Graphs. RRDs for these new values are also added to the client queue history.

For the bonus points data to be available, you'll have to update qd on your FCI clients to at least fr 081. qd fr082 introduces an alternate PPD calculation which doesn't account for the progress, but asssumes the WU is completed at the expected date. This data is preferred for PPD values used in FCI, if the alternate PPD values are not availble, it will fallback to the points per hour and multiply by 24 as was done before.

So you'll want to run all your FCI clients at least once with --update-qd if you don't always do so already, to have the FCI client download the latest qd from your FCI server.

New Dependency: Math::Round

With the work to add support for the Bonus Points to the PPD Graphs also came the opportunity to set smarter maximum values for the graphs. I chose to use nhimult() from Math::Round for this. Most OSes on which FCI Server is supported provide a package for Math::Round, although some require some more work (Gentoo: g-cpan & OpenSUSE: OpenSUSE Build Service). The installation instructions have been updated to include instructions for Math::Round.

The Great Renaming: Credits -> Points

As Usenet saw the Great Renaming back in 1987 to provide a better naming scheme, so sees FCI its own Great Renaming today.

Due to popular demand, the column formally known as Credit has been renamed to Points to be more in line with the naming used by most users . :)

This renaming includes the keys used in the XML files generated by FCI. The exception are the XML files populated with data from the psummary and team/user stats files, whose upstream naming is adopted.

New Feature: Extended Team Information

Similar to the extinfo used in Nagios, this version of FCI ships with support for additional team information. For now this are only the team website URL, and URL to its logo. These will be shown on the team page in FCI next to the team information, smiliar to how they're shown atop of the team stats page at Stanford.

I've provided a pre-populated team-extinfo.xml with the team info of a handful of teams. A management interface is available in the Settings web interface, with which you can add more.

Improved Functionality: Show 'Passkey: Yes' in client configuration section

When a clients uses a passkey, this now also displayed on its client page in the configuration section as 'Passkey: Yes', similar to the 'Passkey found' line logged in FAHlog.txt.

Bugfix: Client Type parsing from client.cfg

fci-update-xml-files.pl will no longer overwrite the client type when parsing the client.cfg if the client type was already parsed from the qd data. This caused an incorrect type (0 No Preference) to be reported for clients which do have a client type configured (Advmethods, BigAdv, etc), but only stored in the queue.dat not also in the client.cfg (e.g. because it was set using a commandline argument).

Bugfix: Argument parsing from FAHlog.txt

fci-update-xml-files.pl will forget about the arguments it parsed from a previous FAH client startup, to properly reflect the current situation. It now also properly merges arguments from FAHlog with those in the client.cfg.

Bugfix: Don't show disfunctional TPF graph in IE

As expected, the jQuery Flot TPF graphs are not support in Internet Explorer. So these will no longer be shown for users of IE. Advanced features, require advanced browers such as Firefox, Safari, Chrome, or Opera. :)

Flot v0.6 possibly improves support for IE browers, but I haven't tested this version yet.

Minor Changes

clients.plc Align filesizes to the right in the Client Files list on detailed client pages.



Meer informatie over deze release (en vorigen) in de ChangeLog op de FCI download pagina.

Het is natuurlijk vanzelfsprekend dat de nieuwe extinfo voor DPC standaard mee geleverd wordt }:O

[Voor 3% gewijzigd door smoking2000 op 21-02-2010 21:17]

| [Folding@Home] Announce: Client monitor voor Linux (fci) | fci-1.8.4 | Fatal Error Group |


  • smoking2000
  • Registratie: september 2001
  • Laatst online: 18:26

smoking2000

DPC-Crew

dpkg-reconfigure reality

Topicstarter
http://haliemnurhuda.files.wordpress.com/2010/01/ipv61.png Drie dagen geleden zag ik dat er een nieuwe (stable) firmware voor m'n Fritz!Box 7340 was, onder andere met IPv6 support. Direct na het installeren van de firmware update heb ik dus een IPv6 prefix bij XS4ALL aangevraagd, waarna ik even later een mooie dual stack op m'n modem had draaien, en het mooi vooruitzicht om IPv6 op alle hosts in mijn netwerk te configureren. Dit is zojuist voltooid, en zodra de DNS change is overal gepropageerd is, heeft het ook nog de finishing touch. B)

Vanaf dan is de FCI project website ook beschikbaar via IPv6: http://fci.ipv6.linuxminded.nl/
De FCI server die ik voor Fatal Error Group draai via: http://fci-feg.ipv6.linuxminded.nl/
En mijn algemene website met FAH tools, qd-tools, e.d. via: http://ipv6.linuxminded.nl/

[Voor 6% gewijzigd door smoking2000 op 19-11-2010 23:42]

| [Folding@Home] Announce: Client monitor voor Linux (fci) | fci-1.8.4 | Fatal Error Group |

Pagina: 1


Nintendo Switch (OLED model) Apple iPhone 13 LG G1 Google Pixel 6 Call of Duty: Vanguard Samsung Galaxy S21 5G Apple iPad Pro (2021) 11" Wi-Fi, 8GB ram Nintendo Switch Lite

Tweakers vormt samen met Hardware Info, AutoTrack, Gaspedaal.nl, Nationale Vacaturebank, Intermediair en Independer DPG Online Services B.V.
Alle rechten voorbehouden © 1998 - 2021 Hosting door True

Tweakers maakt gebruik van cookies

Bij het bezoeken van het forum plaatst Tweakers alleen functionele en analytische cookies voor optimalisatie en analyse om de website-ervaring te verbeteren. Op het forum worden geen trackingcookies geplaatst. Voor het bekijken van video's en grafieken van derden vragen we je toestemming, we gebruiken daarvoor externe tooling die mogelijk cookies kunnen plaatsen.

Meer informatie vind je in ons cookiebeleid.

Sluiten

Forum cookie-instellingen

Bekijk de onderstaande instellingen en maak je keuze. Meer informatie vind je in ons cookiebeleid.

Functionele en analytische cookies

Deze cookies helpen de website zijn functies uit te voeren en zijn verplicht. Meer details

janee

    Cookies van derden

    Deze cookies kunnen geplaatst worden door derde partijen via ingesloten content en om de gebruikerservaring van de website te verbeteren. Meer details

    janee