Archived

This forum has been archived. Please start a new discussion on GitHub.

Possible cause of Replica down.

During the running of icegridregistry, hit a case which the process has stopped with replica down message in the ice.<host>.stderr

-- 12/26/11 07:03:53.614 icegridregistry: Replica: replica `Replica3' down

Any advice on troubleshooting the root cause? Should there be a dump file generated, and if so where should it be located?

Thanks.

Comments

  • bernard
    bernard Jupiter, FL
    Hi Vic,

    You should have a look at the log file of the icegridregistry named "Replica3". The location of this log file depends on the configuration of this icegridregistry; it could be for example a simple file, or the Windows Event log (on Windows), or /var/log/messages (on Linux).

    Best regards,
    Bernard
  • Looking at the config, doesn't look like replica log path was overridden. However, didn't see a log named "Replica3" under /var/log.

    IceGrid.InstanceName=IceGridAP
    IceGrid.Registry.Client.Endpoints=tcp -p 14099
    IceGrid.Registry.Server.Endpoints=tcp
    IceGrid.Registry.Internal.Endpoints=tcp
    IceGrid.Registry.AdminPermissionsVerifier=IceGridAP/NullPermissionsVerifier
    IceGrid.Registry.Data=/var/tmp/icegrid/registry
    IceGrid.Registry.DynamicRegistration=1
    IceGrid.Registry.Trace.Replica=1
    IceGrid.Registry.Trace.Node=1
    IceGrid.Node.Trace.Replica=1

    Please advice.
    Thanks
  • bernard
    bernard Jupiter, FL
    Hi Vic,

    This 'Replica3' icegridregistry is most likely running on another computer (or was running since it's now down).

    The config file of the Replica3 IceGrid registry contains:
    IceGrid.Registry.ReplicaName=Replica1
    

    (See the manual for details).

    If there is no log-related configuration in this file, your application (here: icegridregistry) uses the default logger, i.e. it outputs all messages to stderr.

    You may want to switch to one of the built-in loggers.

    Best regards,
    Bernard