Bill,

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


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Bill Cadier
Sent: Tuesday, September 16, 2003 11:59 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] JARMSRVD Startup Problem


Dan writes:

> 3000-L Gang,
>
> On a series 979-200 running 7.0 PP2, the job JARMSRVD.PUB.SYS gets the
> following error on startup after a node name change in nmmgr (not sure of
> the relation, but that _did_ just get changed on a test box I am working
on
> and this process was running before the reboot....):
>
>
> XEQ /opt/hparray/bin/ARMSRVD
> ./arrayscan status: Success.
> ControllerSN: R07RADK258681111 PairSN: R07RADK260051111 BackPlaneSN:
> 00000025F6C9
>
>     Copyright (C) 1995 Hewlett-Packard Company
> ArmServr: osctrlr::ServerLock Unable to open server lock file; errno = 50
> DEBUG/iX C.39.06
>
>
> --> On the console I see .......
>
> 10:19/#J13/689/Sep 16 10:19:04 localhost syslog: ArmServr:
> osctrlr::ServerLock Unable to open server lock file; errno = 50
>
>
> TIA !
>
> Dan

The ARMServer's 'lock file' is

/var/opt/hparray/ARMServer.lock

The file is empty, its only purpose being to prevent more than one ARMServer
from running. If the file were missing the ARMServer would create a new
copy.
If the file happened to be accessed by something else then you'd see same
error.
It's unlikely something else would be accessing that file but it's worth
checking
first.

One common gotcha with the ARMServer is that it relies on the ability to
locate
localhost (127.0.0.1) and the name of the server on which it's running.
Since you
just changed the name of the system the solution may be as simple as adding
the
new system name to /etc/hosts (hosts.net.sys) or getting the new name added
to
your domain name server.

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 *

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