Glenn A Mitchell wrote:

> I am having trouble getting ARMServr to talk to my newly installed AutoRaid 12H.
> 
> I have followed the instructions in readme.doc as best I can.  The syslog
> daemon seems to be running fine.  The JARMSRVD job seems to be running fine
> and I get the following message on the console just after streaming it:
> 
> :11:00/#J25/46/Jan 16 11:00:42 localhost syslog: ArmServr Started
> 
> However, when I try to talk to the array, I get the following:
> 
> shell/iX> cd /opt/hparray/bin
> shell/iX> ./arraydsp -i
> Arrays known to the ARMServer:
> No arrays were found by the ARMServer
> 
> I should note that ./arrayscan runs normally; sees the array; and creates
> the appropriate /dev/autoraid# files on my system as well as the DeviceList
> file:
> 
> shell/iX> cat DeviceList
>  LDEV-TYPE            STATUS    VOLUME           VOLUME SET - GEN
>  ----------           -------   ----------------------------------
>     1-C5447A          MASTER    MEMBER1          MPEXL_SYSTEM_VOLUME_SET-0
>     2-C5447A          MASTER    MEMBER2          PROD1_SET-0
>     3-C5447A          MEMBER    MEMBER3          PROD1_SET-0
> 
> Also, while I'm asking, is there a way to terminate the syslog and JARMSRVD
> jobs "normally", i.e. without doing an ABORTJOB?
> 
> TIA for your help.
> 
> Glenn

It has been a lot of years since I fooled around with the Armserver but 
here are a few things I can recall that you should look at.

First off; what release of MPE/iX are you on? And, what Armserver patch, 
if any do you have installed (these would start with "ARM").

If the Armserver started properly then the $stdlist for the job should 
contain something that looks like this:

  :xeq /opt/hparray/bin/ARMSRVD
  ./arrayscan status: Success.
  ControllerSN: R87RADF121451111 PairSN: R87RADF121411111 BackPlaneSN: 
000000136CA9

You can "tail" /tmp/syslog.log after starting the Armserver to see if it 
has correctly started up. The log entries should look something like this:

Jan 16 14:06:19 localhost syslog: HP Advanced Disk Array serial number 
?: ARM debug: Device Manager Constructor Called
Jan 16 14:06:19 localhost syslog: HP Advanced Disk Array serial number 
?: ARM debug: Controller Identified for backplane id 000000136CA9
Jan 16 14:06:19 localhost syslog: HP Advanced Disk Array serial number 
?: ARM debug: Device Manager found 1 subsystems from 1 controllers
Jan 16 14:06:19 localhost syslog: HP Advanced Disk Array serial number 
?: ARM debug: Device Manager InitComplete Called
Jan 16 14:06:19 localhost syslog: ArmServr Started

Finally, Armserver wants a "localhost" configured. This is done in 
either /etc/hosts or /etc/resolv.conf if using domain name services. The 
quick test is to see if you can ping localhost. On the 3000 this would 
be done using NETTOOL.NET.SYS. There may also be a PING.NET.SYS 
symbolically linked to /etc/ping but I couldn't get that to accept 
"localhost" where the NETTOOL version does.

On your second question regarding stopping syslog and the armserver; 
normally in the shell you'd do something like this:

kill -s TERM <pid of the process to stop>

Things like Apache and Syslog write their pids into a file so that 
terminating the process can be automated. For example:

shell/iX> kill -s TERM `cat /SYSLOG/PUB/syslog.pid`

Or, from the MPE/iX CI:

:xeq sh.hpbin.sys "-c 'kill -s TERM `cat /SYSLOG/PUB/syslog.pid`'"

Unfortunately the Armserver doesn't write its pid into a file like this. 
And, it also doesn't respond to SIGTERM (as far as I can tell). So you 
would have to extract the pid from something like the output of "ps -ef" 
and then stop it using SIGKILL (-9). This isn't very graceful and for 
all intents and purposes is just the same as doing an abortjob on JARMSRVD.

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 *