Conference smurf::buildhelp

801.0. "bsubmit problems; expect Vikas so_locations files late" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Jun 13 1994 18:47

Date Of Receipt: 	11-JUN-1994 07:30:39.56
From: 	FLAMBE::"[email protected]" "10-Jun-1994 2354"
To: 	[email protected], [email protected], [email protected]
CC: 	[email protected], sontakke@dec:.mro.helix
Subj: 	bsubmit problems; expect Vikas' so_locations files late

John/Cori/Darrell, and FYI...

I was helping Vikas with his submit, but it still seems to be either
stuck or really c-r-a-w-l-i-n-g.  He's had VERY poor connectivity
between MRO and ZK3, and has observed processes moving steadily but
like mollases.

(This will demonstrate if the non-expirating ticket for bsubmit works!)

It's still in the hold, and seems to be still running (see below):

    % more /usr/sde/osf1/build/goldos/logs/bsubmit.hold
    : Vikas_Sontakke; Date: 6/10/94; Time: 17:08
    ./usr/shlib/Makefile
    ./usr/shlib/alpha/so_locations               

There is evidence that the submit is still moving - it's already past the
first 2 phases of the submit on to the "check-in" phase.  The ps attached
is part of this phase, locking the submit branch, rev 1.1.12.5.

As you can see from the ps showing that rcs is "locking" rev 1.1.12.5:
27980 p3 I 0:00.00 authcover rcs -q -l1.1.12.5 ./usr/shlib/alpha/so_locations,v

And blog on so_locations shows this is the submit branch:
    GOLDOS_BL11: 1.1.12.5

This submit may just complete on its own.  But it doesn't look promising.

-josh


------- Forwarded Message

Return-Path: [email protected] 
Delivery-Date: Fri, 10 Jun 94 17:43:40 -0400
Return-Path: [email protected]
Received: from styrax.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/30Mar94-0502PM)
	id AA27553; Fri, 10 Jun 1994 17:43:38 -0400
Received: from DECnet-Mail11.alpha.zk3.dec.com by alpha.zk3.dec.com; (5.65/1.1.8.2/26May94-1024AM)
	id AA05281; Fri, 10 Jun 1994 17:39:47 -0400
Date: Fri, 10 Jun 1994 17:39:46 -0400
Message-Id: <[email protected]>
From: [email protected] (Vikas, DTN 297-9192, Extern (508)-467-9192)
To: [email protected]
Cc: [email protected]
Subject: can someone from the North check the status of my hung bsubmit?  thanks

After help from Josh Friedman, we restarted the entire process, it asked me to 
merge one file manually (./usr/shlib/Makefile) but now the process is hung 
again

27818 p3  I      0:01.07 bsubmit -auto_out -all -defect goldos-3123-sontakke
27978 p3  I      0:00.05 authcover rcs -q -l1.1.12.5 ./usr/shlib/alpha/so_locations,v
27980 p3  I      0:00.00 authcover rcs -q -l1.1.12.5 ./usr/shlib/alpha/so_locations,v


------- End of Forwarded Message

Date Of Receipt: 	11-JUN-1994 19:14:25.75
From: 	FLAMBE::"[email protected]" "Steve Beikman USG/Release Eng"
To: 	[email protected], [email protected], [email protected],
	[email protected]
CC: 	[email protected], sontakke@dec:.mro.helix
Subj: 	Re:  bsubmit problems; expect Vikas' so_locations files late

when conditions, such as Vikas has experienced, additional information
might be usefull.   'traceroute' and 'ping -R buffer.zk3' output would
be the kind of information we would like to see.    If we supect a
problem with the network, then we could notify the appropriate people.

/sb