Thread Info
  • State Verified Answer
  • Replies 10 replies
  • Subscribers 6 subscribers
  • Views 4645 views
  • Users 0 members are here
Options
Suggested

HA_pair service stopped

Paul Warriner

I tried to Quick HA pair a set of XG210's using ports 6, then 3, but they would not pair.

I was able to manually set the HA on port 6, but the HA_pair service continues to warn it is stopped.

The units are paired.

I see in the log where it warns SSH could not be configured, :

ha_pair.log

sleeping...
...done
{ "status": "544", "statusmessage": "configure SSH failed" }
sleeping...
...done
{ "status": "544", "statusmessage": "configure SSH failed" }
sleeping...
...done
{ "statusmessage": "configure SSH failed", "status": "544" }
sleeping...

Anyone know a way to clear the warning?

 

Thanks,

Paul 

Parents
  • 0

    Just to complete the loop.

    After cancelling the HA_pair (due over 30 minute hang), manually pairing, and having primary enter a failed state (after rebooting to clear warning), I found primary was using a 2 month old configuration (from the looks of the IP scheme and ports available, assuming from my original v18 EAP1 config).

    Drive and memory tests were done successfully.

    Did a factory reset on faulting primary with v18 EAP3 firmware in USB slot 1.

    Restored auxiliary backup (last primary backup [post HA_pair attempt] was corrupt) to unit, but did not enable HA on the primary.

    Leaving old primary as a standalone, until time allows a reset on the auxiliary (to ensure it's HA doesn't putz with things). Then will try HA again (most likely with GA release, unless time allows rebuilding an EAP release).

Reply
  • 0

    Just to complete the loop.

    After cancelling the HA_pair (due over 30 minute hang), manually pairing, and having primary enter a failed state (after rebooting to clear warning), I found primary was using a 2 month old configuration (from the looks of the IP scheme and ports available, assuming from my original v18 EAP1 config).

    Drive and memory tests were done successfully.

    Did a factory reset on faulting primary with v18 EAP3 firmware in USB slot 1.

    Restored auxiliary backup (last primary backup [post HA_pair attempt] was corrupt) to unit, but did not enable HA on the primary.

    Leaving old primary as a standalone, until time allows a reset on the auxiliary (to ensure it's HA doesn't putz with things). Then will try HA again (most likely with GA release, unless time allows rebuilding an EAP release).

Children
No Data
Unfiltered HTML