Sysadmin Todo List

This is an unordered set of tasks. Detailed information on any of the tasks typically goes in related topics' pages, although usually not until the task has been filed under Completed.

Daily Check off list

Each day when you come in check the following:

Einstein (script):
1. Up and running?
2. Disks are at less than 90% full?
3. Mail system OK? (spamassasin, amavisd, ...)
Temperature OK?
Systems up: Taro, Pepper, Pumpkin/Corn ?
Backups:
1. Did backup succeed?
2. Does Lentil need a new disk?

Important

Towards a stable setup

Here are some options:

Test VMware server (See VMWare Progress). Specifically, I would like to know:

1. How easy is it to move a VM from one hardware to another? (Can you simply move the disks?) Yes.
2. Specifically, if you need to service some hardware, can you move the host to other hardware with little down time? (Clearly not for large disk arrays, like pumpkin, but that is storage, not hosts). Considering portability of disks/files, the downtime is the time it takes to move the image around and start up on another machine.
3. Do we need a RedHat license for each VM or do we only need a license for the host, as with Xen? It seems to consume a license per VM. Following this didn't work for the VMWare systems. The closes thing to an official word that I could find was this.
4. VMware allows for "virtual appliances", but how good are these really? Are these fast enough?

Miscellaneous

Figure out the mailman password!
Fix EVO webcam video on Sarah's computer.
Fix front sound output on Sarah's computer.
Determine a better organization system for cables, parts, etc. Junky cardboard boxes are a bit cumbersome, and they look bad.
We should look into what software is necessary on what machines, for disk space concerns. I'm thinking of Pepper in particular, do we really want openoffice data taking up an eighth of the root partition?
Gourd is giving smartd errors. Should we be concerned at all, since nobody uses it anymore?
Move systems into the new rack.
- Zip tie the cables in place behind the rack.
Set up the wigner printer queue on einstein, as well as tracking supply usage, etc.
Set up the new benfranklin. ATI strikes again. Maybe the proprietary drivers work better, but these are so bad that FC9 dies from it.
Pull Maurik's old data off blackbody, and then make blackbody a real workstation again.
Bohr is slow with PDFs. Maybe time to put a newer distro on bohr?
Upgrade lepton.
Order replacement batteries for those UPS power strip things. Looks like they're HC 1221W, made by CSB battery co.
Move pauli8 drives into another machine so that Heisenberg can access his data.
Get the rest of the paulis up. Looks like NIS is in the way on at least one of them. Update to LDAP will be necessary.
Fix some of the older workstations (hobo, ennui, etc.)
Get PxEboot network installs working. Gluon should be a good testbed, since it needs to be fixed anyways.
Monitoring: I would like to see the new temp-monitor integrated with Cacti, and fix some of the cacti capabilities, i.e. tie it in with the sensors output from pepper and taro (and tomato/einstein). Setup sensors on the corn/pumpkin. Have an intelligent way in which we are warned when conditions are too hot, a drive has failed, a system is down. I'm starting to get the hang of getting this sort of data via snmp. I wrote a perl script that pulls the temperature data from the environmental monitor, as well as some nice info from einstein. We SHOULD be able to integrate a rudimentary script like this into cacti or splunk, getting a bit closer to an all-in-one monitoring solution. It's in Matt's home directory, under code/npgmon/
Check into smartd monitoring (and processing its output) on Pepper, Taro, Corn/Pumpkin, Einstein, Tomato (Actually, all the systems).
Learn how to use cacti using a VM appliance.

Ongoing

Documentation

Maintain the Documentation of all systems!
- Main function
- Hardware
- OS
- Network
Continue homogenizing the configurations of the machines.

Maintenance

Check e-mails to root every morning
Check up on security [1]

On-the-Side

Learn how to use ssh-agent for task automation.
Backup stuff: We need exclude filters on the backups. We need to plan and execute extensive tests before modifying the production backup program. Also, see if we can implement some sort of NFS user access. I've set up both filters and read-only snapshot access to backups at home. Uses what essentially amounts to a bash script version of the fancy perl thing we use now, only far less sophisticated. However, the filtering and user access uses a standard rsync exclude file (syntax in man page) and the user access is fairly obvious NFS read-only hosting. I am wondering if this is needed. The current scheme (ie the perl script) uses excludes by having a .rsync-filter is each of the directories where you want excluded contents. This has worked well. See ~maurik/tmp/.rsync-filter . The current script takes care of some important issues, like incomplete backups. Ah. So we need to get users to somehow keep that .rsync-filter file fairly updated. And to get them to use data to hold things, not home. Also, I wasn't suggesting we get rid of the perl script, I was saying that I've become familiar with a number of the things it does. [2]
Continue purgin NIS from ancient workstations, and replacing with files. The following remain:
- pauli nodes -- Low priority!

Waiting

Sent out an email to Heisenberg explaining that the intel fortran compiler is a commercial piece of software, and he only purchased the 32-bit version. Waiting to see if he can use GCC instead.