hendersj Acclaimed Contributor.
Acclaimed Contributor.
320 views

Re: -637 Error when deleting a replica

On Sun, 17 Jun 2012 15:36:01 +0000, antoniogutierrez wrote:

> Then I have the famous -637 error. So, I tried to run ndsrepair with all
> posibles switches and I have the same error.


-637 - PREVIOUS_MOVE_IN_PROGRESS (the definition) is typically caused by
a communications error. ndsrepair won't fix that.

Pull up iMonitor and go to the replica status - that should tell you
which server is having the communications error and which server it's
trying to communicate with. Fix that issue and the obit should process
and the error will clear out.

Jim



--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner
Labels (1)
0 Likes
2 Replies
hendersj Acclaimed Contributor.
Acclaimed Contributor.

Re: -637 Error when deleting a replica

On Sun, 17 Jun 2012 17:36:01 +0000, antoniogutierrez wrote:

> Are you sure? I think that the communication between my replicas are ok:
> On iMonitor on the master server I see that all servers are marked with
> "active" (replica status) and on the "delta reception" column,
> I see less than 1 minute, of the last sync...


Yes, I'm sure.

Previous move in progress is caused by a stuck INHIBIT_MOVE obit. It's
the /only/ thing that causes that error.

By going where I said in iMonitor and looking, you can see where the
error originates.

It isn't necessarily servers in the replica ring - a stuck INHIBIT_MOVE
obit can be caused by a secondary backlink obit being hung up on the move
operation that took place. As such, it can be communications between the
master and a server that holds an extref of the object that is holding up
the move as well as just within the replica ring.

The INHIBIT_MOVE obit is placed on the object at the destination replica
as well - the purpose is to prevent an object from being created with the
same name while the obit states advance.

Jim
--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner
0 Likes
hendersj Acclaimed Contributor.
Acclaimed Contributor.

Re: -637 Error when deleting a replica

On Sun, 17 Jun 2012 18:36:01 +0000, antoniogutierrez wrote:

> And other question. You say that the problem is maybe not related to the
> replicas on the ring. So, maybe the problem is related to a server that
> cant communicate on the "know servers" page?


Very likely.

> Because, on the replica status I see that all the replicas are ok, but
> on the "know servers" I have 23 servers in total, but 2 inactive. Maybe
> this is the problem, or its related?


Are the two servers down? If they are, chances are they hold (or held,
if they've been removed from the tree) extrefs of an object.

I'd run an obit report on the server that holds the master replica of
each partition and see what comes back.

Jim



--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.