|
|
| (352 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| − | 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 [[Sysadmin Todo List#Completed|Completed]]. | + | This is the new Sysadmin Todo List as of 05/27/2010. The previous list was moved to [[Old Sysadmin Todo List]]. This list list is incomplete, and needs updating. |
| − | == Important ==
| |
| − | === Einstein Upgrade ===
| |
| − | [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/index.html Massive amount of deployment documentation for RHEL 5]
| |
| | | | |
| − | '''Remade the RAID5. Will redo the software, but if the RAID dies again we should think of a different machine to sub for einstein.'''
| + | == Projects == |
| | + | *Convert physical and VMs to CentOS 6 for compute servers ([[taro]],[[endeavour]]) and all others to either 6 or 7. |
| | + | **VMs: Einstein |
| | + | **Physical: [[endeavour]], [[taro]], and [[gourd]] |
| | + | *Mailman: Clean up mailman and make sure all the groups and users are in order. |
| | + | *CUPS: Look into getting CUPS authenticating users through LDAP instead of using Samba. |
| | + | *Printer: Get printtracker.py working and see if you can get a driver to properly recognize page number count instead of just giving the value as a number of 1 which corresponds to a job submission not the number of pages. |
| | + | *Check /etc/apcupsd/shutdown2 script on Gourd to make sure all the keys are correctly implemented so the machines go down properly during a power outage. |
| | + | *Do a check on Lentil to see if there is any unneccessary data being backed up. |
| | | | |
| − | # Pick a date within the next week '''Monday, 7/23/2007'''
| + | ==Daily Tasks== |
| − | # Send an e-mail to Aaron, warning him of the future takedown of tomato '''Done'''
| |
| − | # Update Tomato to RHEL5 '''Installed w/ basic configuration (auth, autofs, etc)'''
| |
| − | # Check all services einstein currently provides. Locate as many custom scripts, etc. as is reasonable and label/copy them.
| |
| − | ## [[DNS]] ''Installed, set up, working''
| |
| − | ## [[LDAP]] ''Installed, set up, working.'' Changed config files on tomato and einstein to do replication, but their LDAP services need restarted. Need to schedule a time to do it on einstein. Double-check configs!
| |
| − | ## [[Postfix]] ''Installed, set up, working!''
| |
| − | ## [[AMaViS]] ''Installed, set up''
| |
| − | ## [[ClamAV]] ''Installed, set up''
| |
| − | ## [[SpamAssassin]] ''Installed, set up, working? (need to test to make sure)''
| |
| − | ## <del>[[Cyrus Imap|IMAP]] <code>cyradm localhost</code> gives "cannot connect to server". This all seems to be sasl-related. It'd be probably be easy if there was a way to have cyrus use PAM. [http://www.openldap.org/doc/admin23/sasl.html LDAP and sasl] <ins>Nevermind, that has to do with using SASL to authenticate LDAP</ins><code>saslauthd -v</code> lists pam and ldap as available authentication mechanisms, and /etc/sysconfig/saslauthd has an entry "MECH=pam"…! What am I missing? '''Tried making a new "mail.physics.unh.edu.crt" for tomato, but couldn't because that would have required revoking einstein's cert of the same name. Tried using the "tomato.unh.edu.crt" and "tomato.unh.edu.key", but is giving the same results as the "mail.physics.unh.edu.*" copied from einstein.''' Tried using tomato's UNH address instead of hostname: same result. '''I'm able to login using the <code>imtest</code> program, but the server doesn't send the same messages as shown [http://cyrusimap.web.cmu.edu/twiki/bin/view/Cyrus/ImtestByHand here].'''</del> Let's try Dovecot instead. It supposed to be simpler to maintain and is supported by RedHat.
| |
| − | ## [[automount|/home]] ''Installed, set up, working''
| |
| − | ## [[Samba]] ''Installed, set up, working.'' If anyone needs samba access, they need to find us and have us make them a samba account. No LDAP integration.
| |
| − | ## [[Web Servers|Web]]?
| |
| − | ## Fortran compilers and things like that? (Also needs compat libs--'''Nope, tomato is 32-bit.''')
| |
| − | # Clone those services to tomato
| |
| − | # Switch einstein <-> tomato, and then upgrade what was originally einstein
| |
| − | # Look into making an einstein, tomato failsafe setup.
| |
| | | | |
| − | === Miscellaneous ===
| + | These are things that should be done every day when you come into work. |
| − | * When I was checking root's email, I waded through the logwatch reports and found that gourd's been giving smartd errors, namely
| |
| − | <code>
| |
| − | Offline uncorrectable sectors detected:
| |
| − | /dev/sda [3ware_disk_00] - 48 Time(s)
| |
| − | 1 offline uncorrectable sectors detected
| |
| − | </code>
| |
| − | benfranklin is apparently up and running somewhere, because it's reporting drive issues too:
| |
| − | <code>
| |
| − | Currently unreadable (pending) sectors detected:
| |
| − | /dev/hda - 48 Time(s)
| |
| − | 1 unreadable sectors detected
| |
| − | </code> interesting that both have a 48 times error every day. Gourd's drive needs looking at, and benfranklin eventually someday if we find out where it is. '''Benfranklin is Dan's workstation, it's in the room next to Maurik's office.''' <font color="green"><b>BenFranklin is a Pentium III "Coppermine" at 800MHz. I have ordered a replacement system already, so we can decommission the old BenFranklin.</b></font>
| |
| − | * Lentil's not doing backups. I tried manually runing the script friday afternoon and the email log looks like it was backing up and stopped for no real reason. Checking the space on the drives (since the script seems unable to do so now), I found that npg-daily/28 is basically full, and npg-daily/29 is an untouched 250gb. Maybe an update screwed around with how the script checks free space, preventing it from knowing how to move to the next drive. '''It's probably not any update - lentil was working fine until "The Friday Taro Event".''' I manually made the new symbolic link from /mnt/npg-daily-current -> /mnt/npg-daily/29 . Maybe this'll fix it? '''That seems to be a no. Lots of unable to make hard link errors, invalid cross-device link, and similar errors. It needs to know to copy the data it's backing up to the disk since it's a new disk. I still think it's got something to do with that unable to statfs error.'''
| |
| − | * Continue purgin NIS from ancient workstations, and replacing with files. The following remain:
| |
| − | ** pauli nodes
| |
| − | * '''Environmental monitoring'''. See [[The Friday Taro Event]] for more.
| |
| − | ** For sensors, we need to get them working on just one reliable machine to get decent notification. '''blackbody''' has a CPU temp. sensor that works. [http://www.lm-sensors.org/wiki/FAQ lm_sensors FAQ] - adding more sensors seems to work for bb, but some settings seem to be off. <font color="green">Sensors is working on both Taro and Pepper. We should now tie this into the Cacti readout scheme. (volunteers?) </font>
| |
| − | ** We should also look into dedicated temperature monitoring devices. <font color="green">Ordered, a nice one, should be here before Christmas. This can be read out by SNMP so we can get Okra/Cacti to read and log it.</font>
| |
| − | ** RAID monitoring with smartd works on gourd. We should try to figure out why.
| |
| − | * To fix the RAID degradation, a disk has been transferred from lentil to taro. Now lentil is one short. '''Shouldn't really be a problem, considering how many other spare empty drives we have in lentil. Well, once we figure out why lentil gives us errors in its backup script...'''
| |
| − | * Booted tomato with a Xen kernel. I'm going to try to set up some VMs. Apparently VMs of RHEL are free with the host's license. It should be easier to experiment with IMAP and the other upgrade issues (such as the swap) with some VMs running on the network. [http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html#SECTION01110000000000000000 Xen Docs] Tomato isn't cooperating with the installation, as usual. We need to resize or rearrange the data partition to give some space for installations. Apparently it's not possible to simply resize an LVM partition.
| |
| − | * Idea for a future virtual machine: Set it up with vital services like LDAP and mail, and let it get the latest and greatest updates. Test that these updates don't break anything, then send the packages the npg-custom repository.
| |
| − | * Learn how to use [[cacti]] on okra. Seems like a nice tool, mostly set up for us already. '''Find out why lentil and okra (and tomato?) aren't being read by [[cacti]]. Could be related to the warnings that repeat in ''okra:/var/www/cacti/log/cacti.log''.''' Not related to the warnings; those are for other machines that are otherwise being monitored. <font color="blue">Try adding cacti to the exclude exclude list in access.conf</font> Nevermind, lentil doesn't have any restrictions. Need to find out the requirements for a machine to be monitored by cacti/rrdtools. The documentaion makes it sound like only the cacti host needs any configuration, but I'm dubious. '''Ahh, it looks like every client has a file snmpd.conf, which affects what can be graphed.''' Tried configuring things on improv as in the Cacti HowTo, but no go. Must be some other settings as well. '''At some point on friday, cacti stopped being able to monitor einstein. Update-related? There are no errors in cacti.log, but the status page for einstein just says "down".'''
| |
| − | * Install the right SNMP stuff on tomato so that it can be graphed
| |
| − | * '''jalapeno hangups:''' Look at sensors on jalapeno, so that cacti can monitor the temp. The crashing probably isn't the splunk beta (no longer beta!), since it runs entirely in userspace. '''lm_sensors fails to detect anything readable. Is there a way around this?'''
| |
| | | | |
| − | == Ongoing ==
| + | #Do a physical walk-through/visual inspection of the server room |
| − | === Documentation ===
| + | #Verify that all systems are running and all necessary services are functioning properly |
| − | * '''<font color="red" size="+1">Maintain the Documentation of all systems!</font>''' | + | #*For a quick look at which systems are up you can use /usr/local/bin/[[serversup.py]] |
| − | ** Main function | + | #*[[Gourd]]: Make sure that home folders are accessible, all virtual machines are running |
| − | ** Hardware
| + | #*[[Einstein]]: Make sure that [[LDAP]] and all [[e-mail]] services (dovecot, spamassassain, postfix, mailman) are running |
| − | ** OS
| + | #*[[Roentgen]]: Make sure website/MySQL are available |
| − | ** Network
| + | #*[[Jalapeno]]: Named and Cups |
| − | * Continue homogenizing the configurations of the machines.
| + | #*[[Lentil]]: Verify that backups ran successfully overnight. Check space on backup drives, and add new drives as needed. |
| − | * Improve documentation of [[Software Issues#Mail Chain Dependencies|mail software]], specifically SpamAssassin, Cyrus, etc. | + | #Check [[Splunk]]: [https://pumpkin.farm.physics.unh.edu:8000 click here if you're in the server room], or open localhost:8000 (use https) from [[Pumpkin]] |
| − | === Maintenance ===
| + | #*Check logs for errors, keep an eye out for other irregularities. |
| − | * Check e-mails to root every morning | + | #Check [[Cacti]]: [http://roentgen.unh.edu/cacti http://roentgen.unh.edu/cacti] |
| − | * Resize/clean up partitions as necessary. Seems to be a running trend that a computer gets 0 free space and problems crop up. Symanzik, bohr seem imminent. '''Yup, bohr died. Expanded his root by 2.5 gigs. Still serious monitor problems though, temporarily bypassed with vesa...''' Bohr's problem seems tied to the nvidia drivers, let's wait until the next release and see how those work out. | + | #*Verify that temperatures are acceptable. |
| − | * Check up on security [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/ch-sec-network.html#ch-wstation]
| + | #*Monitor other graphs/indicators for any unusual activity. |
| | | | |
| − | === On-the-Side === | + | ==Weekly Tasks== |
| − | * See if we can get the busted printer in 322 to work down here.
| |
| − | * Certain settings are similar or identical for all machines, such as resolv.conf. It would be beneficial to write a program to do remote configuration. This would also simplify the process of adding/upgrading machines. '''Since resolv.conf was mentioned, I made a [[Script Prototypes#setres|prototype]] that seems to work.''' Another idea that was tossed around was a program that periodically compared such files against master copies, to see if the settings somehow got changed. '''Learn how to use ssh-agent for most of these tasks'''
| |
| − | * 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.''' <font color="green"> 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.</font> 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. [http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Deployment_Guide-en-US/ch-acls.html#s2-acls-mounting-nfs] '''Put this on the backburner for now, since the current rate of backup disk consumption will give about 10 months before the next empty disk is needed.'''
| |
| | | | |
| − | == Waiting ==
| + | These are things that should be done once every 7 days or so. |
| − | * That guy's computer has a BIOS checksum error. Flashing the BIOS to the newest version succeeds, but doesn't fix the problem. No obvious mobo damage either. What happen? '''Who was that guy, anyhow?''' (Silviu Covrig, probably) The machine is gluon, according to him. '''Waiting on ASUS tech support for warranty info''' Aaron said it might be power-supply-related. '''Nope. Definitely not. Used a known good PSU and still got error, reflashed bios with it and still got error. '''Got RMA, sending out on wed.''' Waiting on ASUS to send us a working one!''' Called ASUS on 8/6, they said it's getting repaired right now. '''Wohoo! Got a notification that it shipped!''' ...they didn't fix it... Still has the EXACT same error it had when we shipped it to them. '''What should we do about this?''' I'm going to call them up and have a talk, considering looking at the details on their shipment reveals that they sent us a different motherboard, different serial number and everything but with the same problem.
| |
| − | * Printer queue for Copier: Konica Minolta Bizhub 750. IP=pita.unh.edu '''Seems like we need info from the Konica guy to get it set up on Red Hat. The installation documentation for the driver doesn't mention things like the passcode, because those are machine-specific. Katie says that if he doesn't come on Monday, she'll make an inquiry.''' <font color="green">Mac OS X now working, IT guy should be here week of June 26th</font> '''Did he ever come?''' No, he didn't, and did not respond to a voice message left. Will call again.
| |
| − | * Try to pull as much data from Jim William's old drives as possible, if there's even anything on them. '''They seem dead. Maybe we can swap one board to the other drive and see if it works?''' What room is he in? His computer is working now (the ethernet devices will have to be changed to a non-farm setup once the machine is back in his office).
| |
| − | * Pauli crashes nearly every day, not when backups come around. We need to set up detailed system logging to find out why. Pauli2 and 4 don't give out their data via /net to the other paulis. This doesn't seem to be an autofs setting, since I see nothing about it in the working nodes' configs. Similarly, 2,4, and 6 won't access the other paulis via /net. 2,4 were nodes we rebuilt this summer, so it makes sense they don't have the right settings, but 6 is a mystery. Pauli2's hard drive may be dying. Some files in /data are inaccessible, and smartctl shows a large number of errors (98 if I'm reading this right...). Time to get Heisenberg a new hard drive? '''Or maybe just wean him off of NPG…''' It may be done for; can't connect to pauli2 and rebooting didn't seem to work. Need to set up the monitor/keyboard for it & check things out. '''The pauli nodes are all off for now. They've been deemed to produce more heat than they're worth. We'll leave them off until Heisenberg complains.''' Heisenberg's complaining now. Fixed his pauli machine by walking in the room (still don't know what he was talking about) and dirac had LDAP shut off. He wants the paulis up whenever possible, which I explained could be awhile because of the heat issues.
| |
| | | | |
| − | == Completed ==
| + | #Check physical interface connections |
| − | * Taro and Pepper Iptable configurations: It seems that we have a problem in the iptable configuration, which caused connectivity issues on taro. | + | #*Verify that all devices are connected appropriately, that cables are labeled properly, and that all devices (including RAID and IPMI cards) are accessible on the network. |
| − | * Taro now has one ethernet port connected to the backend network. Outside connectivity is over the VLAN.
| + | #Check Areca RAID interfaces |
| − | * Swap jalapeno power supply. No need to schedule downtime, considering it's always down. '''Has this been done? It's been up all week.''' The Epsilon power supply we bought for taro way back at the begining of the summer is now in jalapeno.
| + | #*The RAID interfaces on each machine are configured to send e-mail to the administrators if an error occurs. It may still be a good idea to login and check them manually on occasion as well, just for the sake of caution. |
| − | * The weather might be getting too cold for running two air conditioners. The top one has been having some issues. Yesterday I came in and it had left the floor wet. Today, it had collected a major amount of ice and started to flash its lights and beep. I turned it off after that. '''The other day I came in and both were coated in ice and the room was stifling. I defrosted with the door wide open and fans on high. Any chance we can start leaving the window open without running environmental risks to the machines?''' We'd have to disconnect the top machine to do that, and that's a heavy-duty job, so probably not. '''See [[The Friday Taro Event]]''' Whoops. Looks like it happened by itself.
| + | #Clean up the server room, sweep the floors. |
| − | * Made a hard copy of roentgen's <code>getent passwd</code> in ''/etc/passwd'' (ditto for group and shadow), and commented out the nis dependencies in roentgen's ''/etc/nsswitch.conf''. Now roentgen should be free of the shackles of NIS. While doing the transfer, I noticed that my account didn't have a shadow entry! I copied the entry from einstein to roentgen, and voila, I could log into roentgen. Good riddance, NIS!
| |
| − | * Coincidentally, roentgen's UPS started flipping out right after I finished the above. It ran out of power, so I quickly replaced the old UPS with the new one that was being used by Matt's workstation.
| |
| − | * Temporarily mounted that random box fan that's been in the hall all summer into the old AC's spot. The maintenance guy's note implies that we'll be getting a fan to actually fit the hole, and Maurik said we might get a freestanding AC unit to pump cold air straight onto the machines. | |
| − | * Sent a request to order a replacement battery for Roentgen's UPS to Michelle Walker.
| |
| − | * '''Something very wrong happened to tomato: I changed grub.conf to boot at runlevel 3 (normal, excludes X) and rebooted, but there was a kernel panic mentioning not being able to find vg_tomato. I rebooted again at the default runlevel, and got the same error. I booted with the intall disk, and it doesn't see any LVM anywhere.''' Ok, so it sees some LVM on sdd4. It also lists /dev/md1 as a "foreign" filesystem, presumably this is where the LVM should be residing. '''The kernel panic has a message saying that only 7/8 devices could be found for RAID5 device md1. What are the odds of taro ''and'' tomato losing a disk at the same time?''' Actually, it says 7/8 failed. This doesn't seem possible... Is the RAID card unplugged or something? '''Was able to make a new RAID, maybe it was a software error?'''
| |
| | | | |
| − | == Previous Months Completed == | + | ==Monthly Tasks== |
| − | [[Completed in June 2007|June 2007]]
| |
| | | | |
| − | [[Completed in July 2007|July 2007]] | + | #Perform [[Enviromental_Control_Info#Scheduled_Maintenance|scheduled maintenance]] on the server room air conditioning units. |
| | + | #Check S.M.A.R.T. information on all server hard drives |
| | + | #*Make a record of any drives which are reporting errors or nearing failure. |
| | | | |
| − | [[Completed in August 2007|August 2007]]
| + | ==Annual Tasks== |
| | | | |
| − | [[Completed in September 2007|September 2007]]
| + | These are tasks that are necessary but not critical, or that might require some amount of downtime. These should be done during semester breaks (probably mostly in the summer) when we're likely to have more time, and when downtime won't have as detrimental of an impact on users. |
| | | | |
| − | [[Completed in October 2007|October 2007]]
| + | #Server software upgrades |
| | + | #*Kernel updates, or updates for any software related to critical services, should only be performed during breaks to minimize the inconvenience caused by reboots, or unexpected problems and downtime. |
| | + | #Run fsck on data volumes |
| | + | #Clean/Dust out systems |
| | + | #Rotate old disks out of RAID arrays |
| | + | #Take an inventory of our server room / computing equipment |
| | + | |
| | + | <!--{| cellpadding="5" cellspacing="0" border="1" |
| | + | ! Time of Year !! Things to Do !! Misc. |
| | + | |- |
| | + | | Summer Break || || |
| | + | |- |
| | + | | || Major Kernel Upgrades || |
| | + | |- |
| | + | | || Run FDisk || |
| | + | |- |
| | + | | || Clean (Dust-off/Filters) while Systems are Shut down || |
| | + | |- |
| | + | | Thanksgiving Break || || |
| | + | |- |
| | + | | Winter Break || || |
| | + | |- |
| | + | | || Upgrade RAID disks || Upgrade only disks connected to a RAID card |
| | + | |-- |
| | + | | Spring Break || || |
| | + | |- |
| | + | |} --> |
