Celigo · On-premise agent

On-premise agent: Failed to send heartbeat

Short answer

A heartbeat failure in the Celigo on-premise agent log means the agent could not report to integrator.io, usually because of a network, token or process problem. Check the logs for successful tunnel messages, tunnelCreated followed by tunnelReadyForUse.

VerifiedLast verified

01Error text

Celigo error
[ERROR] Failed to send heartbeat: Connection timeout
[ERROR] Unable to reach https://api.integrator.io
[ERROR] Invalid token while sending heartbeat
[ERROR] Socket timeout during heartbeat

02Likely causes

  • The agent process is not running, or it crashed or hung.
  • The access token is expired or invalid.
  • There are network connectivity issues, or a firewall or proxy is blocking the agent.
  • There is time skew between the agent and the server.

03How to fix it

  1. Check the logs for successful tunnel messages, tunnelCreated followed by tunnelReadyForUse.
  2. If there is no tunnel, check for level=error with logName=noInternet.
  3. If noInternet and heartbeatFailed appear around the same time, look for a network connectivity issue on the machine or server.

iNotes

Heartbeats are sent approximately every 60 seconds. Brief outages of seconds to a minute typically resolve themselves.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Celigo work:Open Celigo jobsCeligo rates and salaries

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.