Home / Repstance User Guide / TROUBLESHOOTING AND FAQ / Logs and Information for Support

Logs and Information for Support

Where Repstance writes what it does, how to get more detail, and what to collect before you contact support.

Where to look

What	Where
The state of a process and its last error	repcli status and the dashboard of the Web UI (see Status of any Capture or Apply Processes)
The log of a process	The file /opt/repstance/log/capture-{id}-dd-mm-yyyy.log or apply-{id}-dd-mm-yyyy.log, a new file every day for every process. For example capture-1-04-10-2026.log is the log of the Capture Process 1 of 4 October 2026
The incidents: errors and warnings	Incident Management of the Web UI (see Monitoring Replication), kept in the files /opt/repstance/log/inc_dd-mm-yyyy.im
The messages of the server: start-up, check of the product or of the license key, ports	The service log: sudo journalctl -u repstance, and sudo journalctl -u repstance_ui2 for the Web UI (see Access and Product Validation)

Each line of the log of a process starts with the date and the time of the server, in its local time: 2026/10/04 15:47:00. The times that the status shows for the changes of the database are UTC. Repstance does not delete the log files, see Housekeeping.

More detail: the debug level

The parameter debuglevel of a process (0 to 15, the default is 0) says how much the process writes to its log: a line is written when its level is not higher than the value of the parameter. With 0 the log has the errors, the warnings and the main events of the process: its start and stop, the commands it receives. For an Oracle Capture Process the level 1 adds what each cycle did: the range that was read, and whether it found changes or nothing. The higher levels write much more, and some of them write the values of the rows, so use them only for a short time and when support asks for them.

The process reads the level when it is run. Stop the process, wait until repcli status shows it stopped, change the level, and run it again:

repcli stop process=capture id=1
repcli alter process=capture id=1 debuglevel=1
repcli run process=capture id=1

Set the level back to 0 afterwards. See Alter Process.

What to send to support

The version and the edition: rpm -q repstance (for example repstance-5.2.0279-AWS_AL2023, see How to Update Repstance).
The output of repcli status.
The log of the failing process for the days of the problem, with the lines before the first error.
The service log of the same days: sudo journalctl -u repstance --since "2 days ago".
The kinds and the versions of the Source Database and of the Target Database.
What was done before the problem: the commands, and when.
The settings of the processes without the passwords. repcli show process=capture id=1 prints the passwords of the databases as they are stored, so remove them first.

The log of a failed statement contains the values of the rows (the part SQL = [...] of an Apply Process). Look through the files before you send them. The trail files contain your data, send them only when support asks for them. Contact support through Contact Us.

Data Type Conversion

GLOSSARY