Error Logs

There are a number of ways to check for errors that occur during the compute node boot process, as follows:

• During the compute node boot process, any error messages are sent to the console of the compute nodes and copied to the master node's /var/log/messages file by the kernel logging daemon klogd. Messages can be viewed by editing this file.

  You can also view these messages by running the standard Linux System Logs tool. Select System Tools -> System Logs from the desktop menu to open the System Logs window. Select the System Log from the list of logs in the left panel, then scroll near the end to see errors that may have been reported while the node was booting.

• Node-specific messages may be viewed by right-clicking the node in the BeoSetup window and choosing View Syslog.

• Any output that is generated by the node_up script is sent to a log file in /var/log/beowulf/. The actual log file is named node.<nodenumber>, where <nodenumber> is the node number for the node in question. If the compute node ends up in the error state, then there was a problem during the node_up script, and you should check the error log in /var/log/beowulf/.

  This log can also be checked by right-clicking on the node in the BeoSetup window and choosing View Beoboot Log from the menu.

• If the node never seems to get to the boot state, check the console of the compute node or the master node's /var/log/messages file to see what is happening.