CB MOC is a peer node monitoring tool used by Chess Brain peer node operators. Although this project is in it's beginning development stages, CB MOC is already a useful monitoring program that provides useful and easy to view statistics.

The current version of CB MOC is v. 0.6, as it is not yet complete. While it has been tested for functionality and usability, there absolutely are no guarantees that this software will operate correctly. Having said that, I personally run this daily and have found it to be quite stable and useful.

New In v.0.6

• Initial graphing capabilities
• Pie chart showing peer node contribution to computation power
• Added timestamp table column (with sorting)
• Added "Idle" table column, seconds since last job was posted
• Added Clock
• Implemented continuous table sorting and coloring

New In v.0.5 (first public release)

• Table sorting by column
• Tablular statistics plus raw message view
• Intelligent job post reading, with generation of statistics

Also, you can check the CB-MOC Change Log and Development Status pages for more detailed information on the status of upcoming features.

To run CB-MOC you must have a relatively current Java Runtime Environment installed on your machine. If you don't have one you can download the current Sun JRE from Sun's "Get Java" page.

If you run the CB-MOC often in a Linux or Other GUI environment, I recommend placing a shortcut or "Launcher" icon on your desktop for ease of use. If creating a Launcher, use the above command line commands. (And CB-MOC Icons are coming soon, just for such an occasion.)

In order for CB MOC to receive messages from your peer nodes, you must configure each Chess Brain peer node to report to the address of the machine that CB MOC will be running. This configuration varies by the operating system that the Peer Node client is running on but for each peer node there is an option such as Peer Node Monitor Address . This needs to be set to the network IP address of the machine that will be running MOC.

Once running, you can simply observe the statistics as the jobs are reported. The CB MOC has several tabs at the top of the window. Currently "Monitoring" and "Messages" tabs are available. The Monitoring tab displays collected and summarized statistics for each peer node reporting to CB MOC. The Messages tab displays the "raw" messages sent from each peer node, in case you're curious. More tabs will appear in the future with other features available.

For those who need to have the peer node reports pass through a firewall in order to get to CB MOC, or for those who run a personal firewall on their computers, here's the information you need. (If you don't know what we're talking about, you probabaly don't need to read any of this.) The network communication used by the peer nodes to communicate to CB MOC occurs on TCP port 3434. The traffic orignates from the peer nodes and connects to the CB MOC who reads the info and disconnects for each job posted. So your firewall or firewall software will need to allow TCP traffic from peer nodes to CB MOC on port 3434.

Some have asked about the access control model used for the extended server functions. This is something that I hope will be more developed and generally useful as the code and functions open up. But the value "578d4b7717b556f541a2fd7a50c66e35" used in the request parameter is simply the md5 hash for "13373mu:getscore" which is only used for an integrity check.

As this project is just getting started, feedback from those who use this software can help eliminate bugs and tweak features to make them more valuable. If you have a bug report, please send as much information as possible to help explain the issue. If possible please include your OS, Java Runtime Environment version, and a description of the problem and how to re-create it. While I can't respond to and address all concerns, all such feedback is taken into consideration for future development efforts.

Send bug reports to: Kris Drent, kdrent <at> blivion <dot> com.