HP3000-L Archives

September 2003, Week 3

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:
Dan Barnes <[log in to unmask]>
Reply To:
Dan Barnes <[log in to unmask]>
Date:
Wed, 17 Sep 2003 07:46:56 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
Thanks very much for the help gang.  We're up and running !  Dan

-----Original Message-----
From: Bill Cadier [mailto:[log in to unmask]]
Sent: Tuesday, September 16, 2003 1:59 PM
To: Dan Barnes; [log in to unmask]
Subject: Re: Re: [HP3000-L] JARMSRVD Startup Problem


Dan writes

> The file is in fact there. I removed it, but then get the following on the
> console when I try to restart it:
>
> 12:18/#J64/697/LOGON FOR: "JARMSRVD,MANAGER.SYS,MANAGER" ON LDEV #10.
> 12:18/#J13/689/Sep 16 12:18:49 localhost syslog: ArmServr Started
> 12:18/#J13/689/Sep 16 12:18:49 localhost syslog: ArmServr:
> DatagramEar::InitTask
>  bind
> 12:18/#J13/689/Sep 16 12:18:49 localhost syslog: ArmServr: Ear::InitTask
> bind
> 12:18/#J64/697/LOGOFF ON LDEV #10.
>
> ... and in the stdlist ...
>
> :xeq /opt/hparray/bin/ARMSRVD
> ./arrayscan status: Success.
> ControllerSN: R07RADK258681111 PairSN: R07RADK260051111 BackPlaneSN:
> 00000025F6C9
> **** Data memory protection trap (TRAPS 68). ABORT:
> /opt/hparray/bin/ARMServer **** Unknown trap (TRAPS 69). ABORT: /opt/h
> NM PROG  7cf.000e163c fileno
> sh.hpbin.sys
> Program terminated in an error state. (CIERR 976)
> REMAINDER OF JOB FLUSHED.
>
>
> Dan

If the network is configured correctly then there is only one more thing I
can think of that
might correct this; remove the logfiles from /var/opt/hparray/log. You can
store them if you
wish and purge them as they're stored or just purge them if this is a test
system and you
don't need to retain them. You can purge store and purge the 'LOGCATLG' file
too, it will be
recreated (assuming the armserver fires up).

I have never understood why this works but there have been cases where doing
this has
resolved problems that appear to be like yours. The difficulty is that
pretty much any time the
armserver rolls over it will appear to be what you're seeing so it is
difficult to know exactly
what may be causing it.

If that doesn't resolve the problem then you should contact the Response
Center or who ever
provides your software support for some help.

hth,

Bill
hp/vCSY

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

ATOM RSS1 RSS2