Troubleshooting

Experiencing issues with the ConHive Agent? Here are some common problems and solutions.

Agent Fails to Start

Permission Denied (Linux): Ensure the agent binary has execute permissions (chmod +x ./conhive-agent). Check permissions on the workdir and configs directories.
Port Conflict: The agent defaults to port 5050. If another service uses this port, the agent may fail. Check logs for errors like “address already in use”. Change the port in the agent’s configuration (agentmanager.json or similar).
Configuration Error: Invalid JSON in a configuration file can prevent startup. Check agent logs for parsing errors. Try running ./conhive-agent config create to reset to defaults (backup your existing configs first!) or validate your JSON files using an online validator.
Missing Dependencies: Although Go binaries are usually self-contained, check if any specific system libraries are unexpectedly required (unlikely but possible).

Check Service Logs: Use sudo journalctl -u conhive-agent.service -f to see detailed logs.
Check Service Status: sudo systemctl status conhive-agent.service might show error messages.
Incorrect Paths: Ensure the .service file points to the correct binary location and workdir.
Permissions: The user the service runs as (often root or a dedicated user) needs permissions to access the binary, workdir, and any resources the agent manages.

Agent Not Running: Verify the agent process is active (ps aux | grep conhive-agent on Linux) or the service is running.
Firewall: Check if a local firewall (like ufw on Linux or Windows Defender Firewall) is blocking port 5050.
Incorrect Port/Address: Confirm the listening address and port in the agent’s configuration. It might be configured to listen only on a specific IP address instead of 0.0.0.0 (all interfaces) or 127.0.0.1 (localhost).
Proxy Issues: If you’re using system or browser proxies, ensure they aren’t interfering with access to localhost.

Incorrect Configuration: Double-check the platform URL, agent ID, and authentication credentials in the relevant configuration file.
Network/Firewall: Ensure the device can reach the ConHive Platform URL over the network. Check outbound firewall rules on the device and any network firewalls between the agent and the platform.
Platform Status: Verify the ConHive Platform itself is operational.

Check Module Configuration: Some modules, if configured aggressively (e.g., very frequent status checks, verbose logging), might consume more CPU/RAM. Adjust intervals or settings.
Identify Culprit: Use tools like top or htop (Linux) or Task Manager (Windows) to see the agent’s resource consumption. Check agent logs for excessive activity.
Memory Leaks: If usage continuously grows over time without bound, it might indicate a bug or memory leak. Report this issue, providing details about the agent version and configuration.

(Add more specific issues and solutions as they become known.)