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

Conference iosg::all-in-1_v30

Title:	OLD ALL-IN-1 (tm) Support Conference
Notice:	Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:	IOSG::PYE

Created:	Thu Jan 30 1992
Last Modified:	Tue Jan 23 1996
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4343
Total number of notes:	18308

4230.0. "FCS is not available" by DEKVC::ALLIN1 () Fri Jun 03 1994 08:39

Hi,

I have one problem on upgrade of ALL-IN-1 V3.0.
During auto postinstallation task, one problem occurred at FCS starting.

Though I have relavant log files , can't find a way out easily.
                                                              
Are there anybody who can give me a advise ?
For any help, thanks in advance.

HJ.

PS. attached is reference log files and comment. 

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

1.  installation log.

	>    A1$POST running -- setting file protections
	>%UAF-I-GRANTMSG, identifier OAFC$SYSMAN granted to SYSTEM
	>%OA-I-LASTLINE, "ALL-IN-1 running -- Starting local File Cabinet Server"
	>%RUN-S-PROC_ID, identification of created process is 20C00A8A
	>%OA-I-LASTLINE, ERROR STARTING SERVER DEKV03::"73="
	>%OA-I-LASTLINE, "ALL-IN-1 running -- Populating partition data"
	>%OA-I-LASTLINE, File Cabinet Server DEKV03::"73=" is not available
	>%OA-I-LASTLINE, The default MAIN drawers have NOT been seeded
	>%OA-I-LASTLINE, Please check the log file SYS$MANAGER:OAFC$SERVER.LOG

2.  oafc$server.log

	>2-JUN-1994 16:26:19.98  Server: DEKV03::"73="  Error: %OAFC-E-INTERR,
	>Internal error in File Cabinet Server  
	>Message: PCAdd; Partition already in name cache.

3.  I can't find object OBJ_73 at network.

T.R	Title	User	Date	Lines
4230.1	?	IOSG::STANDAGE	`Fri Jun 03 1994 09:27`	22
	HJ, Did the server only log this message and then die ? You could try running the server in the foreground, as that can sometimes give you more information : $ SRV=="$SYS$SYSTEM:OAFC$SERVER.EXE" $ SRV OA$DATA_SHARE:DEKV03$SERVER73.DAT Is this a cluster ? - I take it DEKV03 is either a standalone node or the node you installed from within the cluster. Check that SCSNODE and SCSSYSTEMID are defined in SYSGEN, although typically that throws up different errors to the one you are seeing. I have to confess this one looks a little peculiar ! Kevin.
4230.2	meaning of "partition already in name cashe" ?	DEKVC::ALLIN1	`Tue Jun 07 1994 09:38`	52
	Kevin, > Did the server only log this message and then die ? No, installation procedure was completed with IPVs failed . > You could try running the server in the foreground, as that can > sometimes give you more information : The result was the same as those messages of oafc$server.log. > Is this a cluster ? - I take it DEKV03 is either a standalone node or the > node you installed from within the cluster. Yes, our system is as below. DEKV01 & DEKV02 (Product system) :homo cluster DEKV03 (Test system) :hetero cluster with DEKV01& DEKV02 > Check that SCSNODE and SCSSYSTEMID are defined in SYSGEN, although > typically that throws up different errors to the one you are seeing. Those were defined in SYSGEN. As installation was failed at postinstallation step, current version was changed to v3.0 but, menu screen when ALL-IN-1 invoked was still v2.4. I don't understand the meaning of oafc$server.log. "Partition already in name cache". Could you pls advise what I am to do for the further checking ? Thanks & Regards, HJ. ----------------------------------------------------------------------------- PS. Hope below files may be references for your grip of current my problem status... I copied 3 files to DEKVC::. 1. Install log file : dekv03_a1v30.log 2. IVP log file : allin1_ivp.log (Except the FCS, Create account checking & Electronic mail checking were failed during the IVP procedure.) 3. ALL-IN-1 A/Cs UAF list : allin1_uaf.txt (I'm not sure if default device "NL:[user]" (for OAFC$DEFAULT )& "NLA0:[user]" (for OAFC$SERVER) were correct or not. Because those device names were undefined logicals.)
4230.3		IOSG::STANDAGE	`Tue Jun 07 1994 10:28`	34
	HJ, Ah, so this is a hetrogeneous cluster ! This configuration is not strictly supported by the file cabinet server, although we have produced a one-off ICF to resolve a problem. However, this should not cause the server to immediately die, only that sharing drawers get's broken. The ICF was to resolve drawer sharing problems, and nothing else. When a server connects to another server, they swap information regarding the partitions they know about (in the Partition Cache). Somewhere along the way, it appears as though your servers are getting confused and attempting to connect to themselves. This would probably cause them to crash out, and possibly log the message "partition already in name cache" (as they already know about themselves). The OAFC$DEFAULT account is used when remote people are connecting to your local system. The OAFC$SERVER account is more important, the device names have to be correct for this ! I will try and look at your log files when I can. Unfortunately I have to prepare for a customer visit. Kevin.
4230.4	waiting any advise ....	DEKVC::ALLIN1	`Mon Jun 13 1994 07:29`	20
	Hi, Kevin > When a server connects to another server, they swap information > regarding the partitions they know about (in the Partition Cache). > Somewhere along the way, it appears as though your servers are getting > confused and attempting to connect to themselves. This would probably > cause them to crash out, and possibly log the message "partition > already in name cache" (as they already know about themselves). If server connect to themselves was the reason, how I can prevent/solve it ? I looked over the whole relative notes and manuals but, can't find any hints for the messages. When I run OAFC$STARTUP.COM , FCS process created for a while and then die soon. Hoping you aren't so busy... HJ.