PingDirectory

Replication subcommand logs and exit codes

To preserve important troubleshooting and support information, PingDirectory Server logs dsreplication subcommand executions, grouped by name, in the logs/tools directory. By default, the server retains the output from the last 10 executions for each subcommand (such as status, enable, and initialize). You can use these logs to review or troubleshoot the execution of a specific subcommand within the retention window.

The retention policy for these logs is not configurable.

If a dsreplication subcommand returns a non-standard result code, such as in the event of an error, the server generates a special log file that gets:

  • Published to the logs/tools directory

  • Named according to the result code and timestamp of the execution

  • Compressed and retained indefinitely

Check these logs first to more quickly and effectively determine a root cause.

These non-standard logs should be created by the server infrequently and contain valuable information for support technicians. Don’t delete these files unless necessary. When you run the collect-support-data tool, it generates a support package that includes all non-standard logs and the six most recent logs for each subcommand.

dsreplication exit codes

The following table details the exit codes that the server logs for dsreplication subcommand executions. Use these codes to troubleshoot errors with replication operations.

Exit code Details

0

  • Successful.

  • Successful, but no operation was performed.

1

Unable to initialize the arguments.

2

Can’t parse the arguments because the user-provided arguments aren’t valid or there was an error checking the user data.

3

The user canceled the operation in interactive mode.

4

There was an unexpected error (potential bug).

5

The provided base DNs can’t be used to enable replication.

6

The provided base DNs can’t be used to disable replication.

7

The provided base DNs can’t be used to initialize the contents of the replicas.

8

Error connecting with the provided credentials.

9

Couldn’t find the replication ID of the domain to be used to initialize the replica.

10

Exceeded the number of tries to start initialization. The server systematically receives a peer not found error.

11

Error enabling replication on a base DN.

12

Error initializing a base DN.

13

Error reading the configuration.

14

Error updating the topology registry.

15

Error reading the topology registry.

16

Error reading TopologyCache.

17

Error configuring the replication server.

19

Error disabling replication on a base DN.

20

Error removing the replication port reference on a base DN.

21

Error initializing the administration framework.

22

Error seeding the truststore.

23

Error launching pre-external initialization.

24

Error launching post-external initialization.

25

Error disabling a replication server.

27

The server must be offline to perform the operation.

28

Error updating the server configuration.

29

The server is unavailable (either can’t be contacted or has an active unavailable alert).

30

The server joining the topology has the replication set defined, but no restricted domains have been selected.

31

Failed to lock the topology for a subcommand that requires no other commands running.

32

The location provided on the command line didn’t match the location set in the server.

33

One or more replicas aren’t connected to the replication topology when executing the initialize-all subcommand.

34

One or more replicas didn’t complete the import in a timely fashion.

35

Either the first server, the second server, or both are running an older PingDirectory version than the one used for dsreplication.

36

Initialization didn’t complete because it was canceled.

37

The remove-defunct-server subcommand was invoked for a still active server.

38

The remove-defunct-server subcommand was invoked with a defunct replication port that doesn’t match the server’s replication port in the topology registry.

39

The server is part of a mixed-version environment where some servers support the topology registry and others do not.

40

The replication subcommand is no longer supported.

41

Problem parsing the topology JSON file.

42

The internal seed server required to concurrently enable replication is unavailable.

43

The internal seed server required to enable replication is the same as the server added to the topology.

44

The base entry for the given base DN to replicate couldn’t be added on both servers.

45

The server doesn’t have mirrored subtrees, but the dsreplication disable command is being run from a server that does.

100

Other error.