Worklog

[Installations] Cyrus, Perdition, LDAP

I got Cyrus working again on Solaris, as per entries last spring. Not terribly difficult. The harder part was getting Perdition, the IMAP/POP3 proxy, working. There are some source code errors that made the build on Solaris tricky.

• Don’t build Perdition with the daemon map option. It requires the mkdtemp(3) library call, which isn’t available on Solaris.

• Don’t build Perdition static like the documentation tells you to for Solaris. It will always try to load a dynamic library, but static builds don’t provide dynamic libs.

• There is an error in the LDAP initialization routines. #if 0 the code that calls ldap_initialize and just let it call ldap_init. The author said the fix would be in the next release sometime last fall, but no such release seems to be forthcoming.

• Installation: Perdition is set to listen on the third network interface, which is set to mailproxy.earlham.edu, a different IP address from the first interface. That way the LDAP attribute can be the hostname of the local box without having to mess around with alternate ports for Cyrus. Cyrus listens on the bge0 interface, while Perdition listens on bge2 and then contacts bge0 if LDAP tells it to.

Once installed, there have to be individual Perdition processes for each protocol: IMAP, POP3, IMAPS, and POP3S. They each use different config files and PID files. Once up and running, it does work flawlessly, and changing the mailHost attribute in LDAP points Perdition to the right place.

[Installations] SULA, Big RAM

Got SULA installed, mostly, and Aaron’s taking it over now. It’s got 8GB of RAM, which entailed turning on the PAE extensions for FreeBSD’s kernel. And that entailed making a static kernel, which entailed compiling in the IPFilter stuff. All is well now, and MySQL is up and running for development work.

Off the top of my head, MySQL will be used for:

• Moodle (PostgreSQL just isn’t working out there, since some of the developers can’t seem to write database-neutral SQL code).

• Cascade content management server

• MovableType

There will probably be other things coming down the pike that could benefit from a MySQL install.

[Installations] Lumana and Jumpstart tweaks

There were still a few bugs in the SVM script that I was tweaking the other day, but I got them worked out, jumpstarted Lumana, and things are pretty good now.

The new SVM script creates MD device names based on the raw devicce name of the slice and only deals with mirrored setups:

cNtXdYsZ becomes dXZ, throwing out the controller number (we’re assuming that all install disks are on the same controller) and the disk LUN number (we’re assuming that there’s only the one). So a mirror of c1t0d0s7 and c1t1d0s7 has submirror devices of d7 and d17. The meta device container for the two is taken from 7 plus the target number of the second disk: here, 7+1, and then the slice number is the ones place. So the container for this would be d87.

I did this for Lumana, because it came with 4 disks, and I wanted to mirror the second pair as well. They’re on c1t2d0sN and c1t2d0sN, so they’re made of meta devices d30 and d40, with a container of d100 (only the first slice, 0, is used).

Need to add NetBackup and possibly the Forte compiler set to Lumana, and I’ll be done with it.

[Installations] Jumpstart and V440

The Solaris 9 version we had on ROJ was too ancient to support the new V440, so when it tried to boot in Jumpstart, it failed. Updating the Solaris version in the Jumpstart area has always been a pain; something about the script seemed to always bomb out on ROJ, requiring editing of the script and running it from somewhere other than the CD. Fortunately, Doug Hughes clued me in to the fact that all I had to do was copy the Solaris_9 directory contents from the DVD into the expected place in the Jumpstart area, and all would be good.

Next up, though, is making my volume manager Jumpstart script work with four disks. It’s always assumed two disks for a simple mirroring setup, but the V440 has four, and I’d like to add those in to the mix at Jumpstart time, too. I think I got it working now — now that I’ve removed a couple of lines of stale code that were causing a test bug and leaving the system in a pretty sad state. To test it all tomorrow.

[Installations] SANs and LUNs and devices, oh my...

Once you tell the ITMPT driver in Solaris that it can access more than the first LUN on a fibre channel device, mapping out the SAN makes a lot more sense.

I’ve got the SAN mapped out by Solaris and VMware device names over in the TWiki. I’m not entirely certain what happens to the device mappings if we add another FC target device to the SAN (like, say, the original Xserve RAID), but I suspect that if we just add it to the next available ports on the switches it’ll be ok.