How to turn on debug logging for Hystax VMware Replication Agent

How to turn on debug logging for Hystax VMware Replication Agent

Task

Turn on debug logging to perform advanced troubleshooting of Hystax VMware Replication Agent (HVRAgent)

Solution

Go to the agent console and create a flag to enable debug logging by creating a flag file with the following command:
sudo touch /hx/cabrio/flags/debug_logs

The next step is to restart services in TUI.



You can see the logs in agent TUI or in file /var/log/cabrio/cabrio.log


    • Related Articles

    • How to turn on debug logging for Hystax Linux Replication Agent

      Task Turn on debug logging to perform advanced troubleshooting of Hystax Linux Replication Agent (HLRAgent) Solution Stop the HLRAgent service with the following command: sudo service hlragent stop Enable debug logs, set the value ...

    • How to turn on debug logs for Hystax Windows Replication Agent

      Task Turn on debug logging to perform advanced troubleshooting for Hystax Windows Replication Agent (HWRAgent). Solution HWRAgent is running as two separate processes - HWRAgent service and Replication Manager (Repman_x64.exe), so you need to turn on ...

    • List of log files locations

      Log files locations, by agent type: Agent type Log file location Windows replication agent %ProgramData%\Hystax\acura\LOG\repman.log %ProgramData%\Hystax\acura\LOG\hwragent.log.txt Linux replication agent /var/log/repman.log VMware replication agent ...

    • How to edit the "hosts" file of a VMware agent

      Task Edit the "hosts" file of a VMware agent. Solution The "hosts" file of the VMware agent is mounted into the agent system and can be edited from its console. Perform the following steps: Go to the agent command line by pressing the "To console" ...

    • How to change network settings of an Agent in VMware

      Challenge Hystax VMware Agent (HVRAgent) is deployed as a virtual machine to a source ESXi host. It uses DHCP for its single NIC by default. However, these default settings might not work in case the source VMware infrastructure doesn't have DHCP or ...