InfraBeacon

If your server is not reporting, here are some simple things to check.

Server shows as Offline

The server is marked offline if no report has been received in the last 5 minutes.

• Check the agent is running: Look for the cron job in /etc/cron.d/ib-agent

• Check the log file: tail /var/log/ib-agent.log for error messages

• Run the agent manually: sudo /usr/local/bin/ib-agent and watch for errors

• Check network access: The agent needs outbound HTTPS (port 443) to api.infrabeacon.io

"post failed" in the log

This usually means the agent could not reach the InfraBeacon API. Possible causes:

• Firewall blocking outbound HTTPS - Check your firewall rules

• DNS resolution failure - Check the server can resolve api.infrabeacon.io

• Proxy required - If your server needs a proxy, curl must be set up to use it

• Invalid token - Double-check the token in /etc/ib-agent.conf

Metrics look incorrect

• CPU always shows 0% on first run: This is normal. CPU usage is worked out from the change between readings, so the first report has nothing to compare with.

• Memory usage seems high: "Used" memory includes buffers and cache. This is expected behaviour on Linux. Only truly free memory is counted as free.

• Disk totals look different from df /: The agent reports root filesystem usage and combined totals for non-temporary mounted filesystems, so totals can be higher than the root disk alone.

Agent not installed

If the installer failed:

• Make sure you are running as root (sudo)

• Check that curl is installed (which curl)

• Check the server can reach infrabeacon.io over HTTPS

Still having issues?

If you have tried these steps and your server still is not reporting, contact support with:

• The output of cat /etc/ib-agent.conf (redact the token)

• The last 20 lines of /var/log/ib-agent.log

• The output of curl -I https://api.infrabeacon.io/server-agent