[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
3007.0. "Filecab server fails to start - Timeout !" by RDGENG::AWILLIAMS () Wed Jul 14 1993 17:26
I have been having problems getting the filecab server to run.
STA from the MS menu seemed not to work but the DOOZER$SRV process
gets created.
I looked through the ALL-IN-1 S.M. Guide which suggests running the
image manually.
Start_server :="$osfc$$server"
start_server oa$data_share:doozer$server73.dat doozer$srv73
This worked and the status window changed to started/enabled.
I have had a look through the log file (oa$log:OAFC$SERVER_STARTUP.LOG)
and it seems that I am experiencing a timeout problem. The command
procedure (SYS$COMMON:[SYS$STARTUP]OAFC$STARTUP.COM) has a loop which
attempts to read from a mailbox.
> $ try_write_again:
> $ IF loop .EQ. 120 THEN GOTO write_mbx_error
> $ WAIT 00:00:00.5
> $ loop = loop + 1
> $ OPEN/READ/WRITE/ERROR=try_write_again write_mbx 'write_mbx_name'
This eventually drops out. I have now modified the wait statement to read
WAIT 00:00:01
And this appears to have fixed it although it did take 89 seconds !
The cluster comprises of two 4000-500's and up until recently both servers
had been running smoothly.
A MON SYS shows virtually zero activity so why should it take to long to start ?
Maybe the command procedure being a little optimistic ?
Andy
T.R | Title | User | Personal Name | Date | Lines
|
---|