[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

693.0. "RE - Error Sup ing Files" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Fri Apr 15 1994 15:11

Date Of Receipt: 	15-APR-1994 09:44:18.08
From: 	KRISIS::hantman "Paul C. Hantman OSG Test Tools"
To: 	KRISIS::odehelp
CC: 	KRISIS::hantman, KRISIS::jmf
Subj: 	RE - Error Sup'ing Files

HI,

Can anyone tell me why I would be getting this message?

Also, where can I find a list of error messages from sup? I hate having to 
send mail everytime sup hiccups.

Thanks in Advance,
Paul

------- Forwarded Message

Return-Path: [email protected]
Received: from monterio.pa.dec.com by alpha.zk3.dec.com;
(5.65/1.1.8.2/06Apr94-1115AM)
	id AA10326; Fri, 15 Apr 1994 04:50:11 -0400
Received: by monterio.pa.dec.com; id AA01778; Fri, 15 Apr 1994 01:50:03 -0700
Date: Fri, 15 Apr 1994 01:50:03 -0700
From: [email protected] (Ko Yu ODE Development)
Message-Id: <[email protected]>
To: "[email protected]"@pa.dec.com
Subject: SUP Upgrade of qaqc.nightly_pool at Fri Apr 15 01:50:02 1994


SUP: Error reading setup reply from file server
SUP: Upgrade of qaqc.nightly_pool aborted at Fri Apr 15 01:50:02 1994

------- End of Forwarded Message


T.RTitleUserPersonal
Name
DateLines
693.1Re: RE - Error Sup ing FilesSMURF::FILTERAutomatic Posting Software - mail to flume::puckFri Apr 15 1994 15:1830
Date Of Receipt: 	15-APR-1994 11:17:52.19
From: 	WASTED::"[email protected]" "15-Apr-1994 0818"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: RE - Error Sup'ing Files

Paul,

Unfortunately, there isn't a single listing of SUP error messages
that I am aware of and, like other UNIX software, SUP just tells
you what it was doing when it encountered an error.

This message (error reading setup reply from file server) means that
an I/O error or timeout occurred in the initial phase of updating
the collection.  The client has located the server and they have
exchanged some data to just handshake at this point and now they
are starting the "meat" of the conversation re: the details of
the collection involved.

My expectation is that this is indicative of a) a transitory network
event or b) non-responsiveness of the server.  I would proactively
verify that the file protections and ownerships of both the paths
to the collection data and to the sup description data themselves
are correct.  The only way I know how to do that is to eyeball it.

Is this a hard fault or a one-time event?

Regards,
Myles Connors

693.2Re: RE - Error Sup ing FilesSMURF::FILTERAutomatic Posting Software - mail to flume::puckFri Apr 15 1994 15:2224
Date Of Receipt: 	15-APR-1994 12:55:18.29
From: 	KRISIS::hantman "Paul C. Hantman OSG Test Tools"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: RE - Error Sup'ing Files

Hi,

Thanks for the quick response.
 
I checked the server and all file protections, ownerships and groups appear to 
be correct. The only possible exception is that the file 
src/kxct.conf, which is a symbolic link to the file 
config/kxct.conf.src.alpha_OSF1, was readable by "others". I reset
the file permisions to 664. As a matter of fact, every once in a while
I notice that the permissions for that file are modified. It's not
something I'm doing
explicitly. Is there any reason this might be happening?

This is the only time I have seen this error so hopefully this is a transitory 
network event.

-Paul

693.3Re: RE - Error Sup ing FilesSMURF::FILTERAutomatic Posting Software - mail to flume::puckTue Apr 19 1994 11:5364
Date Of Receipt: 	19-APR-1994 08:39:21.85
From: 	KRISIS::hantman "Paul C. Hantman OSG Test Tools"
To: 	KRISIS::odehelp
CC: 	decwet::jdaddamio, KRISIS::hantman
Subj: 	Re: RE - Error Sup'ing Files

#Paul,

#>The basic problem is that palo alto cannot sup the pool. They've been getting
#>the error "error reading setup reply from file server". When I noticed this 
#>problem I looked at the pool and everything seemed to look okay except that
#>the permissions for the file config//kxct.conf.src.alpha_OSF1 were changed.
#>I just thought the two might be related, I am not doing anything that I
#>know of at this end that would cause the permissions to be modified. 

#Let's start at the beginning. Are you running sup on their node? 
#I don't see how you can help them without logging into their node.

I have not been running sup on their system, they have and I get mail when sup
fails ."notify" in the coll.list file has been set to send me mail along with 
the pool admin. at pa.

I have asked them to run check_ode on monterio.

#>check_ode output follows:
#>#########################################################################
#>Check_ode for ODE-II V2.0 -- $Revision: 1.1.8.3 $
#>Mon Apr 18 14:53:21 EDT 1994
#>Using logfile=tmp16895.logfile
#>/usr/sde/tools/alpha_OSF1/bin/check_ode[23]: tmp16895.logfile: cannot create

#I don't know how that script behaves if it script can't write a logfile. 
#It's output here is certainly incomplete and abnormal. 

#Rerun check_ode a) in a directory where you have write priveleges and using 
#-debug option to find out what's going on.


I have re-run check_ode with the sup_server option. The results follow:

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Check_ode for ODE-II V2.0 -- $Revision: 1.1.8.3 $
Tue Apr 19 08:38:11 EDT 1994
Using logfile=tmp6628.logfile

Checking sup server troi.zk3.dec.com Tue Apr 19 08:38:11 EDT 1994
    Info -- troi.zk3.dec.com: Sup server Load=0

Error No. 1 ---------- Tue Apr 19 08:38:15 EDT 1994
    troi.zk3.dec.com: processes /usr/bin/supfilesrv /usr/sbin/supfilesrv /etc/su
pfilesrv not running


    Sup server error count is 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I ran ps and found that supfilesrv had been running, but was now idle.

#Might be a good idea to run check_ode on their node too.

I have also asked pa to run check_ode on their system.

#John