Difference between revisions of "Lentil"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to searchLine 223: | Line 223: | ||
</pre> | </pre> | ||
== rc.local Configuration == | == rc.local Configuration == | ||
+ | This script is modified to run commands when the system is done powering on. | ||
=== /etc/rc.local === | === /etc/rc.local === | ||
<pre> | <pre> | ||
Line 236: | Line 237: | ||
mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log | mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log | ||
</pre> | </pre> | ||
+ | |||
== Hardware Information == | == Hardware Information == | ||
Motherboard: Asus P5QL-CM | Motherboard: Asus P5QL-CM |
Revision as of 15:40, 1 June 2009
General Information
Lentil performs backups. Its backup script needs further investigation to determine exactly how it works.
Network Configuration
Hostnames: lentil.unh.edu, lentil.farm.physics.unh.edu
Currently connected to the unh and farm networks via the switch and VLAN.
ifconfig
eth0 Link encap:Ethernet HWaddr 00:23:54:BC:70:F1 inet addr:10.0.0.250 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::223:54ff:febc:70f1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30404 errors:0 dropped:0 overruns:0 frame:0 TX packets:1778 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3723593 (3.5 MiB) TX bytes:227139 (221.8 KiB) Interrupt:66 Base address:0x6000 eth0.2 Link encap:Ethernet HWaddr 00:23:54:BC:70:F1 inet addr:132.177.88.254 Bcast:132.177.91.255 Mask:255.255.252.0 inet6 addr: fe80::223:54ff:febc:70f1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:28826 errors:0 dropped:0 overruns:0 frame:0 TX packets:1032 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3068357 (2.9 MiB) TX bytes:114723 (112.0 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:99 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9335 (9.1 KiB) TX bytes:9335 (9.1 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:54 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:10754 (10.5 KiB)
/etc/sysconfig/network-scripts/ifcfg-farm
# Intel Corporation 82541GI Gigabit Ethernet Controller DEVICE=eth0 BOOTPROTO=none #HWADDR=00:0E:0C:4C:E1:52 ONBOOT=yes DHCP_HOSTNAME=lentil.unh.edu IPADDR=10.0.0.250 NETMASK=255.255.255.0 TYPE=Ethernet USERCTL=no IPV6INIT=no PEERDNS=yes
/etc/sysconfig/network-scripts/ifcfg-unh
VLAN=yes # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. GATEWAY=132.177.88.1 TYPE=Ethernet DEVICE=eth0.2 #HWADDR=00:0e:0c:4c:e1:52 BOOTPROTO=none NETMASK=255.255.252.0 IPADDR=132.177.88.254 ONBOOT=yes USERCTL=no IPV6INIT=no PEERDNS=yes
/etc/sysconfig/network-scripts/ifcfg-lo
DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) BROADCAST=127.255.255.255 ONBOOT=yes NAME=loopback
Access Configuration
/etc/security/access.conf Any valid user can log into lentil from any machine on the Internet.
Backup Configuration
Location of Backups
/mnt/npg-daily/34/
All backup related scripts are:
/etc/auto.npg-daily /usr/local/bin/rsync_backup.pl /etc/cron.daily/0rsync_backup /usr/sbin/vgcfgbackup /etc/rsync-backup.conf
/etc/rsync-backup.conf
# Backups are 'pull' only. Too bad there isn't a better way to enforce this. read only = yes # Oh for the ability to retain CAP_DAC_READ_SEARCH, and no other. #uid = root # XXX There seems to be an obscure bug with pam_ldap and rsync whereby # getpwnam(3) segfaults when (and only when) archiving /etc. Using a numeric # uid avoids this bug. Only verified on Fedora Core 2. uid = 0 # There's not much point in putting the superuser in a chroot jail # use chroot = yes # This isn't really an effective "lock" per se, since the value is per-module, # but there really ought never be more than one, and it would at least # ensure serialized backups. max connections = 1 [usr_local] path = /usr/local comment = unpackaged software [opt] path = /opt comment = unpackaged software [etc] path = /etc comment = conf files [var] path = /var comment = user and system storage
SNMP Configuration
/etc/snmp/snmpd.conf Copied from Pepper.
Smartd Configuration
/etc/smartd.conf
# *SMARTD*AUTOGENERATED* /etc/smartd.conf # Remove the line above if you have edited the file and you do not want # it to be overwritten on the next smartd startup. # Sample configuration file for smartd. See man 5 smartd.conf. # Home page is: http://smartmontools.sourceforge.net # The file gives a list of devices to monitor using smartd, with one # device per line. Text after a hash (#) is ignored, and you may use # spaces and tabs for white space. You may use '\' to continue lines. # You can usually identify which hard disks are on your system by # looking in /proc/ide and in /proc/scsi. # The word DEVICESCAN will cause any remaining lines in this # configuration file to be ignored: it tells smartd to scan for all # ATA and SCSI devices. DEVICESCAN may be followed by any of the # Directives listed below, which will be applied to all devices that # are found. Most users should comment out DEVICESCAN and explicitly # list the devices that they wish to monitor. # DEVICESCAN # First (primary) ATA/IDE hard disk. Monitor all attributes # /dev/hda -a # Monitor SMART status, ATA Error Log, Self-test log, and track # changes in all attributes except for attribute 194 # /dev/hdb -H -l error -l selftest -t -I 194 # A very silent check. Only report SMART health status if it fails # But send an email in this case /dev/hde -H -m root /dev/sda -d ata -H -m root /dev/sdb -d ata -H -m root /dev/sdc -d ata -H -m root # First two SCSI disks. This will monitor everything that smartd can # monitor. # /dev/sda -d scsi # /dev/sdb -d scsi # HERE IS A LIST OF DIRECTIVES FOR THIS CONFIGURATION FILE # -d TYPE Set the device type to one of: ata, scsi # -T TYPE set the tolerance to one of: normal, permissive # -o VAL Enable/disable automatic offline tests (on/off) # -S VAL Enable/disable attribute autosave (on/off) # -H Monitor SMART Health Status, report if failed # -l TYPE Monitor SMART log. Type is one of: error, selftest # -f Monitor for failure of any 'Usage' Attributes # -m ADD Send warning email to ADD for -H, -l error, -l selftest, and -f # -M TYPE Modify email warning behavior (see man page) # -p Report changes in 'Prefailure' Normalized Attributes # -u Report changes in 'Usage' Normalized Attributes # -t Equivalent to -p and -u Directives # -r ID Also report Raw values of Attribute ID with -p, -u or -t # -R ID Track changes in Attribute ID Raw value with -p, -u or -t # -i ID Ignore Attribute ID for -f Directive # -I ID Ignore Attribute ID for -p, -u or -t Directive # -v N,ST Modifies labeling of Attribute N (see man page) # -a Default: equivalent to -H -f -t -l error -l selftest # -F TYPE Use firmware bug workaround. Type is one of: none, samsung # -P TYPE Drive-specific presets: use, ignore, show, showall # # Comment: text after a hash sign is ignored # \ Line continuation character # Attribute ID is a decimal integer 1 <= ID <= 255 # All but -d, -m and -M Directives are only implemented for ATA devices # # If the test string DEVICESCAN is the first uncommented text # then smartd will scan for devices /dev/hd[a-l] and /dev/sd[a-z] # DEVICESCAN may be followed by any desired Directives.
rc.local Configuration
This script is modified to run commands when the system is done powering on.
/etc/rc.local
#!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local #This will send the boot.log to npg-admins everytime the pc is started. mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log
Hardware Information
Motherboard: Asus P5QL-CM Specifications: Specifications User Manual: V2.pdf Users Manual Memory: 2 GB DDR2 Wake On Lan Command: sudo ether-wake 00:1e:4f:9b:13:90
Fixes
- Kernel Crash Fix (2/24/2009)