HP3000-L Archives

April 2002, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"HOFMEISTER,JAMES (HP-USA,ex1)" <[log in to unmask]>
Reply To:
HOFMEISTER,JAMES (HP-USA,ex1)
Date:
Mon, 22 Apr 2002 08:06:10 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
hello et all @ 3000-l,

RE: SA700 & Netcontrol Stop

Just a fyi:

I am working on a SA700 caused by an sockets application performing a
"gethostbyname" after a network shutdown was in progress.  The
":netcontrol stop" told NETCP.net.sys to shutdown all system network
process and delete the network data structures, but a timing window
exist where the procedures called from "gethostbyname" tried to read
a data structure which NETCP "just" deleted.  HP is working to fix
this problem, but...

The moral to this story is to avoid this problem and problems in
general, HP Recommends as Standard Operating Procedure:

1) Shutdown all socket programs
2) Shutdown all network socket utilities like network spoolers or
   network data shadowing
3) Shutdown/Abortjob all Telnet and VT sessions as well as DSCOPY
   FTP, etc.
4) Stop the ARPA Services ":Abortjob JINETD" and the NS Services
   ":NSCONTROL STOP"
5) Netcontrol Stop.

Following this procedure will avoid the aforementioned SA700 and other
problems in general.

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2