Repman process exits unexpectedly indicating a status code in logs
Challenge
Repman process, as a part of the internal agent service, fails and exits with a certain status code.
Cause
After installing an internal agent on your VM, there should be 2 new services running in the background: repman and hlragent/hwragent (in Linux or Windows, respectively).
Sometimes, repman process can exit unexpectedly and without user's provision. In that case, lincbt will generate a similar record in the logs:
Repman process exited: status(1), signal(0)
If you need more information on what goes wrong with the process and its follow-up, repman can be started separately from the hlragent service in Linux using:
/usr/bin/hlragent/Repman_x64
or from the hwragent service in Windows using:
C:\Program Files (x86)\Hystax\hwragent\Repman_x64.exe
There is a different status code (2) in the instances where repman.conf is broken or invalid.
Please submit a new support request and attach agent log files if the problem remains.
Related Articles
Replication with VMware agent fails with the message: Backup creation failed with code 500
Challenge Replication with VMware agent fails with the following error message: "Backup creation failed with code 500, reason: Command '['umount', '/tmp/e9dc80e9-0a54-4991-9003-edeffd7e4920']' returned non-zero exit status 32" Cause In case of using ...How to replace Windows replication agent's config file in case a machine is shown offline in ACP
Challenge A machine is shown offline in ACP, although the source instance is running and has been replicated successfully before. Cause The replication agent's config file might have become corrupted during an unexpected termination of the repman ...Replication fails with an error: "Failed to create backup on device. Internal library error. Failed build snapshot sequence"
Challenge Replication fails with the following message in Acura's Events section or in the agent's logs: "Failed to create backup on device <...>: Internal library error. Failed to filter snapshots Failed to find end snapshot(<...>). Failed build ..."Module build for the currently running kernel was skipped" message in console during Replication agent's installation
Challenge During the installation of a Linux replication agent (hlragent) with DKMS, the following message can be displayed in the console: Module build for the currently running kernel was skipped since the kernel source for this kernel does not ...Why Windows replication fails with Hystax VMware Replication Agent - quiesce failure
Challenge Replication fails when a Windows machine is being replicated with Hystax VMware Replication Agent with the following error message: "Backup creation failed with code 500, reason: An error occurred while quiescing the virtual machine. See ...