29-Sep-2008

Fixing things

I patched a couple of Alphaservers up-to-date yesterday afternoon, including updating the SRM firmware, which was a tad out of date. On reboot, I was surprised to see a bunch of audit messages appearing when TCP/IP Services attempted to restart. The audit messages were indicating that a number of services were experiencing problems attempting to create log files or read configuration files in their service-specific directories.

Once the machines were up, I started investigating, and found that nearly every directory associated with these services was owned by the incorrect user. I hurriedly set the file ownerships, and restarted the affected services.

I'd love to know how this got screwed up, and more interestingly, how it worked (or didn't) and got fixed at the last boot.

Unfortunately, the consoles here are not connected to a permanent recording device, so historical research is a little difficult.

Posted at September 29, 2008 6:28 PM
Tag Set:
Comments

Rings a bell ...
* Move SYSUAF and RIGHSTLIST off their default positions (Copy the files and redefine the logicals)
* Add users and identifiers
* Do anything to the system
* reboot

and THEN discover you did it all by hand and forgot to incorporate the changes and additions in your startup sequence...

If it wasn't you did it, and the preson that did all this has left, it's quite a challenge to get things right again.

That's a price to pay if you don't need to reboot so often

Posted by: SYSMGR at September 30, 2008 6:10 PM

I'd have to guess that's exactly what happened. But it must have entailed renaming/modifying identifiers or some such. And you're right, I inherited it...

Posted by: Jim Duff at September 30, 2008 10:54 PM

Comments are closed