Difference between revisions of "Lentil"
From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search| Line 2: | Line 2: | ||
Lentil performs [[backups]]. Its backup script needs further investigation to determine exactly how it works. | Lentil performs [[backups]]. Its backup script needs further investigation to determine exactly how it works. | ||
== Network Configuration == | == Network Configuration == | ||
| − | |||
| − | |||
Currently connected to the unh and farm networks via the switch and VLAN. | Currently connected to the unh and farm networks via the switch and VLAN. | ||
| − | + | eth0 | |
| − | + | Hostname: lentil.farm.physics.unh.edu | |
| − | + | HWaddr 00:23:54:BC:70:F1 | |
| − | + | IP:10.0.0.250 | |
| − | + | eth0.2 | |
| − | + | Hostname: lentil.unh.edu | |
| − | + | HWaddr 00:23:54:BC:70:F1 | |
| − | + | IP:132.177.88.254 | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Access Configuration == | == Access Configuration == | ||
| Line 112: | Line 78: | ||
This will send the boot.log to npg-admins everytime the pc is started. | 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 | mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log | ||
| + | |||
| + | == Wake On LAN == | ||
| + | This is used so we can shutdown the server and remotely turn it back on. | ||
| + | Wake On Lan Command: | ||
| + | sudo ether-wake 00:1e:4f:9b:13:90 | ||
== Hardware Information == | == Hardware Information == | ||
| Line 118: | Line 89: | ||
User Manual: [http://nuclear.unh.edu/wiki/images/7/72/E4411_P5QL-CM V2.pdf Users Manual] | User Manual: [http://nuclear.unh.edu/wiki/images/7/72/E4411_P5QL-CM V2.pdf Users Manual] | ||
Memory: 2 GB DDR2 | Memory: 2 GB DDR2 | ||
| − | |||
== Fixes == | == Fixes == | ||
*Kernel Crash Fix (2/24/2009) | *Kernel Crash Fix (2/24/2009) | ||
**[[Hardware Issues History]] | **[[Hardware Issues History]] | ||
Revision as of 15:03, 2 June 2009
General Information
Lentil performs backups. Its backup script needs further investigation to determine exactly how it works.
Network Configuration
Currently connected to the unh and farm networks via the switch and VLAN. eth0
Hostname: lentil.farm.physics.unh.edu HWaddr 00:23:54:BC:70:F1 IP:10.0.0.250
eth0.2
Hostname: lentil.unh.edu HWaddr 00:23:54:BC:70:F1 IP:132.177.88.254
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
The configuration file is at /etc/smartd.conf. The smartd.conf does a silent check, which only emails reports if the SMART health status comes back as failed. This smartd.conf will look different from alot of the other computers because it doesn't have a RAID card installed, so each disk is mounted seperately for backups.
SMARTD Smartd setup and configuration
rc.local Configuration
This script is modified to run commands when the system is done powering on.
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
Wake On LAN
This is used so we can shutdown the server and remotely turn it back on. Wake On Lan Command:
sudo ether-wake 00:1e:4f:9b:13:90
Hardware Information
Motherboard: Asus P5QL-CM Specifications: Specifications User Manual: V2.pdf Users Manual Memory: 2 GB DDR2
Fixes
- Kernel Crash Fix (2/24/2009)
