Server Rebuild Info

From WittleNet

Jump to: navigation, search

Contents

Rebuild of Wittle.net

As you may have read, wittle.net suffered a hard disk crash that took it down for a couple of weeks. As an experience information systems professional, I was sure I didn't need backups. Oops. Anyway, this page documents the steps I took to rebuild the system with a new hard drive.

Install RHEL4 Update 1

Fairly straightforward.

eth0: 
  IP: 24.172.62.206 
  SN: 255.255.255.252
  GW: 24.172.62.205
  NS1: 24.25.4.106
  NS2: 24.25.4.107
eth1:
  IP: 10.3.1.1
  SN: 255.255.0.0
Hostname: wittle.net

Make sure to install apache development tools, because that's where apxs is, which is required to build the apache tomcat connectors.

Build mod_jk2 since binaries for RHEL4 are not available

 Download & untar source
 cd jakarta-tomcat-connectors/jk/native2
   ./configure --with-apxs2=/your/path/to/apxs
   make
   cd ../build/jk2/apache2
   apxs -n jk2 -i mod_jk2.so

Backup Drive

I'm using my external USB drive to back up the new configuration. I just finished creating the filesystem on it; here's the info (especially interested in the backup superblock info).

 mke2fs 1.35 (28-Feb-2004)
 Filesystem label=
 OS type: Linux
 Block size=4096 (log=2)
 Fragment size=4096 (log=2)
 15007744 inodes, 30013428 blocks
 1500671 blocks (5.00%) reserved for the super user
 First data block=0
 Maximum filesystem blocks=33554432
 916 block groups
 32768 blocks per group, 32768 fragments per group
 16384 inodes per group
 Superblock backups stored on blocks: 
       32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
       4096000, 7962624, 11239424, 20480000, 23887872

UPS

I keep having to fix up my ups monitor after a reboot:

 kill upsmon
 kill upsd
 chmod 0600 /dev/ttyS0
 chown nut:nut /dev/ttyS0

Then the commands in rc.local for the ups.

Printing

After configuring shared printing in the RHEL4 GUI, could not get printing from clients to work.

 lpstat -h <hostname>

returned

 lpstat: get-jobs failed: client-error-forbidden

This failed with the same error on the server, so it didn't appear to be a client problem.

Solution involved adding 631 as open port for TCP in the firewall configuration (probably only required for my testing, but I left it open), and go into cupsd.conf and allow eth1 for ALL configuration sections. Basically, I added

AuthType None
Allow from @IF(eth1)

to each of the <Location></Location> tags that were uncommented and these didn't already exist. I also enabled port 631 in the RHEL4 firewall for TCP (the UDP line was added when I set the printers up to be shared in the GUI).

This was the only way I could get things to work, and ipp still didn't work; I fell back to lpd as the printing protocol.

The major title below is so that Wikid marks this up well so that other people can find it.

client-error-forbidden

RHEL4

cups

Personal tools