Most data on PAX is slowly migrating to RAHU. Home directories were completely migrated just prior to fall semester, 2004. We are in the process of migrating groups directories to RAHU as well.
I updated ProFTPd last night to 1.2.8. Most operations are working well, however the SSL/TLS code has changed and the configuration directives probably need tweaking to make it work.
This was partly in response to the ISS security alert for ProFTPd. It also gets a more up to date daemon with other bugfixes and enhancements.
OpenSSH has been upgraded on all the FreeBSD servers to the latest openssh-portable package, correcting the vulnerabilities discovered last week.
FreeBSD 4.4 packages were installed on HEIWA, KE, and SHANTI. A FreeBSD 4.7 package was installed on PAX. These are all openssh-portable-3.6.1p2_3. They install into /usr/local and require the following changes to /etc/rc.conf:
sshd_program="/usr/local/sbin/sshd"
sshd_flags="-f /etc/ssh/sshd_config"
PAX is the only server that currently required these changes, as the others had previously been upgraded to OpenSSH-portable. PAX also required minor changes in the /etc/ssh/sshd_config file.
After booting this morning, PAX complained of bad memory and failing drives on the PowerVault array.
We took out the first four 256MB DIMMs and moved the remaining four into the first slots. The first four came with the system and the remaining four were added some time later. It was happy with the memmory at that point, but the PV drives were still unhappy.
The PERC BIOS claimed that drives 3 and 5 on the PV220S were “different” somehow, and put the container into critical. This was unacceptable, since there were no alert indications on the PowerVault unit itself and two drives out of a RAID-5 system is bad news. Poking at the PERC BIOS didn’t seem to change things. We talked with Dell tech support for quite a while, during which they had us verify the drives from the PERC BIOS. The two “failed” drives were fine, but drive 8 had a couple of bad sectors. We left tech support with the suggestion to upgrade the PERC firmware and see if that made a difference. If not, our only hope was to delete the container, recreate it, and restore from tape.
Upgrading to version 2.7 of the PERC BIOS changed the error. Now it stated that drive 8 (the one with bad sectors) was changed or missing, or somesuch. It allowed us to verify the drive and start a rebuild of the array. The rebuild is currently ongoing and the data is intact.
Update
The PowerVault array finished rebuilding successfully at approximately 7:00 AM Sunday morning.
Upgraded Samba on all systems except MIR on Friday morning.
PACO and ROJ are using Sunfreeware.com packages (requires the popt package). All others are using FreeBSD packages built on my workstation.
On installation on SHANTI, it somehow overwrote all individual entries in the smbpasswd file such that passwords were null and accounts were disabled. Restored from previous night's backup.