UPDATE:
With recent versions of ksysguard, you need to start off using the menu entry File->New tab. Otherwise you will not see the option to connect to a remote machine. When I create a new tab, I use 2 rows and 2 columns, because I have 4 machines in my cluster. Then I connect to each machine and drag the process controller from each machine into a cell. You can sort by CPU activity, and you'll see the processes that are using most CPU on each machine.
The following is copied from a
this post by Andre Balsa to the old ParallelKnoppix forum. The Pelican tutorial points you to the original post, but I'm copying it here too in case that forum disappears.
From Andre:
3) This is not a question but a tip : P-KPX already includes a very nice tool to monitor the cluster nodes ! It is quite simply KDE's Ksysguard and the associated daemon ksysguardd. To use :
- Launch Ksysguard on the master node (it's in the KDE System menu).
- File -> Load Standard Sheets.
- File -> Connect Host... ; in the dialog that opens, choose custom command and follow the example, user knoppix, and the ip address of node 2. This launches ksysguardd on the node and tunnels its output back to Ksysguard on the master node through ssh. Nice and safe!
- Repeat for nodes 3 - n.
- Edit -> Worksheet Properties; adjust the number of columns/rows.
- Drag-n-drop sensors from the Sensor browser on the left to empty worksheet cells.
Bingo! -> complete monitoring of each node, nice graphical panel showing the status of the cluster, alarms, etc. Cool
Once you have a custom worksheet that fits your cluster monitoring requirements, you can save it and avoid having to recreate it at each cluster reboot.
------------
Thanks again to Andre for that tip. The cluster monitor on PK used this, and if you're interested, it's quick to do this on Pelican, too. I may add a cluster monitor as part of the Pelican setup in the future, but for now, at least the info about how to do it is here.
