Q: Problems with ASE 1.4

From: Gunther Feuereisen <gunther_at_ibm.net>
Date: Thu, 22 May 1997 09:25:12 -1000

Hi,

I'm currently configuring two AXP4000's in a DECSafe environment. I'm
using DU 4.0b and ASE 1.4.

I'm testing failover with disk based services, and have the current problem.

- Relocating from one machine to another works fine.
- If the service is on the "A" machine, and I reboot "A", the daemon.log
reports a new
  director starting, and then it sits there with the message:

May 22 09:04:27 pofreb ASE: pofreb Agent Notice: starting a new director
May 22 09:04:28 pofreb ASE: send_to_instance: have to have destination

  It then sits there until it detects the "A" machine as beiing up again,
and then starts
  the service:

  If I reverse the situation with the "B" machine, the same thing happens
again, further
  I get the following additional error:

May 22 09:11:49 pofrea ASE: pofrea Agent Notice: agent on pofreb should
start director, but isn't in RUN state
May 22 09:11:50 pofrea ASE: pofrea Agent Notice: starting a new director
May 22 09:11:53 pofrea ASE: send_to_instance: have to have destination

  Now I have information to point to a possible hardware fault, and that
where I believe
  the problem lies at this stage (it came pre-built from Digital). Without
opening anything
  up, I'm hazarding a guess at a KZPSA with either the internal termination
on (although
  the console reports it isn't) or a defect of some sort. An engineer will
be out to verify
  the hardware today.

  I get similar problems if I halt a machine, except that the service never
starts up
  again, and hangs on the "send_to_instance" until the other machine is
booted.

  My questions for the ASE Admins out there are:

Question 1:
----------
  I have never seen the "send_to_instance" message before, and was
wondering if anyone
  had seen it, what it might mean etc.

Question 2:
----------
  My service is set up to be a balanced policy, with no relocation should
another member
  come up, and no favoured members. I don't understand why I am getting the
following
  the "agent on pofreb should start director, but isn't in RUN state" error
on one machine.

  Any ideas/comments/thoughts/discussion would be most welcome.

  Many Thanks,
  Gunther Feuereisen
Received on Thu May 22 1997 - 01:30:39 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:36 NZDT