[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

2281.0. "re: We are having a problem with our shared sandbox" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed May 15 1996 15:07

Date Of Receipt: 	15-MAY-1996 13:38:30.47
From: 	ALPHA::"[email protected]" "Joshua M. Friedman OSF/UNIX SDE  15-May-1996 1331"
To: 	[email protected]
CC: 	[email protected]
Subj: 	re: We are having a problem with our shared sandbox

Cliff, I've cc'd odehelp here - it's best to always report sandbox
problems via odehelp.

Here are some things to check:

on the shared sandbox submit server, ihike, run check_ode server; see
if that reports anything that gives you a clue.  You can ignore the
devbld/devrcs account warnings.

can you do a kinit -d from ihike?  this will check /etc/krb.conf and the 
kerberos slave connection.  there was a problem yesterday with named which
caused kerberos1... to not resolve; if this fails try putting the real
name of kerberos1 in the file as another server: virago.zk3.dec.com

is the srvtab on ihike in place and correct (strings /etc/srvtab should
show kxct and ihike + garbage)

is there an entry in the kerberos database for kxct@ihike (see admin)?

-josh



------- Forwarded Message

From: Cliff Straw USG <[email protected]>
Received: by ihike.zk3.dec.com (5.65v3.2/1.1.10.5/13Feb96-0331PM)
	id AA06589; Wed, 15 May 1996 10:36:16 -0400
Date: Wed, 15 May 1996 10:36:16 -0400
Message-Id: <[email protected]>
To: [email protected], [email protected]
Subject: We are having a problem with our shared sandbox
Cc: [email protected]

Grant, Josh:

We have a new problem with our project shared sandbox.  The sandbox is
currently backed by steeldx.pre.bl1.  When I try to do a workon to a
sandbox that is backed by the shared sandbox, I get a message about not
having a valid kerberos ticket.  This happens even when I do have a ticket.

I suspect the shared sandbox is the culprit because I can do a workon to a
sandbox that is backed directly to steeldx.pre.bl1.  I have checked the
documentation, reinstalled the ode server on ihike (the shared sandbox
server) and I cannot figure our what is wrong.

I have included the output from the klist and workon commands.  I would
really appreciate some help from one of you to figure out what is causing
this.

Thanks,
Cliff

- --------------

ihike$ klist
Ticket file:    /var/dss/kerberos/tkt/tkt5003
Principal:      Cliff_Straw@ZONE

  Issued           Expires          Principal
May 15 09:48:50  May 15 19:48:50  krbtgt.ZONE@ZONE
ihike$      
ihike$ workon -sb imageproj
cd'ing to sandbox source directory: 
/usr/projects/ihike_work/sandboxes/imageproj/src.
starting new shell: /usr/bin/ksh.
To access your ODE server you must:

        o kinit $PRINCIPAL (then input your kerberos password)

        o Enter workon -sb sandbox name or default.

Please obtain kerberos ticket and try again.


NOTE: You are in your sandbox.

   o This sandbox can only be used for ODE services which don't
   require the ODE server (i.e. build, mklinks, etc. ).
   To avoid this message use the no kerberos switch:

          workon -nk -sb sandbox name
Executing .kshrc


------- End of Forwarded Message


T.RTitleUserPersonal
Name
DateLines
2281.1re: We are having a problem with our shared sandboxAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Jun 12 1996 15:57156
Date Of Receipt: 	12-JUN-1996 14:26:45.57
From: 	QUARRY::straw "Cliff Straw USG"
To: 	odehelp@DEC:.zko.quarry
CC: 	jmf@DEC:.zko.quarry, straw@DEC:.zko.quarry
Subj: 	re: We are having a problem with our shared sandbox

I have checked everything that Josh suggested and I don't see any obvious 
problems.


ihike.zk3.dec.com> check_ode server
Check_ode for DECode II V3.0 -- $Revision: 1.1.4.31 $
Wed Jun 12 14:19:51 EDT 1996
Using logfile=tmp16697.logfile
             
Checking server ihike.zk3.dec.com Wed Jun 12 14:19:52 EDT 1996        
    Info -- ihike.zk3.dec.com: DECode II Server Load=0        
    Info -- Checking nfs locks on ihike.zk3.dec.com        
    Info -- Time diff ihike.zk3.dec.com - kerberos.zk3.dec.com is 455 ms.        
    Info -- cron running        
    Info -- ode_server3.0 running        

Error No. 1 ---------- Wed Jun 12 14:19:56 EDT 1996
    ihike.zk3.dec.com:/etc/group had no entries that matched the following:

        '^devode:|^staff:|^audit:'        
    Info -- Checking ihike.zk3.dec.com:/etc/srvtab        
    Info -- ihike.zk3.dec.com:/etc/srvtab ok        
            
             
    Server error count is 1        
ihike.zk3.dec.com>                 
ihike.zk3.dec.com> 
ihike.zk3.dec.com> strings /etc/srvtab
kxct
ihike
ZONE
ihike.zk3.dec.com> 


There is a kxct.conf file in the logs directory.  The contents of the file are:

command exists /usr/sde/ode2.0/tools/alpha_OSF1/lib/srcacl no_acl 
./.srctempXXXXXX
command rm /usr/sde/ode2.0/tools/alpha_OSF1/lib/srcacl no_acl ./.srctempXXXXXX
command cp /usr/sde/ode2.0/tools/alpha_OSF1/lib/srcacl no_acl ./.srctempXXXXXX

Do I need this file?  It looks like it was never updated to ode3.0

Thanks,
Cliff


------------- Begin Forwarded Message -------------

From jmf  Wed May 15 13:32:00 1996
Delivery-Date: Wed, 15 May 96 13:32:01 -0400
To: [email protected]
Cc: odehelp
Subject: re: We are having a problem with our shared sandbox
Date: Wed, 15 May 96 13:31:58 -0400
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <, >
X-Mts: smtp
Content-Length: 2791

Cliff, I've cc'd odehelp here - it's best to always report sandbox
problems via odehelp.

Here are some things to check:

on the shared sandbox submit server, ihike, run check_ode server; see
if that reports anything that gives you a clue.  You can ignore the
devbld/devrcs account warnings.

can you do a kinit -d from ihike?  this will check /etc/krb.conf and the 
kerberos slave connection.  there was a problem yesterday with named which
caused kerberos1... to not resolve; if this fails try putting the real
name of kerberos1 in the file as another server: virago.zk3.dec.com

is the srvtab on ihike in place and correct (strings /etc/srvtab should
show kxct and ihike + garbage)

is there an entry in the kerberos database for kxct@ihike (see admin)?

-josh



------- Forwarded Message

From: Cliff Straw USG <[email protected]>
Received: by ihike.zk3.dec.com (5.65v3.2/1.1.10.5/13Feb96-0331PM)
	id AA06589; Wed, 15 May 1996 10:36:16 -0400
Date: Wed, 15 May 1996 10:36:16 -0400
Message-Id: <[email protected]>
To: [email protected], [email protected]
Subject: We are having a problem with our shared sandbox
Cc: [email protected]

Grant, Josh:

We have a new problem with our project shared sandbox.  The sandbox is
currently backed by steeldx.pre.bl1.  When I try to do a workon to a
sandbox that is backed by the shared sandbox, I get a message about not
having a valid kerberos ticket.  This happens even when I do have a ticket.

I suspect the shared sandbox is the culprit because I can do a workon to a
sandbox that is backed directly to steeldx.pre.bl1.  I have checked the
documentation, reinstalled the ode server on ihike (the shared sandbox
server) and I cannot figure our what is wrong.

I have included the output from the klist and workon commands.  I would
really appreciate some help from one of you to figure out what is causing
this.

Thanks,
Cliff

- --------------

ihike$ klist
Ticket file:    /var/dss/kerberos/tkt/tkt5003
Principal:      Cliff_Straw@ZONE

  Issued           Expires          Principal
May 15 09:48:50  May 15 19:48:50  krbtgt.ZONE@ZONE
ihike$      
ihike$ workon -sb imageproj
cd'ing to sandbox source directory: 
/usr/projects/ihike_work/sandboxes/imageproj/src.
starting new shell: /usr/bin/ksh.
To access your ODE server you must:

        o kinit $PRINCIPAL (then input your kerberos password)

        o Enter workon -sb sandbox name or default.

Please obtain kerberos ticket and try again.


NOTE: You are in your sandbox.

   o This sandbox can only be used for ODE services which don't
   require the ODE server (i.e. build, mklinks, etc. ).
   To avoid this message use the no kerberos switch:

          workon -nk -sb sandbox name
Executing .kshrc


------- End of Forwarded Message


------------- End Forwarded Message -------------


2281.2Re: We are having a problem with our shared sandboxAOSG::FILTERAutomatic Posting Software - mail to flume::puckWed Jun 12 1996 16:5921
Date Of Receipt: 	12-JUN-1996 15:03:37.77
From: 	FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  12-Jun-1996 1503"
To: 	Cliff Straw USG <straw@DEC:.zko.flume>
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: We are having a problem with our shared sandbox

Cliff, re
>There is a kxct.conf file in the logs directory .. it was never updated to 
ode3.0

this file is no longer used in ode3.0; we've generally just let them
lie around, though thanks for the reminder - we could clean them up
now.

Are you still having a problem?  If so I haven't seen mail.  Please do
what ever is failing (eg bsubmit) with "-verbose -debug -odedebug csv"
all added to the command line, and send the output to odehelp.

Thanks...		-josh