Main

September 22, 2004

gs.vbs/Backups

  • Coded up gs.vbs, which will dump out the group heirarchy, whenever that arrives
  • Resolved the lockvobs.pl for backup issue - now working!
  • Spoke with server guy about new server's configuirations. Rtnlprod04 & 5 should be available by Monday!
  • Worked with Adam trying to get his login working

September 21, 2004

Group structure/View Server Problems

  • Finished designing group structure - about to make AD requests
  • View server had a problem again. More and more it seems to be a problem with the NIC card on rtnlprod02. Managed to log into rtnlprod02 and look around. Couldn't see any processes at all in the TaskManager even though the 4 CPUs were 70-90% busy! Couldn't look at the Network tab - said there was no network adapter. Additionally the following appeared in the System event log:

    Event Type:	Error
    Event Source:	NIC Agents
    Event Category:	Service 
    Event ID:	1285
    Date:		9/21/2004
    Time:		2:07:32 PM
    User:		N/A
    Computer:	RTNLPROD02
    Description:
    NIC Agent: Connectivity has been lost for the NIC in slot 0, port 1. [SNMP TRAP: 18006 in CPQNIC.MIB]
    Data:
    0000: 00 00 06 00 00 00 00 00   ........
    0008: 01 00                     ..      
    

September 20, 2004

cmconfig.vbs

Held code review for cmconfig.vbs. Spent the rest of the day implementing changes. Some changes were minor while a few others were good catches of possible problems.

September 16, 2004

Finished up populate_groups.vbs

  • Investigated the group structure to document that is it not really heirarchical. We need to get it more tree like
  • Finished up coding populate_groups.vbs. Code now will walk the tree (that is when we get a tree!) and add users to the TOOLS database including their groups, gathered from walking the tree. If we do not have a tree to walk then the groups will be incomplete. Similarly if we tell populate_groups to populate from a node in the tree then only the groups in that node down will be gathered properly.

September 15, 2004

Populate users

  • Worked mainly on a script to backfill and populate users into the TOOLS database
  • View server acted up again. Rebooted it but then it didn't come up! Got the server guys involved and they booted it to the Last Known Good Configuration. This means that the Server Heap Size registry tweaks have been backed out. This also means that we'll probably have the view server having problems again soon. We need to schedule a maintainance period to reboot the view server with the proper registry tweaks. I can't imagine that that setting caused a problem with rebooting as it's the same setting as rtnlprod01 which is the same hardware. I looked at the event log a little bit and I think that rtnlprod02's problems may be a failing NIC card. I guess time will tell...

September 14, 2004

Code complete for cmconfig.vbs

