The Linux and Unix Menagerie

Hey there,

Just wanted to let everyone know that the site move is starting to come along somewhat nicely (you'd be amazed at how much of a PITA having a decent site page cross-linking setup can be when moving between two completely different platforms). It's my hope that, by the end of this week, we'll be broadcasting in stereo with the new site up in "beta" form (we skipped alpha; it was slowing us down ;). When that happens, I'll be sure to email everyone, who requested to be notified, with the new site address. For, give or take, two weeks after that, we'll be publishing at both locations simultaneously while we work out all the bugs we spent so many hours working in ;) There will be no link directly from this blog to the newer version of the blog and (if the spiders and robots honor our requests to not index any pages, follow any links, or even recognize our new site) we, hopefully, won't end up getting slammed for duplicate content.

Just wanted to let everyone know that the site move is starting to come along somewhat nicely (you'd be amazed at how much of a PITA having a decent site page cross-linking setup can be when moving between two completely different platforms). It's my hope that, by the end of this week, we'll be broadcasting in stereo with the new site up in "beta" form (we skipped alpha; it was slowing us down ;). When that happens, I'll be sure to email everyone, who requested to be notified, with the new site address. For, give or take, two weeks after that, we'll be publishing at both locations simultaneously while we work out all the bugs we spent so many hours working in ;) There will be no link directly from this blog to the newer version of the blog and (if the spiders and robots honor our requests to not index any pages, follow any links, or even recognize our new site) we, hopefully, won't end up getting slammed for duplicate content.

For everyone who's wondering; yes, that second paragraph was exactly the same as the first. It was a cheap duplicate-content joke, I admit, and only funny if you're into movies like Airplane and The Naked Gun . I can't get enough of that kind of humour. Alas, it's not for everyone. Pardon my indulgence. ...and feel free to copy and paste that paragraph all over the Internet ;) In any event, if the posts get a little strange(r) this week, it's because my mind's on setting up the whole new site while still trying my hardest not to go soft on the posts. I could do a whole week of showcasing other people's stuff, but it just wouldn't seem right. I am serious ...And don't call me Shirley ;)

This week's Monday script (written in ksh because I write everything in bash now and I could swear it used to be my favorite shell ;) is fairly simple in concept, and can actually be used to monitor pretty much any product composed of a set of processes (or, just any process), with minor modifications. For our purposes, today, we're using it to keep the Oracle DBA's up all night getting pages about every burp and hiccup the database manages to spit and sputter out. Although this script does serve a sinister purpose, as a side effect, it's not meant to equalize the amount of time sys-admins and DBA's spend waking up at odd hours of the night to investigate issues (whether they be actual issues or not ;). This script was written, very simply, to make sure that the DBA's know when there may be a problem with their DB's. If the databases' uptime is only an issue during the day, just don't include the evening hours when you throw this thing into your crontab :)

There's only one prerequisite to running this script, which I didn't want to actually put in the script (although it could be done if I were able to think more clearly). Before you put this script into your crontab, or just run it manually, execute the following at the command line (Assuming you're logged in as oracle and have all the standard environment variables set and populated):

host # grep "[O]RA-" $ORACLE_BASE/admin/$ORACLE_SID/yourDumpDir/alert_$ORACLE_SID.log > $ORACLE_BASE/admin/$ORACLE_SID_alert.prev

This will ensure that you create the basic file that this script checks, initially, when you run it the first time (and every time after that). I decided to do that one step manually, since it keeps down on the clutter. Plus it ensures that this simple check doesn't bother you about an error that happened last week. My actual vision, at this point, is much worse than 20/20, and the way I actually implement this is to run the above command line every night at 23:59 in cron, with the monitoring script running every 15 minutes all day, every day ;)

For everyone who's wondering; yes, the bad jokes will get worse as I grow tired and begin to hallucinate from sleep deprivation over the course of the next few weeks ;) Expect more typos thAn uzual, two ;)

The script also expects that you have the files .dbaoncall and .dbaemail set up (the script can be retooled to have these files located wherever you'd like and called whatever you'd prefer - or, if you're working on a smaller site, you could just include the information, that you would put in these files, in the script itself). Basically, the .dbaoncall file would contain a list of one or more cell-phone/pager email addresses and the .dbaemail file would contain a list of one or more standard email addresses, for notification purposes.

Here's hoping this script helps you out in some way (even if it just makes you feel better about that Oracle monitoring script you wrote yourself, but were having doubts about until you had a look at this incredibly inferior piece of work ;) - Also, for those of you who are curious about the format of the "grep" lines, check out our old post on keeping grep out of your grep output . <-- There's another cross-link I'm going to have to reconcile... When will I learn?!?!?! :)

Cheers,


Creative Commons License


This work is licensed under a
Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License

#!/bin/ksh

#
# oralert.sh - Consult the great Oracle and, perhaps, find out what's wrong ;)
# Double check the values of all variables as these represent a standard setup structure that may not agree with yours!
#
# 2009 - Mike Golvach - eggi@comcast.net
#
# Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License 
#

. /usr/local/bin/oraenv

LOGFILE=$ORACLE_BASE/admin/$ORACLE_SID/yourDumpDir/alert_$ORACLE_SID.log
PREV=$ORACLE_BASE/admin/"$ORACLE_SID"_alert.prev
CURR=$ORACLE_BASE/admin/"$ORACLE_SID"_alert.curr

DBAONCALL=`cat $ORACLE_BASE/admin/.dbaoncall`
DBAEMAIL=`cat $ORACLE_BASE/admin/.dbaemail`
SENDMAIL=/usr/lib/sendmail # Change to /usr/sbin/sendmail if necessary
SCHEMA="prd_schema" # Change this to your schema name

grep "ORA-" $LOGFILE > $CURR

if ! diff $PREV $CURR
then 
 ERR=`diff $PREV $CURR` 
 print $ERR > $ORACLE_BASE/admin/alertlogerr.`date +%b%e%T`
 print "Subject: `hostname` $ORACLE_SID alert_log error \n$ERR" | $SENDMAIL $DBAEMAIL
 print "Subject: `hostname` $ORACLE_SID alert_log error \n$ERR" | $SENDMAIL $DBAONCALL
 cp $CURR $PREV
fi

if ! ps -ef |grep $SCHEMA|grep "[o]ra_dbw"
then 
 print "Subject: ERROR ON `hostname` DBWR is down" | $SENDMAIL $DBAEMAIL
 print "Subject: ERROR ON `hostname` DBWR is down" | $SENDMAIL $DBAONCALL
fi

if ! ps -ef |grep $SCHEMA|grep "[o]ra_lgwr"
then 
 print "Subject: ERROR ON `hostname` LGWR is down" | $SENDMAIL $DBAEMAIL
 print "Subject: ERROR ON `hostname` LGWR is down" | $SENDMAIL $DBAONCALL
fi

if ! ps -ef |grep $SCHEMA|grep "[o]ra_arc"
then 
 print "Subject: ERROR ON `hostname` ARC is down" | $SENDMAIL $DBAEMAIL
 print "Subject: ERROR ON `hostname` ARC is down" | $SENDMAIL $DBAONCALL
fi

if ! ps -ef |grep $SCHEMA|grep "[o]ra_pmon"
then
 print "Subject: ERROR ON `hostname` PMON is down" | $SENDMAIL $DBAEMAIL
 print "Subject: ERROR ON `hostname` PMON is down" | $SENDMAIL $DBAONCALL
fi

if ! ps -ef |grep $SCHEMA|grep "[o]ra_smon"
then 
 print "Subject: ERROR ON `hostname` SMON is down" | $SENDMAIL $DBAEMAIL
 print "Subject: ERROR ON `hostname` SMON is down" | $SENDMAIL $DBAONCALL
fi

Posted by Mike Golvach at 12:40 AM  

database, grep, linux, monitor, oracle, sid, site news, unix

Hey there,

Here comes another Expect monster-sized weekend script for you ;)

Today's script is a twist on a previous script we posted to do network wide updates. The essence is still the same. This should basically save you the hassle of having to log in to a million different servers to find and remove users who you know shouldn't have accounts on your boxes.

Again, you can also delete the "Weed out the undesirables pronto" section if you don't want to minimally secure the script from unauthorized usage by doing a logname check.

We've left out the login functionality for Linux this time, but we'll add it tomorrow as a "diff -c" patch file and add it to this file with "patch" to give the week an appropriate finish :)

There's a section I wrote specifically for an Informix sql database, that you can modify (or remove) if you like, to include an example of how to check for users (or anything, really) in a database. If you don't want or need that functionality, just delete the "$userlogin mail server sql user report:" section. All the sections are highlighted with tons of pound signs (#)

Once you edit this Expect script to suit your needs, you can run it easily, like so (with -h if you want to see the help screen):

Ex:
host # ./eraser

or

host # ./eraser -h

See you tomorrow with the Linux additions. Have a great weekend :)


Creative Commons License


This work is licensed under a
Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License

#!/usr/local/bin/expect

log_user 0 

#########################################################################
# eraser - root out ex-employees across network
# 2008 - Mike Golvach - eggi@comcast.net
# Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License 
# 
# Usage: eraser <-h> [User Login] [Your Login]
#########################################################################

#########################################################################
# Weed out the undesirables pronto
#########################################################################

set gauntlet [exec logname]
if { [string compare $gauntlet "user1"] != 0 && [string compare $gauntlet "user2"] != 0 } {
 puts "Sorry, $gauntlet. You may not use eraser."
 exit
} 

#########################################################################
# Go for the help short-circuit
#########################################################################

foreach member $argv {
 if { $member == "-h" } {
 puts "#############################################################################"
 puts "USAGE:"
 puts " $argv0 <-h> \[User Login\] \[Your Login\]"
 puts "#############################################################################"
 puts "SCO Hosts:"
 puts " sco1 sco2"
 puts "SUN Hosts:"
 puts " sun1 sun2"
 puts "HP Hosts:"
 puts " hp1 hp2"
 puts "#############################################################################"
 puts "FLAGS:"
 puts " -h: Show this message."
 puts " User Login: Theirs."
 puts " Your Login: Yours."
 puts "#############################################################################"
 puts "A FEW VALID COMMAND LINE EXPRESSIONS:"
 puts " $argv0 -h"
 puts " \(The -h command invalidates all others\)"
 puts " $argv0 userlogin yourlogin"
 puts " \(The Regular Way\)"
 puts "#############################################################################"
 exit
 } elseif { [string match -* $member] == 1 } {
 puts "Usage: $argv0 <-h> \[User Login\] \[Your Login\]"
 exit
 }
}

#########################################################################
# Generic login procs divided by architecture
#########################################################################

proc sun_login {tprompt login lpass} {

 set timeout 3
 set prompt $tprompt
 set qlogin $login
 set qpass $lpass

 expect "ogin: " {send "$qlogin\r"}
 expect "word: " {send "$qpass\r"}
}

proc hp_login {tprompt login lpass} {

 set timeout 12
 set prompt $tprompt
 set qlogin $login
 set qpass $lpass

 expect "ogin: " {send "$qlogin\r"}
 expect "word:" {send "$qpass\r"}
}

proc sco_login {tprompt login lpass} {

 set timeout 6
 set prompt $tprompt
 set qlogin $login
 set qpass $lpass

 expect "ogin: " {send "$qlogin\r"}
 expect "word:" {send "$qpass\r"}
 expect -re $tprompt {send "\r"}
}

#########################################################################
# passwd and mail aliases groper procs by architecture
#########################################################################

proc sunhp_q {tprompt login lpass userlogin host} {
 set timeout 5
 set log $login
 set opass $lpass
 set prompt $tprompt
 set ulogin $userlogin
 set hostname $host
 set insidealias none
 set insidepwd none

 send_user "Scanning $hostname... "

 expect -re $tprompt {send "grep $ulogin /etc/passwd\r"}
 expect -re $tprompt
 send "echo $?\r"
 expect -re "\r\n(.*)\r\n"
 set returnval $expect_out(1,string)
 if { $returnval == 0 } {
 set insidepwd 1
 }
 expect -re $tprompt {send "grep $ulogin /etc/mail/aliases\r"}
 expect -re $tprompt
 send "echo $?\r"
 expect -re "\r\n(.*)\r\n"
 set returnval $expect_out(1,string)
 if { $returnval == 0 } {
 set insidealias 1
 }
 expect -re $tprompt {
 send "exit\r"
 }
 return "$hostname $insidepwd $insidealias"
}
 
proc sco_q {tprompt login lpass userlogin host} {
 set timeout 5
 set log $login
 set opass $lpass
 set prompt $tprompt
 set ulogin $userlogin
 set hostname $host
 set insidealias none
 set insidepwd none

 send_user "Scanning $hostname... "

 expect -re $tprompt {send "\r"}
 expect -re $tprompt {send "grep $ulogin /etc/passwd\r"}
 expect -re $tprompt
 send "echo $?\r"
 expect -re "\r\n(.*)\r\n"
 set returnval $expect_out(1,string)
 if { $returnval == 0 } {
 set insidepwd 1
 }
 expect -re $tprompt {send "grep $ulogin /usr/mmdf/table/alias.user\r"}
 expect -re $tprompt
 send "echo $?\r"
 expect -re "\r\n(.*)\r\n"
 set returnval $expect_out(1,string)
 if { $returnval == 0 } {
 set insidealias 1
 }
 expect -re $tprompt {
 send "exit\r"
 }
 return "$hostname $insidepwd $insidealias"
}

#########################################################################
# The main process loop
#########################################################################

#########################################################################
# Check command line args
#########################################################################

if { [llength $argv] < 2 } {
 puts "Usage: $argv0 <-h> \[User Login\] \[Your Login\]"
 exit
}

#########################################################################
# Set list of servers, passwords and other globals
#########################################################################

set sun [list sun1 sun2]
set sco [list sco1 sco2]
set hp [list hp1 hp2]

set userlogin [lindex $argv 0]
set login [lindex $argv 1]
set tprompt "(%|#|\\\/|\\\$|\\\/|\\\/\\\/#|mgolvach|\\\)|\\\>|\\\}) ?$"

#########################################################################
# Grab user password.
#########################################################################

send_user "Enter your login password : "
stty -echo
expect -re "(.*)\n"
stty echo
set lpass $expect_out(1,string)

send_user "\n"

#########################################################################
# Do It To It.
#########################################################################

foreach host $sun { 
 spawn telnet $host
 sun_login $tprompt $login $lpass
 lappend finalists [sunhp_q $tprompt $login $lpass $userlogin $host]
}

foreach host $hp {
 spawn telnet $host
 hp_login $tprompt $login $lpass
 lappend finalists [sunhp_q $tprompt $login $lpass $userlogin $host]
}

foreach host $sco {
 spawn telnet $host
 sco_login $tprompt $login $lpass
 lappend finalists [sco_q $tprompt $login $lpass $userlogin $host]
}

puts ""
puts "#################################################################"
puts "$userlogin is a valid user on the following machines:"
puts "#################################################################"
set counter 0
foreach item $finalists {
 if { [lindex $item 1] == 1 } {
 incr counter
 puts [lindex $item 0]
 }
}
if { $counter == 0 } {
 puts "No valid accounts found for $userlogin"
}
puts "#################################################################"
puts "$userlogin has mail alias entries on the following machines:"
puts "#################################################################"
set counter 0
foreach item $finalists {
 if { [lindex $item 2] == 1 } {
 incr counter
 puts [lindex $item 0]
 }
}
if { $counter == 0 } {
 puts "No alias file entries found for $userlogin"
}
puts "#################################################################"
puts "$userlogin mail server sql user report:"
puts "#################################################################"
set counter 0
set squealer [open "|isql userdb 2>/dev/null >/tmp/tattle1.tmp" w]
puts $squealer "select * from mail_users where mail_user_id = \"$userlogin\""
close $squealer
set stooly [open "/tmp/tattle1.tmp"]
while {[gets $stooly buffer]!=-1} {
 if { [string match *$userlogin* $buffer] == 1 } {
 puts "Mail Dir : $buffer"
 incr counter
 } 
}
if { $counter == 0 } {
 puts "No Mail Dir entries found for $userlogin"
}
system "rm /tmp/tattle1.tmp"
puts "#################################################################"
puts "$userlogin excess files and directories found on mail server"
puts "#################################################################"
set counter 0
if { [file exists "/var/mail/$userlogin"] == 1 } {
 incr counter
 puts "File: /var/mail/$userlogin"
}
if { [file isdirectory "/var/imsp/user/$userlogin"] == 1 } {
 incr counter
 puts "Directory: /var/imsp/user/$userlogin"
}
if { $counter == 0 } {
 puts "No excess mail server files found for $userlogin"
}
puts "#################################################################"
puts "DON'T FORGET TO:"
puts " 1. Do this".
puts " 2. Do that."
puts " 3. Do everything else."
puts "#################################################################"

exit

Posted by Mike Golvach at 12:11 AM  

database, expect, informix, linux, remove, script, sql, unix, users

• ▼ 2011 (1)
  • ▼ January (1)
    • Updated Post: Arbsorption Of Knowledge In The Com...

• ► 2010 (2)
  • ► December (1)
  • ► January (1)

• ► 2009 (179)
  • ► June (28)
  • ► May (31)
  • ► April (30)
  • ► March (31)
  • ► February (28)
  • ► January (31)

• ► 2008 (366)
  • ► December (31)
  • ► November (30)
  • ► October (31)
  • ► September (30)
  • ► August (31)
  • ► July (31)
  • ► June (30)
  • ► May (31)
  • ► April (30)
  • ► March (31)
  • ► February (29)
  • ► January (31)

• ► 2007 (101)
  • ► December (36)
  • ► November (36)
  • ► October (25)
  • ► September (4)