Skip to content

rConfig Vector – Troubleshooting

8 mins Vector

Troubleshooting Common Issues with rConfig Vector

1. Introduction

The rConfig Vector is a powerful solution for managing and monitoring network device configurations across distributed systems. While it is designed to be efficient and reliable, common issues may arise during installation or operation. This guide aims to help you troubleshoot and resolve such problems quickly and effectively.

2. Common Installation Issues

2.1. Service Setup

  • Symptom: Service fails to start or encounter errors during startup.
  • Solution: Ensure the service is properly configured with the correct permissions. The service requires root access on Linux or Windows Administrator privileges to write logs and temporary files locally. Verify that the service is enabled and set to run on startup.

2.2. Disk Permissions Issues

  • Symptom: Unable to write logs, temporary backups, or database files.
  • Solution: Check that the directories appDir/Data/Logs, appDir/Data/Files, and appDir/Data/Db have the correct write permissions. On Linux, use chmod to set appropriate permissions, and on Windows, ensure the service has write access to these directories. Verify that there is sufficient disk space available.

3. Network Connectivity Issues

3.1. Firewall or Port Blocking

  • Symptom: Unable to communicate with devices or the Vector server.

  • Solution: Check the following potential blockers:

    • Host firewall settings
    • Network firewalls
    • Any network security appliances in place

    Ensure that outbound traffic to the Vector server is allowed on the necessary ports.

3.2. SSL/TLS and Packet Loss Issues

  • Symptom: Communication disruptions due to incorrect SSL setup or network issues.
  • Solution:
    • Verify that SSL is configured correctly and using TLS 1.2 or higher.
    • Test the network for packet loss and resolve any connectivity issues that may impact performance.

3.3. Source IP Address Issues

  • Symptom: Agent unable to establish a connection due to source IP mismatch.
  • Solution: Verify that the source IP address of the agent matches the IP configured on the Vector server.
    • If the agent is behind a NAT device, ensure that the correct external IP is configured.
    • For systems with multiple IP addresses, confirm that the expected source IP is being used for communication.

4. Network Device Config Backup Errors

4.1. Backup Fails or Skipped Devices

  • Symptom: Backups incomplete or failing during execution.
  • Solution:
    • Check the backup log files located under appDir/Data/Logs for errors.
    • Enable debugging for the agent from the Vector server configuration page. Once enabled, the next agent sync will start generating verbose output in the logs.
    • As of Vector Agent version 1, advanced debugging may be required for complex issues. This could involve installing Go on a test system and running custom scripts as instructed by the rConfig support team. For further assistance, see the Contacting Support section.

5. Performance Bottlenecks

5.1. High CPU/Memory Usage

  • Symptom: System performance issues or service crashes.
  • Solution: Monitor server resources and optimize task queue configurations.

5.2. Excessive Device Polling

  • Symptom: Network congestion or delayed configuration updates.
  • Solution: Adjust polling intervals and review scheduled jobs.
    • Ensure there is enough time between device job intervals to prevent overlap or overloading. This timing is variable and can depend on the number of devices and the frequency of polling. Proper scheduling helps avoid jobs crossing over or interfering with each other.

6. API Integration Issues

6.1. API Call Timeouts

  • Symptom: API requests fail or take longer than expected.
  • Solution:
    • Check network connectivity to the API server and increase timeout settings if necessary.
    • Enable debugging for the agent from the Vector server configuration page. Once enabled, the next agent sync will start generating verbose output in the logs.
    • Advanced debugging may be required for complex API issues. This could involve installing Go on a test system and running custom scripts as instructed by the rConfig support team. For further assistance, see the Contacting Support section.

6.2. Incorrect API Responses

  • Symptom: Unexpected or missing data returned by the API.
  • Solution:
    • Verify API endpoint URLs, authentication, and request parameters.
    • Enable debugging for the agent from the Vector server configuration page. Once enabled, the next agent sync will start generating verbose output in the logs.
    • Advanced debugging may be required for complex issues. This could involve installing Go on a test system and running custom scripts as instructed by the rConfig support team. For further assistance, see the Contacting Support section.

7. Logging and Monitoring

All logs generated by the Vector Agent are stored locally and uploaded to the Vector server at scheduled intervals.

7.1. Local Log Locations

  • Operational Logs: appDir/Data/Logs
  • Temporary Config Backups: appDir/Data/Files
  • Temporary Databases: appDir/Data/Db

7.2. Viewing Logs on the Vector Server

Logs uploaded to the server can be accessed from the Settings > Agent page on the Vector Server dashboard.

8. Queue Troubleshooting

The queue is a critical component of rConfig Vector, responsible for tracking and managing jobs.

8.1. Accessing the Queue

  • Navigate to the Settings > Agent page on the Vector Server to view the queue.

8.2. Understanding the Queue

  • Waiting Jobs: Jobs waiting to be retrieved by agents.
  • Past Jobs: Jobs that have already been processed and sent to agents.

8.3. Common Queue Issues

  • Stuck Jobs: Jobs that remain in the waiting state.

    • Solution: Verify the agent’s connection and log files for any errors.

  • Delayed Job Execution: Jobs take longer than expected to execute.

    • Solution: Check the agent’s system resources and the frequency of scheduled tasks.

  • Failed Jobs: Jobs that are marked as failed in the queue.

    • Note: The hardcoded default is to attempt a download only once. If the download fails, the job is marked as invalid and is not retried by the agent. This behavior can be modified in the device template under the ‘connect’ section by adding a new key-value pair called retries and setting its value higher than one. However, this is generally not recommended, as it aligns with the default settings of rConfig Pro.
    • Solution: Review the job-specific error messages available in the job history section of the queue.

9. Contacting Support

  • Before reaching out to support, gather the following:

    • System and service logs from the Logs section.
    • Details about the specific issue, including any error messages.

  • Support Channels:

1o. Conclusion

By following the steps outlined in this guide, you should be able to troubleshoot most issues related to rConfig Vector. For any unresolved problems, please contact our support team. Your feedback helps us improve and enhance rConfig Vector for all users.