Slave Tests

Slave Tests for 9 version 1.3

This is a list of tests to perform on a slave node after kickstarting it. Please indicate passed tests with *PASS*, failed tests with *FAIL* and provide additional information whenever possible. Also, please alter the above _ to the currnet kickstart/clone version you are testing.

Note: the slave node must have the correct bios settings before kickstarting and testing.


  1. Does sensors report the memory, voltages and temperature correctly? No alarms shown? (Run sensors to find out.)
    *PASS*
    There is also a new additional voltage "vid".

  2. Are there any error or warning messages...
    1. On boot up (run dmesg): *FAIL*
      1. ether-wake uses obsolete (PF_INET,SOCK_PACKET)
    2. During and after latest boot in /var/log/messages: *FAIL*
      1. xfs: ignoring font path element /usr/X11R6/lib/X11/fonts/cyrillic (unreadable)
      2. xfs: ignoring font path element /usr/share/fonts/default/Type1 (unreadable)
      3. kernel: ether-wake uses obsolete (PF_INET,SOCK_PACKET)

  3. Does the /data directory have reduced # of inodes and reserved space for root? (Checking that the total space for /data is approximately 75360860 with df is reliable enough.)
    *PASS*

  4. Do /boot, /lib/modules not contain vestiges of old kernels, etc?
    *PASS*

  5. Does X run properly using startx as root? This should work on a generic monitor such as a Viewtronics 771.
    *PASS*
    X started up with a very minimal instance of twm.

  6. Do gcc and ddd work correctly?
    *PASS*

  7. Does networking run properly? Is it running full duplex 100baseT (you can use mii-tool to test)?
    *PASS*

  8. Does it correctly gets its identity (eg, s012) using dhcp from the master on bootup?
    *PASS*

  9. Does the system shut down and power off with shutdown -h now?
    *PASS*

  10. After power-down, if AC power is cycled, does system remain off?
    *PASS*

  11. Does the system reboot with shutdown -r now?
    *PASS*

  12. If a running system is unplugged, then plugged in, does it remain off?
    *PASS*

  13. Can that system now be powered on from another machine using etherwake? Does it fsck and boot up correctly?
    *FAIL*
    Does not etherwake if unplugged.

  14. Does the machine act properly as a UPS master and UPS slave? If a UPS master, does it properly issue commands to shut down other machines under its control when the battery is low on the UPS? If a UPS slave, does it understand commands given to it by a UPS master? If power is restored to the UPS, does the slave remain turned off?
    *FAIL*
    Tested on s261-s280. The UPS master, s261, monitored correctly and notified the slaves. The UPS slaves received the messages and attempted to shut down. However, none of the machines shut down fast enough before the power was completely cut off. This may or may not be a problem with the UPS. Setting the FINALDELAY in upsmon.conf may help out a bit.

  15. Are there no files with dates in the future? (One way to check this is to do the following:
    cd / ; touch temp.data ; find . -cnewer temp.data -print -xdev ; rm -f temp.data
    If any files are listed, they have dates set later than the moment you executed the above command.)
    *PASS*

  16. Is NTP running correctly? Is the hardware clock synchronized with the software clock after the software clock has had its time synched with an ntp server? (Look in /var/log/messages for messages from xntpd. If ntp is working correctly, the /etc/ntp/drift file will contain a non-zero entry. Set the hardware clock in the bios to something incorrect (like last week). Boot up. Check the BIOS clock again. It has been set correctly to GMT. This might not work if you are off the UWM subnet. It depends how tight they are on securing the ntp servers.)
    *PASS*

  17. Is vgablank running correctly? (It should call vga_screenoff ten minutes after keyboard input stops, and calls vga_screenon when input resumes.)
    *PASS*

  18. Does running drag 1.2 show > 290 Mflops (at n=220) provided the screen is blanked by vgablank?
    *PASS*

  19. Does hdparm -tT /dev/hda report good speeds (~120 and ~28 MB/s)?
    *PASS*

  20. Does hdparm -tT /dev/hdc report good speeds (~120 and ~28 MB/s)?
    *PASS*

  21. Does hdparm -tT /dev/hdd show good results?
    *PASS*

  22. Is automount on the slave configured so that cd /mnt/cdrom works correctly if a cd is present?
    *FAIL*
    -bash: cd: /mnt/cdrom: No such file or directory

  23. Are big files (2 GB and higher) properly supported? If the following commands do not dump core, they should be supported:
    cp /etc/termcap a; cat a a a a a > b; cat b b b b b > c; cat c c c c c > d; cat d d d d d > e; cat e e e e e e > f
    *PASS*

  24. Does automount work?
    1. On the master, does cd /net/s012 work properly (with whatever the correct slave node # is)?
      *PASS*

    2. Does cd /net/m001 on the slave properly mount the master?
      *PASS*

    3. Does cp file /net/s012/ work correctly?
      *PASS*

  25. Can root on the master log into a node with just rsh s012 (no password needed)?
    *PASS*

  26. Does rsh work correctly, e.g. does rsh s012 uptime correctly return the uptime on s012 from m001?
    *PASS*

  27. Do the above automount and rsh tests work correctly between two slave nodes?
    *PASS*

  28. Is the file /root/cloned_date present and contain the correct information?
    *PASS*

  29. Does recloning over the network preserve the /data and /datc partitions and remake the / and /boot partitions?
    *PASS*

  30. Does /proc/fans contain 'files' that correctly report the fan RPMS?
    *PASS*

  31. Does mail correctly relay to master001.medusa.phys.uwm.edu?
    *PASS*

  32. Is sensorscheck operational and reporting errors if they occur?
    *PASS*


$Id: slavetests-9system-1.3.html,v 1.10 2003/11/24 22:40:05 kflasch Exp $