Boggles

| | Comments (0) | TrackBacks (0)

I came into work this morning and my graveyard coworkers had a problem. They had four new servers installed in the data center all running the new $COMPANY approved version of Red Hat Linux, and they couldn't ssh to the machines. The problem felt familiar, and after trying to log in my self I was pretty sure I had seen this before, but I couldn't remember when or where. Was this something wrong with PAM or OpenSSH?

We've used this version of Red Hat on a few previous projects so I began looking around on our Wiki and starting the excruciating exercise of "Advanced" Find in LookOut. With in about two minutes I had found the answer on the Wiki. The standard $COMPANY sshd_config has some options off that we use.

So I had seen this problem before. In fact I had even documented the existence of this problem and how to fix it. THANK YOU WIKI.

After demonstrating that this problem shouldn't have taken eight hours to fix, one of the graveyard Systems Administrators (a term I use loosely) said that the documentation was "incomplete". I hadn't included that sshd needed to be restarted and how to do it. The reason I hadn't documented it was that if you were qualified to do this job you would know that this needed to be done.

At this point I almost lost it. Instead I went to get some coffee, and find a dart board.


0 TrackBacks

Listed below are links to blogs that reference this entry: Boggles.

TrackBack URL for this entry: http://blog.sf.dasbistro.com/mt-tb.cgi/62

Leave a comment

About this Entry

This page contains a single entry by Sam Phillips published on April 3, 2007 10:59 AM.

Semiregular Baby Post 2! was the previous entry in this blog.

Python Woe is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

February 2008

Sun Mon Tue Wed Thu Fri Sat
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29  

Pages

Powered by Movable Type 4.1