Working mainly on cmconfig.vbs. Solution for the env problem was to set both the user environment and the process environment then call cmverfiy.cmd from cmconfig.vbs. The code now does the folowing:

  1. Configure Clearquest using installutil
  2. Verify connection to Clearquest
  3. Connect to the TOOLS database and verify that the user exists there
  4. Verify the user is in the proper Clearcase Active Directory group
  5. Set CLEARCASE_PRIMARY_GROUP and CLEARCASE_GROUPS properly for the user based on the users TOOLS record
  6. Set the Clearcase region as per the user's TOOLS record
  7. Configure user's Clearquest email settings
  8. Add registry entry to execute PMO-CM.cmd
  9. Add registry entry indicating the version of this script that was used
  10. Update the following fields in the user's record in the TOOLS database:
    • machineName (set to hostname if machineName was blank or set to "My Computer" or "Unknown")
    • machineName2 (set to hostname if machineName was NOT blank or set to "My Computer" or "Unknown")
    • idAddedtoCC (if #4 succeeds)
    • isDeployed (if no other errors occur)
    • isAddedtoCQ (if #3 succeeds)
  11. Runs cmverify to verify that all is OK

September 13, 2004

Env var problems

There is a slight problem with the "set everything and verify it" script cmconfig.cmd. The idea was that that one script would perform 3 separate actions:

  1. Set up Clearquest configuration parameters (installutil)
  2. Set up Clearcase configuration parameters (as per the logged in user) (setccconf.vbs)
  3. Verify the installation (cmverify.cmd)

The problem is with #2 being VBScript and #3 happening as a result of executing from the cmconfig.cmd script. While setccconf.vbs does indeed set the proper configuration environment variables as soon as it ends those settings are no longer set anymore by the evoking script only. All other (new) processes know about the change to the environment variables. To illustrate this odd phenomena:

$ type setenv_var.vbs
Set sh  = WScript.CreateObject ("WScript.Shell")
Set env = sh.Environment ("USER")

env ("foo") = "bar"
$ type senenv_var.cmd
@echo off
set foo=bar
$ echo foo = %foo%
foo = %foo%
$ cscript setenv_var.vbs
$ echo foo = %foo%
foo = %foo%
$ call setenv_var.cmd
$ echo foo = %foo%
foo = bar
$ cmd /c echo foo = %foo%
foo = bar

Why it works for a .cmd script but not for a .vbs script I don't know.

So I will change cmconfig.cmd to do #1 and #2 above but skip #3. This means two things:

  1. Customers will have to run cmconfig.cmd first, then cmverify.cmd second
  2. The running of cmverify.cmd must be done in a separate, new cmd session

The reason for #2 is that even after cmconfig.cmd is run environment variables such as CLEARCASE_PRIMARY_GROUP and CLEARCASE_GROUPS will not have been "exported" into that cmd's environment (unless somebody can tell me how to set the parent's environment variables from VBScript...).

For the point and click crowd this should be OK. The email message you send the customer should have two links: one to cmconfig.cmd and one to cmverify.cmd. If the customer clicks the cmconfig.cmd link then cmconfig.cmd should run, in it's own process, and go away. Subsequently if the user clicks on cmverify.cmd that will run in it's own cmd process and it should pick up the appropriate environment variable settings.

There have been many requests for enhancements to the configuration scripts including updating the TOOLS database on successful verification and performing additional checks such as "is this user really in the AD group". I believe I will only be able to solve the above problem by having the setccconf.vbs script actually envoke the cmverify.cmd directly so that the environment variables that setccconf.vbs just set are exported into the cmverify.cmd's environment.

September 9, 2004

Server Heap Size/Comment PINE code

  • Investigated why the view server keeps needing a reboot. Found out that the server heap size was never increased. Fixed that.
  • Coded up a new trigger called COMMENT_PINE_CODE

September 8, 2004

Fixed corrupted SQL files for BUCS

  • Fixed corrupted SQL files for BUCS

September 2, 2004

setccconf

Found that there are situations where one needs to have CLEARCASE_PRIMARY_GROUP set. Worked with Mike to implement groups in the TOOLS database. Spent a large part of today implementing setccconfig.vbs. This command will replace setregion and sets 3 things:

  • Region
  • CLEARCASE_PRIMARY_GROUP
  • CLEARCASE_GROUPS (if required)

In order to do this the username is used to retrieve information from the TOOLS database. If the username is found then we get the project record and obtain the region. Next we check CC Primary Group and CC Groups. These fields will not always be filled in (previous entries lacked them but future entries should have them filled in. We then set CLEARCASE_PRIMARY_GROUP and CLEARCASE_GROUPS if there are any.

CC Groups in the TOOLS database will contain all Clearcase groups that the user belongs to - including their Primary group. In a lot of cases the user's CC Groups will be only one and equal to the Primary group. In that case CLEARCASE_GROUPS is not set. If the user is a member of more than one group then it will be their Primary group and additional groups in the CC Groups field. In that case Primary group is removed from that list and the rest are set into CLEARCASE_GROUPS.

September 1, 2004

CLEARCASE_PRIMARY_GROUP

Worked on setccconf.vbs

August 30, 2004

Informatica/CLEARCASE_PRIMARY_GROUP

  • Rearranged Informatica script code to be more oriented to what Don needs
  • Helped William Dean with issues regarding Clearcase. I think we are all OK now so I closed the Paragrine ticket for this. This has, however, opened up the issue that CLEARCASE_PRIMARY_GROUP needs to be set in some cases

Continue reading "Informatica/CLEARCASE_PRIMARY_GROUP" »

August 26, 2004

Permissions problems

  • Spent most of the day wrestling with permissions problems. Anje was having problems as vobadm with EAG vobs in a UCM view. Attempted to recreate the problem and understand why it's not allowing her to create elements. Seems the EAG_VMS vob is owned by AsapAdm and group CC-EAG-VMS but vobadm is not the owner. vobadm is in the group and the group has write permission but vobadm can't write.
  • Started writing WSH keystroke module for the Informatica process that Don is working on

August 25, 2004

Implementing Groups

  • Noticed the CC-TTE-EMP-* groups have been created. One has the wrong name (should be CC-TTE-EMP-SCR but is CC-TTE-EMP-SRC. My fault! Typo when I requested the group). Applied these groups to the folders in Core_automation
  • Changed protect trigger to set group owner to that of the parent directory. This is needed for this fix
  • Removed Permissions trigger. This trigger was ineffective and is no longer needed

August 23, 2004

cmverify/protect

  • Changed cmverify to report username in the logfile name and in report itself
  • Changed protect trigger to use the parent directoy's group as the group owner for new elements

August 19, 2004

Group Permissions/mktriggers

  • Started documenting usage of groups within groups
  • Helped John with mktriggers modifications

August 18, 2004

Group Permissions/cmconfig

  • Wrapped up the 3 things we want to do to configure during install into a cmd script - cmconfig.cmd
  • Performed a lot of investigation regarding group permissions problem - writing web page for this

August 17, 2004

cqverify/TOOLS

  • Submitted a few task for improvements with the TOOLS database
  • Changed cqverify to deliniate between username not found and password wrong. Changed return status such that if the username is not in the Clearquest database that's an error. But if the user is in the Clearquest database but the password is not default then that's just a warning
  • Assisted TTE member to add ASAP_WinRunner to his view

August 16, 2004

Setregion/c[qc]verify

  • Implemented setregion.vbs. This command will set the region for the passed in region name. Or, if no region is given, it uses the users ID and the TOOLS database to determine that user's home region
  • Requested SQL folk to allow monitoring of SQL service
  • Changed cqverify to attempt connecting to Clearquest database using the user's username and password
  • Changed ccverify to not consider an empty CLEARCASE_PRIMARY_GROUP as an error

August 13, 2004

What'sUP/set region

  • Worked on setting up What's Up alarms and alerts
  • Created setregion.vbs. This script will set the region to the passed in region. If nothing is passed in it will attempt to find the region associated with the project for the currently logged in user through the CQ TOOLS database. If it can't find it then it will leave the registry setting alone

August 12, 2004

Tools Push

  • Spent most of the day investigating how best to solve the issue of supplying Desktop Support a group/region for a user. Started writing VBScript to interrogate the CQ TOOLS database. Have the code functionally working but we need to add Region to a Project in CQ TOOLS. Also need to orient all of our .reg files to be .reg files.
  • Implemented COMMENT_SQL_CODE trigger for BUCS_SRC

August 11, 2004

Cron problems/Server Problems/CC Groups

  • Had problems with cron not being able to find scripts
  • Spent much of the day researching whether or not we need to use CLEARCASE_PRIMARY_GROUP at all
  • View server needed rebooting

August 10, 2004

AD Groups/setup

  • Worked on trying to sort out the differences between AD groups/groups.dat and the .reg files. Need to investigate if all this is required in the first place.
  • Finished up setup_cygwin. Added links for .inputrc, .Xdefaults and .vimrc. Added stuff for verbose and debug

August 9, 2004

Env/CQ Down/Groups

  • Added more of an environment into CM_TOOLS
  • Clearquest has been down all day. Server threw a shoe. Won't be up 'til tomorrow
  • Seems we may not have a 1-to-1 correspondance between groups.dat/AD Groups and .reg files. Trying to work out the problems here

August 5, 2004

CC-TTE/CommentSQLCode/whosin

  • Had problems with the Permissions trigger. Something we forgot or didn't think about. If the user attempts to add elements to source control they should be permitted in folders that have .perms. However part of adding to source control checks out the parent directory first. At the parent directory level there is no .perms to permit the user to check out the parent directory! This causes Add to Source Control to fail. Solution was to change the algorithm to account for this
  • Finished up CommentSQLCode trigger. Added stuff to triggers.dat and documented things in CM_DOCS. Waiting for code review.
  • Got this bright idea to take GetCCGroups.vbs and make another script that will simply dump the users for the given groups. Useful command line tool called whois
  • Worked on trying to get PC to install the new Rational Web Server for John

August 4, 2004

CommentSQLCode Trigger

  • Implemented CommentSQLCode Trigger - need to do code review, triggers.dat, and documentation
  • Assisted Loren, Padma and William in getting the Permisisons working

August 3, 2004

New Trigger

Here are the requirements as I understand them for the trigger that Steve Lipson wants for the SQL checkins. Basically he desires a trigger that will capture the checkin comment and other information and insert that information in the form of a comment at the top of the checked in element. This trigger will:

  • Be a postop trigger for the checkin action
  • Not be an all element trigger rather it will be attached to certain file elements in the vob
  • Be made for the <fill in vob name here> vob
  • Only work on file elements - directory elements are to be skipped
  • Only work on file elements that have an extension of .sql - other elements will be skipped

Roughly the psuedo code for this trigger will be:

# Get name of element and its type
$pname        = $ENV{CLEARCASE_PN};
$element_type = $ENV{CLEARCASE_ELTYPE};

# Skip directories and elements that aren't .sql
exit if $element_type =~ /directory/i || $pname !~ /\.sql$/i;

# Get comment and user
$comment   = $ENV{CLEARCASE_COMMENT};
$userid    = $ENV{CLEARCASE_USER};

# Format timestamp
$timestamp = getCurrentTime;

# Parse output of lsactivity -cact -long
($activity_id, $activity_title, $activity_owner) = parseLSActivity;

# Open up $pname for reading and $pname.trig for writting
open PNAME_IN, $pname
  or die "Unable to open $pname for reading - $!\n";

open PNAME_OUT, ">$pname.trig"
  or dir "Unable to open $pname.trig for writing - $!\n";

# Add comment to top of file
print $PNAME_OUT <<END;
-- Date:	    $timestamp
-- Activity: $activity_id: $activity_title
-- Owner:    $activity_owner ($userid)
-- Comment:  $comment
END

# Append $pname
while () {
  print PNAME_OUT $_;
} # while

close PNAME;
close PNAME_OUT;

# Switch $pname.trig -> $pname
unlink $pname;
rename "$pname.trig", $pname;

# Allow checkin to proceed
exit 0;

August 2, 2004

Server move (cont)

OK, licenses are all OK now. BTW hostid is not a combination of IP address and MAC address - it's simply MAC address of the NIC card. Problem appears to be that during the server move the NIC card changed! I verified this with the Rational rep this morning. The current MAC address of the NIC card as shown by ipconfig /all (it's the Physical Address) is 00-0f-20-6d-09-97. I gave the old license strings to the rep and she determined our old MAC address of the NIC card was 00-0b-cd-9b-f4-27.

Looking at the Device Manager on the servers I notice that we have two Network Adapters listed:

  1. HP NC7781 Gigabit Server Adapter
  2. HP NC7781 Gigabit Server Adapter #2

Why we have 2 NIC cards I don't know (perhaps merely for the ability to be multihomed). Normally I see #1 being disabled and #2 being enabled. Rtnlprod01 is like this. Rtnlprod02 has #1 enabled and #2 disabled. For the vob and view servers this does not matter. Either card will work. For rtnlprod03 however, since licenses are tied to the NIC card's MAC address, switching from #1 -> #2 (or #2 -> #1 as I suspect has happened here) will invalidate all licenses. We need to insure that the network adapter for rtnlprod03 remains nailed at either #1 or #2.

Since it appears that the network adapter has changed and since I have obtained a new set of licenses for this new network adapter and still have the old set, I have installed both sets so that in the event that the network adapter switches again we'll be covered. However, if we order additional licenses for say card #1 and somehow we get switched to card #2, those additional licenses will not be represented, hence the desire to nail the NIC card to either one or the other.

July 30, 2004

TTE/Server move to Cartwright

  • Had AD groups created in one day!
  • Supported the server move to Cartwright. The move invalidated all Clearcase/Multisite licenses! Got emergency licenses

July 29, 2004

Nag/TTE/Print CSS

  • Finished nag. Started nagging David Chu and TTE-EMP people. Worked well with TTE-EMP people....
  • Requested creation of AD groups for TTE-EMP. Created in one day! Yippie!. Showed Loren how to make .perms files. Still need to address the issue of Empower people being in which CC group...
  • Changed web pages to use new print CSS

July 28, 2004

Tools push/Lockvobs

  • Met with Victor Larson and William Fagerberg regarding tools push. We went over my install scripts and they will attempt to package up an msi file that will install Clearcase and TUP and add the appropriate registry entries for the user. We in CM just need to ensure that we have the appropriate reg file set up before the pushes occur.
  • Changed Lockvobs to use an exclusion list of vobs to not [un]lock vobs
  • Helped new guy, John Luu, with his set up

July 27, 2004

Nag

  • Implementing email reminder

July 23, 2004

Logger/Display modules - backups

  • Attended backup meeting. It may be that we cannot use diskpart to break hardware mirrors! Spoke with a Rusty Young and he wants a copy of our requirements and may present us with other options like Volume Shadow Copy, SAN, etc.
  • Modified Display module to accept optional filehandle and to display errors and warnings to STDERR
  • Checked in initial Logger Object. Now uses Display module

July 22, 2004

Logger

  • Worked on a Logger object
  • Resolved long standing Compare does not work in snapshot view issue. Turns out that certain vobs had forward slashes instead of backslashes in their storage paths for the vob tags. Changed to backslashes and compare works again. Strange! Bug in Rational code. Cleaned up all vob tags. View tags do not appear to be affected. May think about changing tagit to tag things with only backslashes...

July 21, 2004

Mktriggers/restoring view

  • Finally got view restored. Recovered the triggers.dat file and the NoPBLs trigger
  • Implemented both the NoPBLs and Permissions triggers
  • Implemented vobsize

July 20, 2004

Permissions Trigger

Implemented Permissions trigger.

July 19, 2004

Permissions Trigger

I've given the "permissions trigger" some thought and would like to formalize the requirements a bit. The new trigger will have the following characteristics:

  • Since multiple groups will be allowed write access to the vob they will need to be added as additional groups on the vob group list.
  • Determination of what users get additional write capability will be on Active Directory groups. IOW you can grant write access to say the CC-PMO group but not specifically to Mike Hrenko who is a member of the CC-PMO group. Additionally CC-PMO would need to appear on the vob group list in this example.
  • The trigger will use CLEARCASE_PRIMARY_GROUP to determine what group the user is. This avoids having to do LDAP lookups and it's the way that Clearcase does it anyway. CLEARCASE_PRIMARY_GROUP will not be used verbatim - if it were then anybody would "fake" out the trigger by merely setting CLEARCASE_PRIMARY_GROUP. Instead "creds" will be called to ascertain the effective primary group.
  • A permissions element will be created that will contain a list of groups, one per line, that are allowed write access from this folder downward. The vob's initial or primary group owner (CC-TTE in the case of Core_automation) will always have write permission. Furthermore the permissions element should be secured such that only vob's primary group owner can modify it. Otherwise other groups could easily modify the permissions element thus granting write permissions to arbitrary groups.

Let's see an example of how this will work and how the trigger will respond. Let's assume the following directory structure:

Core_automation
Empower CC-EAG-AS, CC-EAG-ESB
Functions CC-EAG-VIP
Results CC-EAG-VMS
Common

Further let's assume that the permissions element is at the Empower level and contains the groups CC-EAG-AS and CC-EAG-ESB. This says that those two groups (as well as CC-TTE as primary group owners of the vob) have write permission (the ability to checkout) elements from Core_automation/Empower downward. Additionally let's say that we have a permissions element at Empower/Functions that lists CC-EAG-VIP and Empower/Results has a permissions element that lists CC-EAG-VMS. The following can be said:

  • Members of CC-EAG-AS and CC-EAG-ESB have write permissions to Empower, Empower/Functions, Empower/Results and Empower/Common. Further, if new folders are created under Empower, CC-EAG-AS and CC-EAG-ESB will have write permissions to those new folders as well (IOW the write permissions are inherited by new folders that are created)
  • Members of CC-EAG-VIP have write permissions to Empower/Functions and any new folders created under Functions, but they do not have write permissions to Empower/Results nor Empower/Common. Similarly CC-EAG-VMS has write permissions to Empower/Results but not to Empower/Functions nor Empower/Common

The pseudo code for the trigger is roughly as follows. Note that the trigger gets fired during checkout of an element only (it is assumed if the user successfully checked out the element then, at the time, he had write permissions and should be allowed to check in the element):

$vob_group_owner = GetGroupOwner (vob) 
$current_group   = GetCurrentGroup (CLEARCASE_PRIMARY_GROUP as per "creds") 

if (permissions element exists in the current folder) { 
  if (IsAMember (Parse ($permissions_element), $current_group) {
    <allow checkout>
  } else { 
    <recurse to check parent folder stopping at vob root> 
    <disallow checkout>
  } 
}

July 16, 2004

TTE/BUCS

  • Helped Don with BUCS
  • Attended meeting with TTE regarding how to better use Clearcase. Need to create a trigger that allows or disallows write access to certain areas of their vob

July 15, 2004

tagit/findview/Clearquest Web

  • Fixed tagit to tag into the current region
  • Adjusted findview to total views and accept multiple view search strings
  • Helped Anje, Timmie and Mike with new Clearquest web installation in the lab

July 12, 2004

Moving views

  • Consulted with ASAP regarding moving of views from a desktop to the server
  • Helped Subba move a vob to the server
  • Consulted with Babu regarding designing of Multisite replacement scheme

July 8, 2004

Display.pm/ASAP View moves/Backups/Compare to Previous

  • Created Display.pm Perl module
  • Consulted with ASAP Re: Moving views
  • Spoke with Rory Re: Backups
  • Worked some more with Rational regarding the Compare to Previous problem

July 7, 2004

mirror_backup coding/Compare to previous

  • Started coding mirror_backup
  • Worked with Rational on Compare to previous fails in snapshot view

July 6, 2004

GetCCGroups.vbs/PowerBuilder

  • Updated GetCCGroups.vbs to send email from servers
  • Documented PowerBuilder/Clearcase Performance.

July 5, 2004

PowerBuilder Testing

Created various views to perform performance testing of PowerBuilder builds.

July 1, 2004

BUCS Build Measurements

  • Completed BUCS Build Measurements. Managed to cut some of the build time by using outofdate and exclude_checkout options. Performed builds on each of Local/Remote snapshot views and Local/Remote dynamic views. Remote dynamic views are by far still the slowest with most of the time being spent in refreshing elements from Clearcase.
  • The GetCCGroups.vbs email process failed today. Turns out the code cannot send email. Posted a question about this on the newsgroup. Need to change the VB Script to set the mail server apparently

June 25, 2004

Finished backup script

The backup script is ready for deployment. It was determined to lock all vobs at once, back them all up then unlock the vobs. I also implemented the 7 days of history option. History is stored under d:\vobstore\backup as numbered directories (0-6 for Sun-Sat). The script now manages that area by first moving the current backup under d:\backup -> d:\vobstore\backup\ after first clearing out d:\vobstore\backup\ (if it existed). It was decided to put the history stuff under vobstore because this way we can tell the backup people "Just exclude d:\vobstore but get everything else".

I was experiencing "Access denied" errors irradically until I found out that there may be .being-deleted files as described here. To solve this I implemented exclusions on the xcopy command (/exclude:d:\backup\exclude.strings) which tells xcopy to exclude things in the "c" directory - i.e. the cleartext pool - which Clearcase can easily recreate without data loss. This also has the effect of reducing the backup copy size in some cases significantly (e.g. \ASAP_Docs goes from 2.1 gig down to 1 gig!).

Here's a rough psuedo code of what the script does:

Obtain a list of all vobs
Lock all vobs
foreach @vobs
  if d:\vobstore\backup\$current_day\$vob exists then
    remove it
  end if
  move d:\backup\$vob -> d:\vobstore\backup\$current_day\$vob
  copy $vob's storage area -> d:\backup\$vob
Next
Unlock all vobs

Cutting out the copying of cleartext pool has reduced the current backup time from 56 minutes (yes it grew) to 33 minutes.

Now, where are we WRT the SQL backup scripts?....

June 23, 2004

Multisite/backup.pl

Spent some time trying to multisite a test vob (\defaria). Realized that we will have a problem in that we will need a machine (server or client) dedicated to handling the multisite region in order to lock vobs and backup things.

Had a meeting WRT multisite approach. It was determined that will we switch to using a script to make a copy of the vobs and back up from there. Started writing script...

June 21, 2004

XML

Spent most of the day investigating XML and XSL.

June 18, 2004

XML

  • Spent most of the day studying XML
  • Added debugging code to LogActivity trigger
  • Worked on problem Sujay's people had with 0 length document

June 16, 2004

AD/CC Registry

  • Activated reporting of Active Directory groups
  • Cleaned up Clearcase Registry

June 15, 2004

BUCS/VOB Snapshots/RequistePro

  • More working with Babu re: BUC$ build script
  • Investigated and prototyped vob_snapshot backups
  • Incorporated Requisite Pro into a FAQ web page

Clearcase Web Server

The Clearcase web service died today. I don't know why but the following is what I did to get it back up and running.

Server is back up.

Problem analysis:

Not really sure where things went wrong however when I looked at it the Rational Web Platform (rwp - which is really just Apache with Tomcat under the hood) was not running. rwp creates error logs but they are hard to parse because there are many of them with apparently random numbers tacked on. I believe these numbers represent the date in some form but haven't figured out how to decode them.

Anyway, I tried moving them aside and to restart the rwp server so that it would be clear what the error file was. Couldn't move all the log files out of the way because some were busy. Wish I had a good tool to figure out who has a file open.

The error message when trying to start rwp was "The Rational Web Platform HTTP Service Terminated with Service-Specific Error 1". Searching the Rational Support site yielded that the reason the service could not start was because some other process was using port 80. Typically this is due to somebody else runnig IIS. No IIS running. Tried netstat but could not find who was using port 80. Tried telneting to port 80 and got "Connection failed" so whoever was using port 80 did not want to talk to me! :-)

Finally I tried running rwp.exe from the command line with --help hoping for help about rwp's possible command line opts. Instead rwp started and ran! Clearcase web was back up but I did not like having rwp running in a console window and if I were to log out I feared that the rwp process would end. So I went to the Services applet and tried to start (since there was no stop) rwp. It started and the rwp running in the console ended. For safety's sake I restarted the rwp service through the Services applet. I believe Clearcase web is OK for now and we are doign server maintainance tonight anyway...

June 9, 2004

PB/ASAP VOB Moves

  • Joined PowerBuilder newsgroup to try to find out how to solve the Orca Script problems. Looks like I'm gonna learn way more about PB than I wanted to
  • Tested moving PVOB and Src vob from vobstore to ASAP_VOBS. Works OK.
  • Learned that we can use the DOS command MOVE which moves the VOBs simply by manipulating the directory entries. This means moving a large vob takes no longer than a small vobs. This is probably possible because we are on the same filesystem
  • WRT these ASAP vobs, we need to ct find -all -exec "cleartool protect -chown <owner> %CLEARCASE_PN%"

June 8, 2004

ActiveState Perl

  • Spent most of the day installing a Networked ActiveState Perl. Had permission problems with making elements in my dynamic view! Don't know why? Tried a clearfsimport and that caused the Perl to fail. I think it didn't properly copy permissions. So I ended up having to Add to Source Control all the files by hand (since I don't have scripting tools)
  • Consulted with Subba about ASAP VOB Move test
  • Babu gave me an assignment to learn OrcaScript which is a scripting language for PowerBuidlder. Oh boy!

June 4, 2004

AD Groups

Worked on getccgroups.vbs most of the day. Managed to get it to recurse for groups within groups and to sort the arrays of names. Need to implement the email portion though.

June 3, 2004

More meetings

  • Yet even more meetings
  • Documented installation scripts. Fixed them to dynamically mktag for \ccverify
  • Helped Rick Cunneen with VOB questions

June 2, 2004

Meetings, Bloody Meetings

  • Attended several (3) meetings today so not much got done
  • Fixed some minor problems with verification scripts

June 1, 2004

CMVerify

  • Worked mostly on [cm|cc|cq]verify scripts. Got them checked in as working
  • Worked a little bit on the GetCCGroups vbs scripts

May 28, 2004

Updated install scripts/started verification scripts

  • Updated install scripts: Added running of PMO-CM.cmd to HKEY_LOCAL_MACHINE key Added checking of pre-existing installation of Clearcase and/or Clearquest and skipping the install if it's already installed.
  • Started putting together verfication scripts

May 27, 2004

VBScript/install command

  • Worked most of the day learning VBScript for the LDAP thing
  • Modified PMO.cmd so that it implements new fucntionality

May 26, 2004

FlexLM/GetCCGroups

  • Spent like 4 hours wrestling with FlexLM but finally got the thing to work and log license usage
  • Dustin gave me a VB Script that gets names for a group. Massaged it (read rewrote it) into GetCCGroups.vbs. This dumps out the names into files like CC-ASAP.grp, CC-PMO.grp, etc.

May 25, 2004

Evil Twin/LDAP/Diff

  • Finished up coding evil twin and went through a quick review with Don. Need to setup some test cases before implementing
  • Received some info from Dustin Sauter regarding LDAP access. He was quite helpful and even provided me with a utility ot show the members of a group as well as shared the LDAP schema.
  • Submitted clearbugnt and sysinfo for the view/vob server for the problem about ct diff

May 24, 2004

Evil Twin

  • Transformed Triggers document back into html
  • Worked on Evil Twin trigger
  • Consulted with Mike regarding moving ASAP to it's own share

May 21, 2004

tail/trigger

  • Worked on implementing tail
  • Worked with Sujay a bit on the ASAP_BUS_REQ trigger. Need to get a testign environment

May 20, 2004

BUCS

  • Attended a few meetings which took up my time
  • Worked about 2 1/2 hours on rmelem'ing some files for BUCS
  • Added installation of TUP to install script for CCADMIN. Need to propogate this to the other install scripts. Involved adding stuff to HKLM RunOnce for TUP install

May 19, 2004

Diff Problem/Ant Build

  • Worked a little on the problem with Core_automation and diff
  • Installed Ant and JDK into CM_TOOLS and performed a build of ASAP_Infrastructure!
  • Performed code review of INHIBIT_DUPLICATE_ELE

May 18, 2004

LogActivity/ASAP & ASAP_BUS_REQ/.reg files

  • Wrote LogActivity trigger which will log activity to an HTML log file. It requires one parameter, the path to where to put the log file. Thereafter it writes log files of the format _yyyy-mm-dd.html.
  • Added LogActivity trigger to ASAP_Docs and ASAP_BUS_REQ vobs
  • Changed old ASAP_NOTIFY trigger to use the generic NotifyTrigger.pl script with a message file for ASAP and another one with a different message file for ASAP_BUS_REQ
  • Adjusted triggers.dat to reflect this
  • Modified etc/*.reg file to include Clearquest settings in an ASCII form

May 17, 2004

ASAP_NOTIFY/PMO view/Install Scripts

  • Created new tools view named PMO
  • Installed ASAP_NOTIFY trigger
  • Created installation scripts

Continue reading "ASAP_NOTIFY/PMO view/Install Scripts" »

May 14, 2004

BUCS PVOB

  • Worked with Don on BUCS import. Problem was that the PVOB was not created with the proper name. Tried repairing the situation but was unable to. Don gave up is recreating the BUCS and BUCS_PVOB properly (again).

May 13, 2004

Lab/ASAP_NOTIFY Trigger

  • Finished up the lab by reregistring the views properly. Also found and tagged the INDIA vobs and views. One thing left on the environment is the Clearquest stuff but I have no idea what the username/passwords might be. I would like to get Mike on this but he's out. Oh well, the licenses are stille expiring in two days anyhow...
  • Reworked the ASAP_NOTIFY trigger:

    I have changed the trigger that you sent us to operate correctly in the Clearcase environment. This involved quite a few steps:
    • Changed to use the proper Perl conventions of -w and use strict.
    • Changed to work under ccperl, thus guaranteeing that it will work for all Clearcase clients
    • Changed to use Net::SMTP, which is already in ccperl, instead of requiring sendmail.pm
    • General code clean up. Also made a few subroutine to help logic flow.
    • Changed to write html logfiles to their web server
    • Changed to send link to html log file in the email.
    • Added this ASAP_NOTIFY trigger to the mktriggers mechanism.
  • Started investigating Ant

May 12, 2004

Installs/Code Review/rgy_backup

  • Used Altris to connect to Nash's computer to investigate her create view problem. Turns out her install was not done properly and she lacked MVFS. Instructed her to speak with Desktop folks to get a proper install
  • Installed licenses onto the lab machines. Clearcase and Multisite are now functioning in the lab... Well at least until May 15th! Also need to reregister vobs and views to have the new machine names in them. Haven't finished the views yet...
  • Assisted Rick Cunneen with some issues he had with the Evil Twin Trigger
  • Code reviewed ASAP's Notification Trigger.
  • Fixed rgy_backup on rtnlprod01. Don't know how it was broke nor how exactly I fixed it. I suspect that perhaps the backup registry server field in the Clearcase Control Panel Applet was mispelled. Sure looked right to me! Anyways I set it to blank thinking that might fix it but it didn't. When setting back I guess I typed it in correctly where it was incorrect before
  • Looked over Don's changed to the Evil Twin Trigger

May 11, 2004

Lab

  • Updated the lab to get Clearcase runnnig
  • Closed ASAP_BUS_REQ vob ticket

May 10, 2004

ASAP_BUS_REQ move

In trying to test this out before actually implementing this on the production vob I found that this does not appear to work as expected. Here's what I did:
  1. Created a new share on the production server (rtnlprod01) named defaria
  2. Set share permissions to Everyone: Full Control (for now).
  3. Created a private vob defaria2 with a path of \\rtnlprod01\defaria\defaria2.vbs. This vob is owned by vobadm and the group is CC-PMO.
  4. Mounted the vob on my desktop and through my already existing defaria view I copied some files into the vob root directory as well as made a subfolder with some files in there too.
  5. Added all files and folders to source control. This is now my test vob.
  6. Unmounted the \defaria2 vob from my desktop. (Note I also had to find and kill the vob_server, db_server and vobrpc_server processes on the vob server that were associated with this vob, \defaria2, as unmounting a vob does not stop these processes)
  7. Changed the share permission on the \\rtnlprod01\defaria share by removing Everyone and adding two groups: CC-PMO, which I am a part of, which will serve as the read/write test group and CC-TTE, which I am not a part of, which will serve as the read only test group. These two groups were added with Full Control to the share. Since CC-TTE is not a member of the vob group list they will fall into using the "other" permissions setting for the vob, which will limit them to read only. CC-PMO, being part of the vob group list will use the "group" permissions setting which will provide read/write.
  8. Next I remounted the vob on my desktop and checked out a file. So far so good. (I'm acting as a member of CC-PMO - a read/writer at this time)
  9. When I went to check in this file, however, I received the following error: "mvfs: ERROR: view=defaria vob=\defaria2 - ClearCase vob error see view_log on host rtnlprod02 for more info"
  10. Checking rtnlprod02 (the view server)'s view log shows me: 'view_server.exe(5684): Error: Unable to construct cleartext for object "0x46" in VOB "rtnlprod01:D:\defaria\defaria2.vbs": error detected by ClearCase subsystem' and 'text_file_delta: Error: Unable to open file \\rtnlprod01\defaria\defaria2.vbs\s\sdft\1f\a\0-8d2a90ad41134b1e9cddf04d42034d38-tk": Permission denied'
  11. Unmounted the vob again and went to the server and killed the vob_server/db_server/vobrpc_process again
  12. Added Everyone: Full Control back to the share point (leaving both CC-PMO and CC-TTE)
  13. Remounted the vob on my desktop. The first thing that I noticed was that the element did not have a checked out symbol next to it and it was accessible. Checked out and checked in the element again. No problems.

So it seems that there is some process in the Clearcase Explorer that requires that the share point have Everyone: Full Control set (or at least something more than just CC-PMO and CC-TTE). Note that if I click somewhere out of the directory, like to the subfolder then go back I get the "mvfs: ERROR..." again. I see no errors in the cleartool command line - just in Clearcase Explorer.

Seems the answer to the problem is to add clearcase_albd to the share permissions. I also added vobadm and the CCADMIN group

May 7, 2004

ASAP_BUS_REQ

  • Responded to ASAP's request to move their vob in order to allow read only access to another group
  • Packed...

May 6, 2004

ASAP_BUS_REQ/Flex LM

  • Worked on ASAP_BUS_REQ request to set up a read only group
  • Worked on Steve Nameroff's request to set up FlexLM monitoring

Continue reading "ASAP_BUS_REQ/Flex LM" »

May 5, 2004

Test web

Spend most of my time setting up a test environment for the web pages. Problem is that the web server (Apache) cannot see the M drive when started as a service so it must refer to a snapshot view. Created webview for this purpose. But how does on test when in order to do so would require to publish your changes?

So I created another view, webtest. But how does Apache reference two different DocumentRoot's? We don't have the power of aliasing, and there's the two web servers to consider: c09-272-a and rtnlprod02.

Ended up configuring Apache to listen on two different ports at the same time using VirtualHosts on both servers.

Then I hit a problem with snapshot views not honoring symlinks properly - it copies the elements instead - and difficulty in updating such things. You see I was attempting to share css and images folders by means of a symlink. Abandoned that idea. Still need to hammer out where I have full URL's and pay attention to the different ports, etc...

Emailed Rory Valle regarding backups, he says they are being done. Also prodded James Portugal again about LDAP access. Finally attended the CM Staff meeting

May 4, 2004

Core_automation and web pages

  • Worked hard with the TTE group to try to resolve the problem with comparing versions. Reproduced problem in a snapshot view. Seems there is still some permissions problem lurking. Can compare in dynamic view. Can compare in an ASCII fashion. Cannot compare in a GUI fashion with any other version than version 0 (or other empty data container. Tried fix_prot. Tried vob_sidwalk. Nothing is working. Contacted Rational. Working with Rational on this problem.
  • Moved web pages into CM_DOCS vob. Reconfigured web servers to point there. Changed LicenseMonitoring to work in this new context. Created webview snapshot view to access this with. Would like to use a dynamic view but Apache can't seem to see the M drive (Probably because it's running as a service).

May 3, 2004

Core_automation

  • Helped Bruce Durbin create a dynamic view
  • Worked with Loren Gifford on a problem he was having comparing elements
  • Eventually needed to create new vob and import Core_automation to it
  • Went to get cell phone.
  • Wrote findview to search for views in all regions

Continue reading "Core_automation" »

April 30, 2004

rgy_backup and server upgrade

  • Spent time trying to understand the Clearcase scheduler and why rgy_backup is not being performed. Apparently modifications were made to the Clearcase scheduler on rtnlprod01 in particular by Paul Kruchmer (or whoever). The net result was the cascading jobs were failing. This should be working more correctly on the new server
  • Dave & Busters - Enuff said
  • Back at the farm for the server swap: Things went well in the beginning - didn't even need to run reregister script. Then some problems occurred. Eventually we nailed it down to only one real problem - the inability of plain users to create views. Mentioned we should create one plain user in each production group so we can "play" plain user. Eventually Mike discovered that Windows 2003 Server tighened up security on the Share Permissions (not the permissions of the shared folder but the permissions of the share itself) such that Full Control for Everybody is now by default off. Toggled that on and all is well
  • Added lockvobs jobs to new rtnlprod01. Script was failing due to recent relative path fixes. Works from the shell but not from the Clearcase Scheduler perspective. Backed out changes for now

April 28, 2004

Meetings/Script review/Backup Registry Service

  • Attended 3 meetings today which, by far, occupied most of my time
  • Script review meeting was good. In particular I've implemented the following changes to reregister
    • Script not loops through regions for vobs as well as views
    • Script now uses -host on lsvob and lsregion to restrict execution to the vob and view hosts only
    • Script mktag's for both public and private vobs
  • Cleaned up the registry a little bit. Subba created some vobs in cs-nt that were:
    1. Not public
    2. Not in the pmo-nt region

    Also cleaned up a vob or two that was tagged in another region as private while it was public in the pmo-nt region. This happens semi-silently in that if you mktag -vob -region <other region>... the mktag will prompt for registry password, giving you the illusion that it is making the tag in other region as public when it is not. If you are mktag'ing into another region a public vob you must explicitly state -public!
  • Investigated backup registry service. It is not working in the current environment. Here's how I believe it is supposed to work:
    • You must, of course, configure backup registry server setting on all clients to point to the backup registry server properly. This we had already done.
    • You can manually take a snapshot of the registry by executing rgy_backup. If run on any machine other than the designated backup registry server it will merely ask the current registry server what the backup registry server is and set the backup registry server key in the Windows registry. If run on the backup registry server it will copy a snapshot of the registry files in $CCASE_DIR/var/rgy/backup. It appends a date timestamp to the file name and in the non timestamped filename, records a pointer to this file (e.g. the backup/vob_tag file contains the machine relative path to vob_tag_).
    • Clearcase relies on the Clearcase scheduler and the Standard Daily Job to perform daily snapshots of the registry via rgy_backup. There are two problems with this:
      1. Currently the Standard Daily Job is not even scheduled by default!
      2. One can envision crude developing in the backup directory after months of these daily jobs! I'm not sure how or if there is a mechanism for cleaning up such stuff

April 27, 2004

Server Swap Prep

  • Sent email to Rory Valle for him to install the backup software and start backing up the new servers
  • Already tested the transfer of [un]lock vobs jobs. Need to have the new servers up and to activate this to test them
  • Scheduled review meeting for reregister script
  • Checked the local users/groups on the old and new servers and they appear to be OK
  • Re: Genius move: Verified that EntData_ARCH wants R/W access for others denied but Core_automation will go with the standard vob permissions

April 26, 2004

CRPS/Genius Move

  • Recieved laptop today
  • Fixed problem with tables for IE
  • Worked on CRPS
  • Figured out how to move Genius vobs
  • Helped Subba with a vob import

Continue reading "CRPS/Genius Move" »

April 23, 2004

Genius move

  • Attempted to move Core_automation and EntData_ARCH vobs to prod01 but failed
  • Worked with security people to get vobadm password back
  • Worked a little to configure RWP for Perl CGI

Vob move problems

First problem with the move of these vobs was that vobadm's password had changed. Therefore I had to perform this vob move in an unfamilar environment. Also, ownerships and permissions on these vobs are odd as they were done before we started standardizing things. As ccadmin1 I was eventually able to copy the vob storage but was not able to register these vobs at the new location. Attempts to do so would fail with

cleartool: Error: Failed to record hostname "rtnlprod01" in storage directory
"D:\vobstore\EntData_ARCH.vbs". Check that root or the ClearCase
administrators group has permission to write to this directory.

Even after changing ownerships this was still failing. I suggest we take soem time to get the ownerships and permissions standardized on these vobs in the Genuis region before we attempt to move them again (that and perhaps doing some test moving...)

Vobadm password problems

AFAICT somebody changed the vobadm password. Now I'm not pointing any fingers however nobody in our group did and the only other group who knows the vobadm password is... Well you fill in the rest! Anyways, for some reason at about 3 Pm that somebody must have changed the password back.

April 22, 2004

Web views/register/Pauls Vob

  • Removed web views from rtnlprod03
  • Worked with Timmie regarding move of Genius vobs
  • Fixed reregister to handle web views
  • Worked with Paul to create CM_Docs vob
  • Helped Subba import some code and setup stuff for cs-nt
  • Started Clearcase Problem Reporting System

Continue reading "Web views/register/Pauls Vob" »

April 21, 2004

  • Requested LDAP access from James Portugal
  • Spoke to Tom regarding Niku. Says we'll only need to report time and that he'll hold a brown bag seminar for it
  • Requested that rtnlprod01/02 be renamed to 04/05
  • Converted web pages to new standard template
  • Set up RWP on prodfix01 so that it can access user FAQs
  • Checked that Clearcase web is working on prodfix02
  • Changed reregister to handle UCM PVOBS in a more intelligent way

April 20, 2004

M Drive problem, LDAP stuff, Installation Areas

  • M drive problem appears to be a networking problem at Eric's location
  • Condensed Client release areas to one release area
  • Attempted to access LDAP through Perl

Continue reading "M Drive problem, LDAP stuff, Installation Areas" »

April 19, 2004

reregister, ccperl, fix FAQ, view private files

  • Finished reregister script. This script will reregister all vobs and views that were based on rtnlprod02. This is needed since the new server will not have the same IP address as the old server.
  • Changed mktriggers to use ccperl unqualified instead of fully qualifying it. This will allow the triggers to work on the servers as well as the clients
  • Added FAQ entry describing view private and derived objects
  • Fixed the FAQ pages. Mike had switched rtnlprod02 over to using rwp. This broke the FAQ pages since they used Apache under Cygwin. Reported rwp to the old FAQ pages.

April 16, 2004

Reregistering Clearcase objects

  • Worked with Mike trying to get Clearcase web to function correctly
  • Since the IP address of the new servers will be different I worked on a script that will reregister views and vobs. This reregistering and retragging should fix up the IP address problem

April 15, 2004

Clearcase & Clearquest Web

Today...
  • Partitioned drive

  • Installed Windows XP

  • Attended Peregrine Training

  • Configured Clearquest web

  • Worked with Michael on Clearcase web problems

  • Worked on problem with accessing Clearcase due to outgrowing the lockmgr's limits

  • Implemented Heap Size fix and Lockmgr fix to new production servers

Continue reading "Clearcase & Clearquest Web" »

April 13, 2004

The new servers have arrived!

The new servers have arrived and I have been testing them today. Here's what I managed to do:

  • Installed Clearcase server software on new machines.
  • Configured storage locations for vobs/views
  • Practiced moving a vob and view over to the new servers. The view even had a checked out file.
  • Once set up on the new servers accessed the view and insured that I could access it and that the checked out element was still accessible.

In setting up prodfix01 as a the vob server I encountered some problems attempting to set the storage location. The default wizard was not the right way to go. Instead I had to:

cleartool> mkstgloc -vob -host prodfix01 -hpath D:\vobstore -gpath \\prodfix01\vobstore vobstore \\prodfix01\vobstore

Naturally this will not due as this machine will eventually be renamed as rtnlprod01, not prodfix01. This will need to be adjusted during the downtime. Just some notes from my testing session:

After setting up the servers I had to create the storage locations as above. I called them vobstore and viewstore instead of ccvobstg/ccviewstg. Personally I find the former more descriptive.

I tried to simply mktag for the vob and view on the new server but that would not work. Instead I had to:

cleartool register -replace -view \\path\to\view
cleartool register -replace -vob \\path\to\vob
cleartool mktag -replace -view -tag \\path\to\view
cleartool mktag -replace -vob -tag \\path\to\vob
cleartool startview
cleartool mount

Again, if we slide the server into place after changing the DNS/Machine name <-> IP address mapping this should not be an issue.

We should be ready to go, perhaps this coming Thursday evening (sometime after 7 Pm). What we would need to do is:

  1. Announce to the Clearcase community that Clearcase will be down for a few hours Thursday night (7 Pm - 9 Pm)
  2. At 7 Pm stop Clearcase on rtnlprod01 and rtnlprod02
  3. xcopy /e /i /f /h /k /x > C:\vobstore_xcopy.log 2>&1
  4. xcopy /e /i /f /h /k /x > C:\viewstore_xcopy.log 2>&1
  5. Shutdown rtnlprod01 and rtnlprod02
  6. Switch DNS so that prodfix01 -> rtnlprod01 and prodfix02 -> rtnlprod02
  7. Test vob/view access from desktop clients.

April 7, 2004

VIP Imports

Imported source into many vobs today with Subba. Had some problems with the vob server (db_VISTA error -922). Ended up stopping and restarting Clearcase on rtnlprod01.

Was assigned to set up both Clearcase web and Clearquest web. Luckily Clearcase web is already up on rtnlprod03. Need to set up Clearquest web...

Modified protect trigger to use current owner instead of original creator of the VOB to change the ownership of new elements.

April 6, 2004

Lockvobs

Re-wrote the lock vobs script in Perl to be much more flexible. It now locks or unlocks (-u) vobs. Also you can supply an -smtphost which defaults to notesmail01. Finally you can specify either -to or -errors-to as a list of email addresses that the report is send to. The later, -errors-to, are for people who only want to be notified if there is an error (i.e. me! :-).

Changed bat files accordingly and tested out adding these to the Clearcase Job Scheduler on my machine. Have not yet added this to "production" (rtnlprod01). Perhaps tomorrow...

Also worked with Subba to clean up and clear out some UCM vobs.

Spend some time trying to get MySQL running under Cygwin.

April 5, 2004

Lock Vobs jobs

Came in today and noticed that Notes was complaining that a network operation had failed. Also saw a couple of messages that Clearcase was having problems so I started investigating. Apparently the albd_server was not running on rtnlprod01. Scanning the logs I found:

albd_log: Error: Unable to connect to SMTP server "172.16.101.56[6400]": Bad file descriptor.

Well 172.16.101.56 happens to be notesadmin01:

C09-272-A:nslookup 172.16.101.56
Server:  dhcp01.ameriquest.net
Address:  172.16.101.100

Name:    notesadmin01.ameriquest.net
Address:  172.16.101.56

Why are we trying to email through notesadmin01 instead of notesmail01?

Meantime I unlocked the vobs...

Looking at the SMTP setting in Control Panel: Clearcase: Options I find the SMTP Host set to appsmtp.ameriquest.net which is an alias to notestadmin01.ameriquest.net:

C09-272-A:nslookup appsmtp
Server:  dhcp01.ameriquest.net
Address:  172.16.101.100

Name:    notesadmin01.ameriquest.net
Address:  172.16.101.56
Aliases:  appsmtp.ameriquest.net

I guess the questions are:

  • What is the official SMTP host that we can rely on?
  • Why does the [un]lock vobs job have problems and eventually kill the albd_server process simply because it cannot contact the SMTP host?

Further investigation yields the following: The lock and unlock vobs scripts apparently appear in .../Rational/Clearcase/var/scheduler/tasks. There are 4 files involved:

  • ccase_lock_vobs.bat: Simple bat file that fires off Perl on...
  • lock_vobs.pl: This locks the vobs and sends email
  • ccase_unlock_vobs.bat: Simple bat file that fires off Perl on...
  • unlock_vobs.pl: This unlocks the vob and sends email

Additionally these Perl scripts use C:/Winnt/System32/blat.exe to send mail.

Finally the task_registry file was modified to add these custom jobs.

I believe that this was done by perhaps Paul and/or Brian and it is fine work and does the job. However, seeing as we are about to reburn this system to Windows 2003 Server such work would be lost! And who would remember where this blat came from and that it needed to be reinstalled?

Suggestions:

I think we should use the Rational supplied tool, notify, instead of blat. This way we would not need to remember to find and reinstall this blat thing. I think Brian had problems getting notify to work and instead fell back on something he knew, blat, to get this working. Additionally IMHO blat should not be in the Windows directory! If we must use blat then perhaps we should install it into CM_TOOLS/bin.

Additionally I suggest that we relocate the .bat files and Perl scripts to CM_TOOLS/bin also and task_registry file should be pointed to CM_TOOLS/bin.

Finally I think there should be a script set up to reproduce/reinstall this environment.

IOW our stuff should also be version controlled and scripts written to automate it's installation and workings.

March 11, 2004

Ah comfort!

Ah the comfort of being able to get through the firewall! It feels so good. Now I can read email from my home and use IM again! Yippie!

Alas my system will be moving in two days as I am moving too! Things will be hectic for the short term.

At work I worked on the script to add triggers to the vobs a bit more. Still need to convert it to Perl...

Started investigating adding storage to the servers. This may get a little tricky. Need to meet with Brian and Babu about this.

Played with the web server some more - now pointing it into the actual vob. Had a hell of time doing this as things were acting weird. Rebooted my system and wham! Everythings good now...

March 10, 2004

Web server

This afternoon, after returning from the training I did:

  • Worked on problem with case perserving MVFS. Two of the servers had case perserving set off so I fixed that. While working on another problem one of those servers rebooted. Oh well, at least that fixes it's case preserving. The other server was later rebooted. Still clients need to make sure that they have case preserving set on and need to reboot. Unfortunately this was not set properly during the rollout.

  • Worked on a problem view with no success. Unable to get it to work. Keep getting unknown error in view server - not very helpful.

  • Got my user ID finally! Was able to run Lotus Notes. Oh boy, what joy! Anyways I was able to send email via Ameriquest's email server. Still can't pop nor imap it though.

  • Installed Cygwin on some of the servers as well as set up my environment. Need to get my new user ID added into the Clearcase group. Can now ssh into some of the servers to perform actions.

  • Set up Apache under Cygwin on one server. Babu asked me to see if I could make a read only web server to view thing.

Back from San Jose

Well I got an apartment! It's called The Lake and it sure has a large lake. The apartment is a 1 bedroom with a loft and it's 1000 square feet. I have the lake right off my patio. This means that I need to move in this coming weekend! Gotta get busy.

My car's transmission decided to die so I could not drive down and had to fly in instead. Well the flight was nice but it was too damn short! :-) Looks like I'll need a new car. Wonder if I can get the Eclipse back...

Today at work I get in and started downloading the tarball of my stuff. Wonder when I'll get my own userid? Then Babu tells me to come with him. Off to another Clearcase Training class that he's holding in another Ameriquest building (Apparently there are a lot of Ameriquest buildings and we might be moving to one of them. This other building was brand new and quite nice). The class was OK but they were not ready for us so we had to make due with a small conference room and just use Babu's laptop for class exercises. Then Babu cuts out and leaves me to finish up the training! It's only my 3rd day here and I'm supposed to train!?! Oh well. It wasn't that bad but I was not prepared for that.

Got a ton of things to do and to keep track of

March 5, 2004

Day 2

Long day yesterday (9 Am - 11 Pm).

Today I:

  1. Attended the 9 Am meeting

  2. Wasn't able to lock the old ASAP_Docs vob so I rm'ed the tag instead

  3. Checked in the CheckinPre trigger

  4. Setup web server on my deskctop

  5. Removed a number of test vobs

March 4, 2004

1st day at Ameriquest

Well made it here. We're on the 9th floor of this building. Argh, having to go through all of the new things like badges, user ids, etc. Apparently this shop is much more closed up than the old place. I cannot, for example, get through to my machine at home for email and the like. I can get to my home page. Guess I'm gonna have to implement that web mail thing after all!

Can't ftp home, can't use IM. No IMAP. No POP. Apparently they also restrict other web sites like sports related stuff, etc.

Interesting in that they apparently use Lotus Notes for email. Argh! This is gonna be a fight regarding tools and the like.

Created a vob, view, etc today. We are supposed to be doing a lot of client installs today and tomorrow.

Managed to install Cygwin partially and get some semblence of my environment.