Conference smurf::buildhelp

2110.0. "re DECode II hangs during boot" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Fri Feb 16 1996 15:26

Date Of Receipt: 	16-FEB-1996 14:32:28.04
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  16-Feb-1996 1429"
To: 	hewitt@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	re  DECode II hangs during boot

Alex, I think you'll find this helpful...

------- Forwarded Message

To: bagley
Cc: odehelp, glidden
Subject: Re: ODE start up problem - odemount hanging?
In-Reply-To: Your message of "Tue, 06 Feb 96 13:08:39 EST."
             <[email protected]> 
Date: Tue, 06 Feb 96 14:16:03 -0500
From: "Joshua M. Friedman, OSF/UNIX SDE 381-1548" <jmf>
X-Mts: smtp

Dick,

Is your system setup as an ode client (it should be a client, not
a server).  Is it setup to do odemounts at bootup?  If you're doing
odemount -all, this mounts about 150 filesystems; you may want to
change this to only mount the trees you really use.

There was a change in odemount recently - when you reboot, if you're
setup to call odemount (grep ODEMOUNT /etc/rc.config), then this odemount
uses the -bg switch.  It used to cause odemount to call mount as follows:
	mount filesystem directory &
	mount filesystem directory &
	...
It now does
	mount -o bg filesystem directory
	mount -o bg filesystem directory
	...

Where the 'bg' switch, from the 'man mount' reference page is defined as:

  bg  Retries in the background, if the first mount attempt fails.


If this is hanging your system (some nfs exports may be unavailable),
then this may be a bug in the version of UNIX you're running.  You may
want to file a QAR against Digital UNIX (not ODE).

Try this as a workaround:  modify the file /sbin/init.d/ode3.0 to call
odemount in the background, and to log its output.
I.e., at line 80 of this startup script, change the command from:
  /usr/sde/${ODE_DEFAULT_DIR}/tools/common/odemount ${ODEMOUNT3_OPTS}
  ${ODE_ODEMOUNT_STRING} > /dev/null 2>&1

to:
  /usr/sde/${ODE_DEFAULT_DIR}/tools/common/odemount ${ODEMOUNT3_OPTS}
  ${ODE_ODEMOUNT_STRING} > /var/adm/odemount.log 2>&1 &
                           ^-changed to a file and    ^-added the '&'

If this isn't at line 80 you may have an old startup that isn't calling
using the -bg switch.  Rerun '/usr/sde/install/ode install' if this is
the case.

If anything useful shows up in the log file it may help diagnose the problem.

- -josh


- --------
To: [email protected]
Cc: [email protected]
Subject: ODE start up problem 
Date: Tue, 06 Feb 96 13:08:39 -0500
From: [email protected]
X-Mts: smtp


- ------- Forwarded Message

Date: Tue, 6 Feb 1996 10:27:29 -0500
From: Dick Bagley USG <bagley>
Message-Id: <[email protected]>
To: [email protected]
Subject: Unable to start ODE since yesterday...
Cc: bagley

Hi -

  I have a Noritake in my office that I installed DECode II V3.0 on some
  time ago. I've been using this system for my HW6 sandbox, backed to the
  hw6os.nightly backing tree.

  Yesterday, while re-booting the system to test out a new kernel with some
  changes I need to check into HW6, the system hangs after invoking
  /sbin/init.d/ode3.0 start. I get the message:

	DECode II V3.0 Starting Tue Feb  6 10:23:12 EST 1996

  Then nothing...After waiting quite awhile to see if I get an NFS error
  message, if I type a control/c, the system will complete booting up to
  the login prompt.

  Any help with this ? I need this system ASAP so I can srequest/submit
  some changes in before the end of the week.

  Thanks,

- - - dick bagley
  UHS_IO
  ZKO3-3/T23

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



------- End of Forwarded Message