Difference between revisions of "Lentil"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
m (Drive letter fix.)
 
(63 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
== General Information ==
 
== General Information ==
Lentil is a backup server.  
+
Lentil performs [[backups]]. Its autofs is configured to mount harddrives labeled npg-daily-XX onto /mnt/npg-daily/XX where XX is a label number. Its backup script needs further investigation to determine exactly how it works.
 +
 
 +
As of Feb. 15, 2015 Lentil is mounted with the following which will last us awhile:
 +
*/dev/sdd1 mounted at /mnt/npg-daily/51; A filled 2TB hard drive
 +
*/dev/sda1 mounted at /mnt/npg-daily/52; A 4TB hard drive
 +
*/dev/sdc1 mounted at /mnt/npg-daily/53; A 4TB hard drive
 +
*/dev/sdb1 as the root file system. Don't hot swap this.
 +
 
 +
== Hardware Information ==
 +
  Motherboard: Asus P5QL-CM
 +
    Specifications: [http://nuclear.unh.edu/wiki/pdfs/motherboards/16744.pdf Specifications]
 +
    User Manual: [http://nuclear.unh.edu/wiki/pdfs/motherboards/E4411_P5QL-CM V2.pdf Users Manual]
 +
  Memory: 2 GB DDR2
 +
 
 +
 
 +
== Authentication ==
 +
Lentil authenticates against the LDAP server running on Einstein, by connecting to einstein.farm.physucs.unh.edu using sssd.
 +
Previously, Lentil went on the UNH network to einstein.unh.edu, but this is blocked (I think by ip-tables). The farm network is the better choice anyhow.
  
 
== Network Configuration ==
 
== Network Configuration ==
Currently has ethernet cable to switch, accessing outside world via the VLAN functions of the switch.
+
Currently connected to farm networks via our switch and a direct port to UNH network.
=== /etc/sysconfig/network-scripts/ifcfg-farm ===
+
Note: Previously, lentil went through the switch and a VLAN network. New network policy at UNH makes this not possible.
DEVICE=eth0
+
 
BOOTPROTO=static
+
<pre>
HWADDR=00:0E:0C:4C:E1:52
+
eth0
  IPADDR=10.0.0.250
+
  Hostname: lentil.farm.physics.unh.edu
NETMASK=255.255.252.0
+
  HWaddr 00:30:48:63:BB:40
ONBOOT=yes
+
  IP:10.0.0.250
TYPE=Ethernet
+
eth1
 +
  Hostname: lentil.unh.edu
 +
  HWaddr 00:30:48:63:BB:41
 +
  IP:132.177.88.254
 +
</pre>
 +
 
 +
== Access Configuration ==
 +
  /etc/security/access.conf
 +
  Any valid user can log into lentil from any machine on the Internet.
 +
 
 +
== Backup Configuration ==
 +
===Location of Backups ===
 +
<pre>
 +
/mnt/npg-daily-current
 +
/mnt/npg-daily/xx/
 +
</pre>
 +
All backup related scripts are:
 +
  /etc/auto.npg-daily
 +
  /usr/local/bin/rsync_backup.py
 +
  /etc/cron.daily/0rsync_backup
 +
  /usr/sbin/vgcfgbackup
 +
  /etc/rsync-backup.conf
 +
 
 +
== 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.
  
=== /etc/sysconfig/network-scripts/ifcfg-eth0.2 ===
+
This will send the boot.log to npg-admins everytime the pc is started.
# UNH network
+
  mail -s "$HOSTNAME Started, Here is the boot.log" npg-admins@physics.unh.edu < /var/log/boot.log
VLAN=yes
+
== If Lentil isn't sending e-mails ==
DEVICE=eth0.2
+
Sometimes after a reboot Lentil won't send its regular e-mail reports. To fix this you simply need to restart sendmail. Be aware that it has saved all of those messages it didn't send, and once sendmail is working you'll get all of them at once.
BOOTPROTO=static
+
== Wake On LAN ==
BROADCAST=132.177.91.255
+
This is used so we can shutdown the server and remotely turn it back on.
IPADDR=132.177.88.254
+
Wake On Lan Command:
NETMASK=255.255.252.0
+
  sudo ether-wake 00:1e:4f:9b:13:90
NETWORK=132.177.88.0
+
== Fixes ==
ONBOOT=yes
+
*Kernel Crash Fix (2/24/2009)
REORDER_HDR=no
+
**[[Hardware Issues History]]
GATEWAY=132.177.88.1
 
=== /etc/sysconfig/network-scripts/ifcfg-farm ===
 
DEVICE=farm
 
BOOTPROTO=none
 
TYPE="GRE Tunnel"
 
DEVICETYPE=gre
 
ONBOOT=no
 
USERCTL=no
 
 
MY_IPADDR=
 
PEER_IPADDR=132.177.88.183
 
PEER_PRIVATE_NET=10.0.0.0/24
 
=== /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
 
  
[[:Category:Network]]
+
*Hard Drive Enclosure Replacement (12/19/2009)
 +
**[[Hardware Issues History]]
 +
'''Important Note:'''
 +
  If this appears while booting:
 +
    request_module: runaway loop modprobe binfmt-464c
 +
  This is an indication that a drive (in the supermicro hot swap bay) is plugged in that
 +
  can't be mounted, like a drive with a software raid setup on it, so just pull the drive
 +
  and reboot and it should boot properly.

Latest revision as of 15:11, 12 March 2015

General Information

Lentil performs backups. Its autofs is configured to mount harddrives labeled npg-daily-XX onto /mnt/npg-daily/XX where XX is a label number. Its backup script needs further investigation to determine exactly how it works.

As of Feb. 15, 2015 Lentil is mounted with the following which will last us awhile:

  • /dev/sdd1 mounted at /mnt/npg-daily/51; A filled 2TB hard drive
  • /dev/sda1 mounted at /mnt/npg-daily/52; A 4TB hard drive
  • /dev/sdc1 mounted at /mnt/npg-daily/53; A 4TB hard drive
  • /dev/sdb1 as the root file system. Don't hot swap this.

Hardware Information

 Motherboard: Asus P5QL-CM
   Specifications: Specifications
   User Manual: V2.pdf Users Manual
 Memory: 2 GB DDR2


Authentication

Lentil authenticates against the LDAP server running on Einstein, by connecting to einstein.farm.physucs.unh.edu using sssd. Previously, Lentil went on the UNH network to einstein.unh.edu, but this is blocked (I think by ip-tables). The farm network is the better choice anyhow.

Network Configuration

Currently connected to farm networks via our switch and a direct port to UNH network. Note: Previously, lentil went through the switch and a VLAN network. New network policy at UNH makes this not possible.

eth0
  Hostname: lentil.farm.physics.unh.edu
  HWaddr 00:30:48:63:BB:40
  IP:10.0.0.250
eth1
  Hostname: lentil.unh.edu
  HWaddr 00:30:48:63:BB:41
  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-current
/mnt/npg-daily/xx/

All backup related scripts are:

 /etc/auto.npg-daily
 /usr/local/bin/rsync_backup.py
 /etc/cron.daily/0rsync_backup
 /usr/sbin/vgcfgbackup
 /etc/rsync-backup.conf

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

If Lentil isn't sending e-mails

Sometimes after a reboot Lentil won't send its regular e-mail reports. To fix this you simply need to restart sendmail. Be aware that it has saved all of those messages it didn't send, and once sendmail is working you'll get all of them at once.

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

Fixes

Important Note:

 If this appears while booting:
   request_module: runaway loop modprobe binfmt-464c
 This is an indication that a drive (in the supermicro hot swap bay) is plugged in that 
 can't be mounted, like a drive with a software raid setup on it, so just pull the drive 
 and reboot and it should boot properly.